diff --git a/CHANGELOG.md b/CHANGELOG.md index 67894f68c..b01281309 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,7 @@ ## [Unreleased] +* Update PowerSTIG to successfully parse/apply Microsoft Windows Server 2019 STIG - Ver 2, Rel 2: [#893](https://github.com/microsoft/PowerStig/issues/893) * Update PowerSTIG to successfully parse/apply Red Hat Enterprise Linux 7 STIG - Ver 2, Rel 2: [#888](https://github.com/microsoft/PowerStig/issues/888) * Update PowerSTIG to successfully parse/apply Microsoft IIS 8.5 SITE/SERVER STIG - V2R2: [#884](https://github.com/microsoft/PowerStig/issues/884) * Update PowerSTIG to Parse/Apply Google Chrome Ver 2, Rel 2: [#876](https://github.com/microsoft/PowerStig/issues/876) diff --git a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V1R5_Manual-xccdf.log b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V1R5_Manual-xccdf.log deleted file mode 100644 index 2c9233963..000000000 --- a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V1R5_Manual-xccdf.log +++ /dev/null @@ -1,20 +0,0 @@ -V-92993::*::'' -V-93029::*::'' -V-93031::Administrators - Special - This folder only (Special = Basic Permissions: all selected except Full control)::Administrators - all selected except Full control - This folder only -V-93031::execute-::execute - -V-93031::(RX) - Read & execute::'' -V-93063::- Administrators::- Administrators`r`nSystems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines", SID S-1-5-83-0). This is not a finding. -V-93175::\SOFTWARE\ Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\::\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ -V-93217::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct AntiVirus service information'} -V-93257::0x00000000 (0) (Security), 0x00000001 (1) (Basic)::0 or 1 -V-93259::0x00000000 (0) - No peering (HTTP Only)::0, 1, 2, 99 or 100 -V-93261::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93263::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93267::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93311::0x00000002 (2) (or if the Value Name does not exist)::2 -V-93413::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93463::*::HardCodedRule(AccountPolicyRule)@{DscResource = 'AccountPolicy'; PolicyName = 'Minimum password length'; PolicyValue = $null; OrganizationValueTestString = "'{0}' -ge '14'"} -V-93523::0x00000002 (2) (Prompt for consent on the secure desktop)::1 or 2 -V-93563::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93571::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct Firewall service information'} -V-93149::*::HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System'; ValueName = 'LegalNoticeCaption'; ValueType = 'String'; ValueData = $null; OrganizationValueTestString = "'{0}' -match '^(DoD Notice and Consent Banner|US Department of Defense Warning Statement)$'"} diff --git a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V2R2_Manual-xccdf.log b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V2R2_Manual-xccdf.log new file mode 100644 index 000000000..ca4eedf7a --- /dev/null +++ b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V2R2_Manual-xccdf.log @@ -0,0 +1,28 @@ +V-205664::*::'' +V-205739::*::'' +V-205740::NT AUTHORITY\Authenticated Users:(RX)::C:\Windows\SYSVOL +V-205740::NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(GR,GE)::Type - "Allow" for all +V-205740::BUILTIN\Server Operators:(RX)::Inherited from - "None" for all +V-205740::BUILTIN\Server Operators:(OI)(CI)(IO)(GR,GE)::Principal - Access - Applies to +V-205740::BUILTIN\Administrators:(M,WDAC,WO)::Authenticated Users - Read & execute - This folder, subfolder, and files +V-205740::BUILTIN\Administrators:(OI)(CI)(IO)(F)::Server Operators - Read & execute - This folder, subfolder, and files +V-205740::NT AUTHORITY\SYSTEM:(F)::Administrators - all selected except Full control - This folder only +V-205740::NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)::CREATOR OWNER - Full control - Subfolders and files only +V-205740::CREATOR OWNER:(OI)(CI)(IO)(F)::Administrators - Full control - Subfolders and files only +V-205740::(RX) - Read & execute::SYSTEM - Full control - This folder, subfolders, and files +V-205756::- Administrators::- Administrators`r`nSystems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines", SID S-1-5-83-0). This is not a finding. +V-205639::\SOFTWARE\ Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\::\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ +V-205820::*::HardCodedRule(SecurityOptionRule)@{DscResource = 'SecurityOption'; OptionName = 'Domain_controller_LDAP_server_signing_requirements'; OptionValue = 'Require Signing'} +V-205850::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct AntiVirus service information'} +V-205869::0x00000000 (0) (Security), 0x00000001 (1) (Basic)::0 or 1 +V-205870::0x00000000 (0) - No peering (HTTP Only)::0, 1, 2, 99 or 100 +V-205871::0x00000000 (0) (or if the Value Name does not exist)::0 +V-205872::0x00000000 (0) (or if the Value Name does not exist)::0 +V-205874::0x00000000 (0) (or if the Value Name does not exist)::0 +V-205924::0x00000002 (2) (or if the Value Name does not exist)::2 +V-205693::0x00000000 (0) (or if the Value Name does not exist)::0 +V-205662::*::HardCodedRule(AccountPolicyRule)@{DscResource = 'AccountPolicy'; PolicyName = 'Minimum password length'; PolicyValue = $null; OrganizationValueTestString = "'{0}' -ge '14'"} +V-205717::0x00000002 (2) (Prompt for consent on the secure desktop)::1 or 2 +V-205830::0x00000000 (0) (or if the Value Name does not exist)::0 +V-214936::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct Firewall service information'} +V-205632::*::HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System'; ValueName = 'LegalNoticeCaption'; ValueType = 'String'; ValueData = $null; OrganizationValueTestString = "'{0}' -match '^(DoD Notice and Consent Banner|US Department of Defense Warning Statement)$'"} diff --git a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V1R5_Manual-xccdf.xml b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V2R2_Manual-xccdf.xml similarity index 62% rename from source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V1R5_Manual-xccdf.xml rename to source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V2R2_Manual-xccdf.xml index 20a293f7b..6403c686d 100644 --- a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V1R5_Manual-xccdf.xml +++ b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_DC_STIG_V2R2_Manual-xccdf.xml @@ -1,2975 +1,2796 @@  - - accepted - Windows Server 2019 Security Technical Implementation Guide + + accepted + Microsoft Windows Server 2019 Security Technical Implementation Guide This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil. + + DISA STIG.DOD.MIL - Release: 5 Benchmark Date: 17 Jun 2020 - 1 + Release: 2 Benchmark Date: 04 May 2021 + 3.2.2.36079 + 1.10.0 + 2 I - 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> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - SRG-OS-000028-GPOS-00009 - <GroupDescription></GroupDescription> - - WN19-SO-000120 - Windows Server 2019 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver. - <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. - -Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000056 - CCI-000057 - CCI-000060 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Interactive logon: Machine inactivity limit" to "900" seconds or less, excluding "0" which is effectively 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\Microsoft\Windows\CurrentVersion\Policies\System\ - -Value Name: InactivityTimeoutSecs - -Value Type: REG_DWORD -Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled) - - - - - SRG-OS-000032-GPOS-00013 - <GroupDescription></GroupDescription> - - WN19-AU-000190 - Windows Server 2019 must be configured to audit 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. - -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000067 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - Success - - - - - SRG-OS-000032-GPOS-00013 - <GroupDescription></GroupDescription> - - WN19-AU-000200 - Windows Server 2019 must be configured to audit 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. - -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000067 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - Failure - - - - - SRG-OS-000033-GPOS-00014 - <GroupDescription></GroupDescription> - - WN19-CC-000370 - Windows Server 2019 Remote Desktop Services must require secure Remote Procedure Call (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. - -Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000068 - CCI-001453 - Configure 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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ - -Value Name: fEncryptRPCTraffic - -Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000033-GPOS-00014 - <GroupDescription></GroupDescription> - - WN19-CC-000380 - Windows Server 2019 Remote Desktop Services must be configured with the client connection encryption set to High 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. - -Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000068 - CCI-001453 - Configure 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" with "High Level" 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 NT\Terminal Services\ - -Value Name: MinEncryptionLevel - -Type: REG_DWORD -Value: 0x00000003 (3) - - - - + SRG-OS-000002-GPOS-00002 <GroupDescription></GroupDescription> - + WN19-00-000300 Windows Server 2019 must automatically remove or disable temporary user accounts after 72 hours. <VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. @@ -2980,23 +2801,25 @@ If temporary accounts are used, the operating system must be configured to autom To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000016 - Configure temporary user accounts to automatically expire within 72 hours. + SV-103063 + V-92975 + CCI-000016 + Configure temporary user accounts to automatically expire within 72 hours. Domain accounts can be configured with an account expiration date, under "Account" properties. Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. Delete any temporary user accounts that are no longer necessary. - - - + + + Review temporary user accounts for expiration dates. Determine if temporary user accounts are used and identify any that exist. If none exist, this is NA. @@ -3019,61 +2842,10 @@ If "Account expires" has not been defined within 72 hours for any temporary user - - SRG-OS-000123-GPOS-00064 - <GroupDescription></GroupDescription> - - WN19-00-000310 - Windows Server 2019 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours. - <VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. - -Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. - -To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001682 - Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours. - -Domain accounts can be configured with an account expiration date, under "Account" properties. - -Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. - - - - Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. - -If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. - -If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. - -Domain Controllers: - -Open "PowerShell". - -Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". - -If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. - -Member servers and standalone systems: - -Open "Command Prompt". - -Run "Net user [username]", where [username] is the name of the emergency account. - -If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. - - - - + SRG-OS-000004-GPOS-00004 <GroupDescription></GroupDescription> - + WN19-AU-000100 Windows Server 2019 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. @@ -3082,22 +2854,24 @@ Security Group Management records events such as creating, deleting, or changing Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000018 - CCI-000172 - CCI-001403 - CCI-001404 - CCI-001405 - CCI-002130 - Configure 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. - - - + SV-103067 + V-92979 + CCI-000018 + CCI-001403 + CCI-001405 + CCI-001404 + CCI-002130 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -3114,10 +2888,10 @@ Account Management >> Security Group Management - Success - + SRG-OS-000004-GPOS-00004 <GroupDescription></GroupDescription> - + WN19-AU-000110 Windows Server 2019 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. @@ -3126,22 +2900,24 @@ User Account Management records events such as creating, changing, deleting, ren Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000018 - CCI-000172 - CCI-001403 - CCI-001404 - CCI-001405 - CCI-002130 - Configure 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. - - - + SV-103069 + V-92981 + CCI-002130 + CCI-001405 + CCI-001404 + CCI-001403 + CCI-000018 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -3158,10 +2934,10 @@ Account Management >> User Account Management - Success - + SRG-OS-000004-GPOS-00004 <GroupDescription></GroupDescription> - + WN19-AU-000120 Windows Server 2019 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. @@ -3170,22 +2946,24 @@ User Account Management records events such as creating, changing, deleting, ren Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000018 - CCI-000172 - CCI-001403 - CCI-001404 - CCI-001405 - CCI-002130 - Configure 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. - - - + SV-103071 + V-92983 + CCI-000172 + CCI-000018 + CCI-001403 + CCI-001404 + CCI-001405 + CCI-002130 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -3202,10 +2980,10 @@ Account Management >> User Account Management - Failure - + SRG-OS-000004-GPOS-00004 <GroupDescription></GroupDescription> - + WN19-DC-000230 Windows Server 2019 must be configured to audit Account Management - Computer 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. @@ -3214,22 +2992,24 @@ Computer Account Management records events such as creating, changing, deleting, Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000018 - CCI-000172 - CCI-001403 - CCI-001404 - CCI-001405 - CCI-002130 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Management >> "Audit Computer Account Management" with "Success" selected. - - - + SV-103073 + V-92985 + CCI-002130 + CCI-001405 + CCI-001403 + CCI-001404 + CCI-000018 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Management >> "Audit Computer Account Management" with "Success" selected. + + + This applies to domain controllers. It is NA for other systems. Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -3248,2927 +3028,3305 @@ Account Management >> Computer Account Management - Success - - SRG-OS-000240-GPOS-00090 + + SRG-OS-000023-GPOS-00006 <GroupDescription></GroupDescription> - - WN19-AU-000150 - Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. - -Account Lockout events can be used to identify potentially malicious logon attempts. + + WN19-SO-000130 + Windows Server 2019 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. -Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-001404 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103235 + V-93147 + CCI-000048 + CCI-000050 + CCI-001384 + CCI-001385 + CCI-001386 + CCI-001387 + CCI-001388 + Configure 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: -Use the "AuditPol" tool to review the current Audit Policy configuration: +You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +By using this IS (which includes any device attached to this IS), you consent to the following conditions: -Enter "AuditPol /get /category:*" +-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. -Compare the "AuditPol" settings with the following: +-At any time, the USG may inspect and seize data stored on this IS. -If the system does not audit the following, this is a finding. +-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. -Logon/Logoff >> Account Lockout - Success - - - - - SRG-OS-000240-GPOS-00090 - <GroupDescription></GroupDescription> - - WN19-AU-000160 - Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Account Lockout events can be used to identify potentially malicious logon attempts. +-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. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000172 - CCI-001404 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Use the "AuditPol" tool to review the current Audit Policy configuration: +Value Name: LegalNoticeText -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Value Type: REG_SZ +Value: See message text below -Enter "AuditPol /get /category:*" +You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. -Compare the "AuditPol" settings with the following: +By using this IS (which includes any device attached to this IS), you consent to the following conditions: -If the system does not audit the following, this is a finding. +-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. -Logon/Logoff >> Account Lockout - Failure +-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. - - SRG-OS-000080-GPOS-00048 + + SRG-OS-000023-GPOS-00006 <GroupDescription></GroupDescription> - - WN19-00-000130 - Windows Server 2019 local volumes must use a format that supports NTFS attributes. - <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 a file system that supports NTFS attributes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000140 + Windows Server 2019 title for legal banner dialog box must be configured with the appropriate text. + <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Format volumes to use NTFS or ReFS. - - - - Open "Computer Management". + SV-103237 + V-93149 + CCI-001388 + CCI-001386 + CCI-001387 + CCI-001384 + CCI-001385 + CCI-000048 + Configure 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 an organization-defined equivalent. -Select "Disk Management" under "Storage". +If an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN19-SO-000150. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -For each local volume, if the file system does not indicate "NTFS", this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -"ReFS" (resilient file system) is also acceptable and would not be a finding. +Value Name: LegalNoticeCaption -This does not apply to system partitions such the Recovery and EFI System Partition. - - - - - SRG-OS-000080-GPOS-00048 - <GroupDescription></GroupDescription> - - WN19-00-000180 - Windows Server 2019 non-administrative accounts or groups must only have print permissions on printer shares. - <VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000213 - Configure the permissions on shared printers to restrict standard users to only have Print permissions. - - - - Open "Printers & scanners" in "Settings". - -If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) - -For each printer: +Value Type: REG_SZ +Value: See message title options below -Select the printer and "Manage". +"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. -Select "Printer Properties". +If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. -Select the "Sharing" tab. +Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required. + + + + + SRG-OS-000028-GPOS-00009 + <GroupDescription></GroupDescription> + + WN19-SO-000120 + Windows Server 2019 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver. + <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. -If "Share this printer" is checked, select the "Security" tab. +Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-92961 + SV-103049 + CCI-000056 + CCI-000057 + CCI-000060 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Interactive logon: Machine inactivity limit" to "900" seconds or less, excluding "0" which is effectively disabled. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If any standard user accounts or groups have permissions other than "Print", this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -The default is for the "Everyone" group to be given "Print" permission. +Value Name: InactivityTimeoutSecs -"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts. +Value Type: REG_DWORD +Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled) - - SRG-OS-000312-GPOS-00122 + + SRG-OS-000032-GPOS-00013 <GroupDescription></GroupDescription> - - WN19-00-000140 - Windows Server 2019 permissions for the system drive root directory (usually C:\) 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. + + WN19-AU-000190 + Windows Server 2019 must be configured to audit 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. -The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). +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. -Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002165 - Maintain the default permissions for the system drive's root directory and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). - -Default Permissions -C:\ -Type - "Allow" for all -Inherited from - "None" for all - -Principal - Access - Applies to - -SYSTEM - Full control - This folder, subfolders, and files -Administrators - Full control - This folder, subfolders, and files -Users - Read & execute - This folder, subfolders, and files -Users - Create folders/append data - This folder and subfolders -Users - Create files/write data - Subfolders only -CREATOR OWNER - Full Control - Subfolders and files only - - - - The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + V-92967 + SV-103055 + CCI-000067 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Review the permissions for the system drive's root directory (usually C:\). 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. +Use the "AuditPol" tool to review the current Audit Policy configuration: -If permissions are not as restrictive as the default permissions listed below, this is a finding. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Viewing in File Explorer: +Enter "AuditPol /get /category:*" -View the Properties of the system drive's root directory. +Compare the "AuditPol" settings with the following: -Select the "Security" tab, and the "Advanced" button. +If the system does not audit the following, this is a finding. -Default permissions: -C:\ -Type - "Allow" for all -Inherited from - "None" for all +Logon/Logoff >> Logon - Success + + + + + SRG-OS-000032-GPOS-00013 + <GroupDescription></GroupDescription> + + WN19-AU-000200 + Windows Server 2019 must be configured to audit 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. -Principal - Access - Applies to +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. -SYSTEM - Full control - This folder, subfolders, and files -Administrators - Full control - This folder, subfolders, and files -Users - Read & execute - This folder, subfolders, and files -Users - Create folders/append data - This folder and subfolders -Users - Create files/write data - Subfolders only -CREATOR OWNER - Full Control - Subfolders and files only +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-92969 + SV-103057 + CCI-000172 + CCI-000067 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Alternately, use icacls: +Use the "AuditPol" tool to review the current Audit Policy configuration: -Open "Command Prompt (Admin)". +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Enter "icacls" followed by the directory: +Enter "AuditPol /get /category:*" -"icacls c:\" +Compare the "AuditPol" settings with the following: -The following results should be displayed: +If the system does not audit the following, this is a finding. -c:\ -NT AUTHORITY\SYSTEM:(OI)(CI)(F) -BUILTIN\Administrators:(OI)(CI)(F) -BUILTIN\Users:(OI)(CI)(RX) -BUILTIN\Users:(CI)(AD) -BUILTIN\Users:(CI)(IO)(WD) -CREATOR OWNER:(OI)(CI)(IO)(F) -Successfully processed 1 files; Failed processing 0 files +Logon/Logoff >> Logon - Failure - - SRG-OS-000312-GPOS-00122 + + SRG-OS-000033-GPOS-00014 <GroupDescription></GroupDescription> - - WN19-00-000150 - Windows Server 2019 permissions for program file 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. - -The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + + WN19-CC-000370 + Windows Server 2019 Remote Desktop Services must require secure Remote Procedure Call (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. -Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002165 - Maintain the default permissions for the program file directories and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). - -Default permissions: -\Program Files and \Program Files (x86) -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files - - - - The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). - -Review the permissions for the program file directories (Program Files and Program Files [x86]). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. - -If permissions are not as restrictive as the default permissions listed below, this is a finding. - -Viewing in File Explorer: + V-92971 + SV-103059 + CCI-000068 + CCI-001453 + Configure 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: -For each folder, view the Properties. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Select the "Security" tab, and the "Advanced" button. +Value Name: fEncryptRPCTraffic -Default permissions: -\Program Files and \Program Files (x86) -Type - "Allow" for all -Inherited from - "None" for all +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000033-GPOS-00014 + <GroupDescription></GroupDescription> + + WN19-CC-000380 + Windows Server 2019 Remote Desktop Services must be configured with the client connection encryption set to High 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. -Principal - Access - Applies to +Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-92973 + SV-103061 + CCI-001453 + CCI-000068 + Configure 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" with "High Level" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Alternately, use icacls: +Value Name: MinEncryptionLevel -Open a Command prompt (admin). +Type: REG_DWORD +Value: 0x00000003 (3) + + + + + SRG-OS-000042-GPOS-00020 + <GroupDescription></GroupDescription> + + WN19-CC-000090 + Windows Server 2019 command 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. -Enter "icacls" followed by the directory: +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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93173 + SV-103261 + CCI-000135 + Configure 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: -'icacls "c:\program files"' -'icacls "c:\program files (x86)"' +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ -The following results should be displayed for each when entered: +Value Name: ProcessCreationIncludeCmdLine_Enabled -c:\program files (c:\program files (x86)) -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) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) -Successfully processed 1 files; Failed processing 0 files +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000312-GPOS-00122 + + SRG-OS-000042-GPOS-00020 <GroupDescription></GroupDescription> - - WN19-00-000160 - Windows Server 2019 permissions for the Windows installation directory 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. - -The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + + WN19-CC-000460 + Windows Server 2019 PowerShell script block logging 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. -Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002165 - Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). + SV-103263 + V-93175 + CCI-000135 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> "Turn on PowerShell Script Block Logging" to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Default permissions: -Type - "Allow" for all -Inherited from - "None" for all +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ -Principal - Access - Applies to +Value Name: EnableScriptBlockLogging -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files - - - - The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000057-GPOS-00027 + <GroupDescription></GroupDescription> + + WN19-AU-000030 + Windows Server 2019 permissions 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. -Review the permissions for the Windows installation directory (usually C:\Windows). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93189 + SV-103277 + CCI-000162 + CCI-000163 + CCI-000164 + Configure the permissions on the Application event log file (Application.evtx) to prevent access by non-privileged accounts. The default permissions listed below satisfy this requirement: -If permissions are not as restrictive as the default permissions listed below, this is a finding: +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control -Viewing in File Explorer: +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. -For each folder, view the Properties. +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". + + + + Navigate to the Application event log file. -Select the "Security" tab and the "Advanced" button. +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. -Default permissions: -\Windows -Type - "Allow" for all -Inherited from - "None" for all +If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: -Principal - Access - Applies to +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + SRG-OS-000057-GPOS-00027 + <GroupDescription></GroupDescription> + + WN19-AU-000040 + Windows Server 2019 permissions 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. -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93191 + SV-103279 + CCI-000164 + CCI-000163 + CCI-000162 + Configure the permissions on the Security event log file (Security.evtx) to prevent access by non-privileged accounts. The default permissions listed below satisfy this requirement: -Alternately, use icacls: +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control -Open a Command prompt (admin). +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. -Enter "icacls" followed by the directory: +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". + + + + Navigate to the Security event log file. -"icacls c:\windows" +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. -The following results should be displayed for each when entered: +If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: -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) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) -Successfully processed 1 files; Failed processing 0 files +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000057-GPOS-00027 <GroupDescription></GroupDescription> - - WN19-00-000170 - Windows Server 2019 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained. - <VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000050 + Windows Server 2019 permissions 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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive. - -The default permissions of the higher-level keys are noted below. - -HKEY_LOCAL_MACHINE\SECURITY - -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -SYSTEM - Full Control - This key and subkeys -Administrators - Special - This key and subkeys + V-93193 + SV-103281 + CCI-000162 + CCI-000164 + CCI-000163 + Configure the permissions on the System event log file (System.evtx) to prevent access by non-privileged accounts. The default permissions listed below satisfy this requirement: -HKEY_LOCAL_MACHINE\SOFTWARE +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - This key and subkeys -ALL APPLICATION PACKAGES - Read - This key and subkeys +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. -HKEY_LOCAL_MACHINE\SYSTEM +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". + + + + Navigate to the System event log file. -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - Subkeys only -ALL APPLICATION PACKAGES - Read - This key and subkeys +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. -Microsoft has also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID. -S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 - - - - Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. +If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: -If any non-privileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + SRG-OS-000062-GPOS-00031 + <GroupDescription></GroupDescription> + + WN19-SO-000050 + Windows Server 2019 must force audit policy subcategory settings to override audit policy category settings. + <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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93151 + SV-103239 + CCI-000169 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If permissions are not as restrictive as the default permissions listed below, this is a finding: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Run "Regedit". +Value Name: SCENoApplyLegacyAuditPolicy -Right-click on the registry areas noted below. +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000066-GPOS-00034 + <GroupDescription></GroupDescription> + + WN19-DC-000280 + Windows Server 2019 domain controllers must have a PKI server certificate. + <VulnDiscussion>Domain controllers are part of the chain of trust for PKI authentications. Without the appropriate certificate, the authenticity of the domain controller cannot be verified. Domain controllers must have a server certificate to establish authenticity as part of PKI authentications in 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93481 + SV-103567 + CCI-000185 + Obtain a server certificate for the domain controller. + + + + This applies to domain controllers. It is NA for other systems. -Select "Permissions" and the "Advanced" button. +Run "MMC". -HKEY_LOCAL_MACHINE\SECURITY +Select "Add/Remove Snap-in" from the "File" menu. -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -SYSTEM - Full Control - This key and subkeys -Administrators - Special - This key and subkeys +Select "Certificates" in the left pane and click the "Add >" button. -HKEY_LOCAL_MACHINE\SOFTWARE +Select "Computer Account" and click "Next". -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - This key and subkeys -ALL APPLICATION PACKAGES - Read - This key and subkeys +Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". -HKEY_LOCAL_MACHINE\SYSTEM +Click "OK". -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - Subkeys only -ALL APPLICATION PACKAGES - Read - This key and subkeys +Select and expand the Certificates (Local Computer) entry in the left pane. -Other examples under the noted keys may also be sampled. There may be some instances where non-privileged groups have greater than Read permission. +Select and expand the Personal entry in the left pane. -Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID, this is currently not a finding. -S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 +Select the Certificates entry in the left pane. -If the defaults have not been changed, these are not a finding. +If no certificate for the domain controller exists in the right pane, this is a finding. - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000066-GPOS-00034 <GroupDescription></GroupDescription> - - WN19-DC-000010 - Windows Server 2019 must only allow administrators responsible for the domain controller to 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 using only accounts with the minimum level of authority necessary. - -Standard user accounts must not be members of the built-in Administrators group.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000290 + Windows Server 2019 domain Controller PKI certificates must be issued by the DoD PKI or an approved External Certificate Authority (ECA). + <VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the Administrators group to include only administrator groups or accounts that are responsible for the system. + SV-103569 + V-93483 + CCI-000185 + Obtain a server certificate for the domain controller issued by the DoD PKI or an approved ECA. + + + + This applies to domain controllers. It is NA for other systems. -Remove any standard user accounts. - - - - This applies to domain controllers. A separate version applies to other systems. +Run "MMC". -Review the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group. +Select "Add/Remove Snap-in" from the "File" menu. -Standard user accounts must not be members of the local administrator group. +Select "Certificates" in the left pane and click the "Add >" button. -If prohibited accounts are members of the local administrators group, this is a finding. +Select "Computer Account" and click "Next". -If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding. +Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". + +Click "OK". + +Select and expand the Certificates (Local Computer) entry in the left pane. + +Select and expand the Personal entry in the left pane. + +Select the Certificates entry in the left pane. + +In the right pane, examine the "Issued By" field for the certificate to determine the issuing CA. + +If the "Issued By" field of the PKI certificate being used by the domain controller does not indicate the issuing CA is part of the DoD PKI or an approved ECA, this is a finding. + +If the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding. + +There are multiple sources from which lists of valid DoD CAs and approved ECAs can be obtained: + +The Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil. + +DoD Public Key Enablement (PKE) Engineering Support maintains the InstallRoot utility to manage DoD supported root certificates on Windows computers, which includes a list of authorized CAs. The utility package can be downloaded from the PKI and PKE Tools page on IASE: + +http://iase.disa.mil/pki-pke/function_pages/tools.html - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000066-GPOS-00034 <GroupDescription></GroupDescription> - - WN19-DC-000070 - Windows Server 2019 permissions on the Active Directory data files must only allow System and Administrators access. - <VulnDiscussion>Improper access permissions for directory data-related files could allow unauthorized users to read, modify, or delete directory data or audit trails.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000300 + Windows Server 2019 PKI certificates associated with user accounts must be issued by a DoD PKI or an approved External Certificate Authority (ECA). + <VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Maintain the permissions on NTDS database and log files as follows: - -NT AUTHORITY\SYSTEM:(I)(F) -BUILTIN\Administrators:(I)(F) - -(I) - permission inherited from parent container -(F) - full access - - - + V-93485 + SV-103571 + CCI-000185 + Map user accounts to PKI certificates using the appropriate User Principal Name (UPN) for the network. See PKE documentation for details. + + + This applies to domain controllers. It is NA for other systems. -Run "Regedit". - -Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". +Review user account mappings to PKI certificates. -Note the directory locations in the values for: +Open "Windows PowerShell". -Database log files path -DSA Database file +Enter "Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled". -By default, they will be \Windows\NTDS. +Exclude disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. -If the locations are different, the following will need to be run for each. +If the User Principal Name (UPN) is not in the format of an individual's identifier for the certificate type and for the appropriate domain suffix, this is a finding. -Open "Command Prompt (Admin)". +For standard NIPRNet certificates, the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI). -Navigate to the NTDS directory (\Windows\NTDS by default). +Alt Tokens and other certificates may use a different UPN format than the EDI-PI which vary by organization. Verified these with the organization. -Run "icacls *.*". +NIPRNet Example: -If the permissions on each file are not as restrictive as the following, this is a finding: +Name - User Principal Name +User1 - 1234567890@mil -NT AUTHORITY\SYSTEM:(I)(F) -BUILTIN\Administrators:(I)(F) +See PKE documentation for other network domain suffixes. -(I) - permission inherited from parent container -(F) - full access +If the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding. - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000066-GPOS-00034 <GroupDescription></GroupDescription> - - WN19-DC-000080 - Windows Server 2019 Active Directory SYSVOL directory must have the proper access control permissions. - <VulnDiscussion>Improper access permissions for directory data files could allow unauthorized users to read, modify, or delete directory data. + + WN19-PK-000010 + Windows Server 2019 must have the DoD Root Certificate Authority (CA) certificates 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 CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. -The SYSVOL directory contains public files (to the domain) such as policies and logon scripts. Data in shared subdirectories are replicated to all domain controllers in a domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Maintain the permissions on the SYSVOL directory. Do not allow greater than "Read & execute" permissions for standard user accounts or groups. The defaults below meet this requirement: + SV-103573 + V-93487 + CCI-000185 + CCI-002470 + Install the DoD Root CA certificates: -C:\Windows\SYSVOL -Type - "Allow" for all -Inherited from - "None" for all +DoD Root CA 2 +DoD Root CA 3 +DoD Root CA 4 +DoD Root CA 5 -Principal - Access - Applies to +The InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. + + + + The certificates and thumbprints referenced below apply to unclassified systems; see PKE documentation for other networks. -Authenticated Users - Read & execute - This folder, subfolder, and files -Server Operators - Read & execute- This folder, subfolder, and files -Administrators - Special - This folder only (Special = Basic Permissions: all selected except Full control) -CREATOR OWNER - Full control - Subfolders and files only -Administrators - Full control - Subfolders and files only -SYSTEM - Full control - This folder, subfolders, and files - - - - This applies to domain controllers. It is NA for other systems. +Open "Windows PowerShell" as an administrator. -Open a command prompt. +Execute the following command: -Run "net share". +Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint, NotAfter -Make note of the directory location of the SYSVOL share. +If the following certificate "Subject" and "Thumbprint" information is not displayed, this is a finding. -By default, this will be \Windows\SYSVOL\sysvol. For this requirement, permissions will be verified at the first SYSVOL directory level. +Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 +NotAfter: 12/5/2029 -If any standard user accounts or groups have greater than "Read & execute" permissions, this is a finding. +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB +NotAfter: 12/30/2029 -The default permissions noted below meet this requirement: +Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 +NotAfter: 7/25/2032 -Open "Command Prompt". +Subject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B +NotAfter: 6/14/2041 -Run "icacls c:\Windows\SYSVOL". +Alternately, use the Certificates MMC snap-in: -The following results should be displayed: +Run "MMC". -NT AUTHORITY\Authenticated Users:(RX) -NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(GR,GE) -BUILTIN\Server Operators:(RX) -BUILTIN\Server Operators:(OI)(CI)(IO)(GR,GE) -BUILTIN\Administrators:(M,WDAC,WO) -BUILTIN\Administrators:(OI)(CI)(IO)(F) -NT AUTHORITY\SYSTEM:(F) -NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) -CREATOR OWNER:(OI)(CI)(IO)(F) +Select "File", "Add/Remove Snap-in". -(RX) - Read & execute +Select "Certificates" and click "Add". -Run "icacls /help" to view definitions of other permission codes. +Select "Computer account" and click "Next". -Alternately, open "File Explorer". +Select "Local computer: (the computer this console is running on)" and click "Finish". -Navigate to \Windows\SYSVOL (or the directory noted previously if different). +Click "OK". -Right-click the directory and select properties. +Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates". -Select the "Security" tab and click "Advanced". +For each of the DoD Root CA certificates noted below: -Default permissions: +Right-click on the certificate and select "Open". -C:\Windows\SYSVOL -Type - "Allow" for all -Inherited from - "None" for all +Select the "Details" Tab. -Principal - Access - Applies to +Scroll to the bottom and select "Thumbprint". -Authenticated Users - Read & execute - This folder, subfolder, and files -Server Operators - Read & execute- This folder, subfolder, and files -Administrators - Special - This folder only (Special = Basic Permissions: all selected except Full control) -CREATOR OWNER - Full control - Subfolders and files only -Administrators - Full control - Subfolders and files only -SYSTEM - Full control - This folder, subfolders, and files +If the DoD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. + +DoD Root CA 2 +Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 +Valid to: Wednesday, December 5, 2029 + +DoD Root CA 3 +Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB +Valid to: Sunday, December 30, 2029 + +DoD Root CA 4 +Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 +Valid to: Sunday, July 25, 2032 + +DoD Root CA 5 +Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B +Valid to: Friday, June 14, 2041 - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000066-GPOS-00034 <GroupDescription></GroupDescription> - - WN19-DC-000090 - Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions. - <VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems relying on the directory service. + + WN19-PK-000020 + Windows Server 2019 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates 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. -For Active Directory (AD), the Group Policy objects require special attention. In a distributed administration model (i.e., help desk), Group Policy objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for Group Policy objects, this could allow an intruder to change the security policy applied to all domain client computers (workstations and servers).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Maintain the permissions on Group Policy objects to not allow greater than "Read" and "Apply group policy" for standard user accounts or groups. The default permissions below meet this requirement: + V-93489 + SV-103575 + CCI-000185 + CCI-002470 + Install the DoD Interoperability Root CA cross-certificates on unclassified systems. -Authenticated Users - Read, Apply group policy, Special permissions +Issued To - Issued By - Thumbprint -The special permissions for Authenticated Users are for Read-type Properties. +DoD Root CA 2 - DoD Interoperability Root CA 1 - A8C27332CCB4CA49554CE55D34062A7DD2850C02 -CREATOR OWNER - Special permissions -SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions -Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions +DoD Root CA 3 - DoD Interoperability Root CA 2 - AC06108CA348CC03B53795C64BF84403C1DBD341 -Document any other access permissions that allow the objects to be updated with the ISSO. +Administrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. -The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on created Group Policy objects. - - - - This applies to domain controllers. It is NA for other systems. +The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. + + + + This is applicable to unclassified systems. It is NA for others. -Review the permissions on Group Policy objects. +Open "PowerShell" as an administrator. -Open "Group Policy Management" (available from various menus or run "gpmc.msc"). +Execute the following command: -Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). +Get-ChildItem -Path Cert:Localmachine\disallowed | Where {$_.Issuer -Like "*DoD Interoperability*" -and $_.Subject -Like "*DoD*"} | FL Subject, Issuer, Thumbprint, NotAfter -For each Group Policy object: +If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. -Select the Group Policy object item in the left pane. +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: AC06108CA348CC03B53795C64BF84403C1DBD341 +NotAfter: 1/22/2022 10:22:56 AM -Select the "Delegation" tab in the right pane. +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: A8C27332CCB4CA49554CE55D34062A7DD2850C02 +NotAfter: 8/26/2022 9:25:51 AM -Select the "Advanced" button. +Alternately, use the Certificates MMC snap-in: -Select each Group or user name. +Run "MMC". -View the permissions. +Select "File", "Add/Remove Snap-in". -If any standard user accounts or groups have "Allow" permissions greater than "Read" and "Apply group policy", this is a finding. +Select "Certificates" and click "Add". -Other access permissions that allow the objects to be updated are considered findings unless specifically documented by the ISSO. +Select "Computer account" and click "Next". -The default permissions noted below satisfy this requirement. +Select "Local computer: (the computer this console is running on)" and click "Finish". -The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next "Advanced" button, the desired Permission entry, and the "Edit" button. +Click "OK". -Authenticated Users - Read, Apply group policy, Special permissions +Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates". -The special permissions for Authenticated Users are for Read-type Properties. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. +For each certificate with "DoD Root CA..." under "Issued To" and "DoD Interoperability Root CA..." under "Issued By": -The special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties: +Right-click on the certificate and select "Open". -CREATOR OWNER - Special permissions -SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions -Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions +Select the "Details" Tab. -The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on organization created Group Policy objects. +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: DoD Root CA 2 +Issued By: DoD Interoperability Root CA 1 +Thumbprint: A8C27332CCB4CA49554CE55D34062A7DD2850C02 +Valid to: Friday, August 26, 2022 + +Issued To: DoD Root CA 3 +Issued By: DoD Interoperability Root CA 2 +Thumbprint: AC06108CA348CC03B53795C64BF84403C1DBD341 +Valid to: Saturday, January 22, 2022 - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000066-GPOS-00034 <GroupDescription></GroupDescription> - - WN19-DC-000100 - Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions. - <VulnDiscussion>When Active Directory objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. + + WN19-PK-000030 + Windows Server 2019 must have the US DoD CCEB Interoperability Root CA cross-certificates 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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. -The Domain Controllers OU object requires special attention as the Domain Controllers are central to the configuration and management of the domain. Inappropriate access permissions defined for the Domain Controllers OU could allow an intruder or unauthorized personnel to make changes that could lead to the compromise of the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Limit the permissions on the Domain Controllers OU to restrict changes to System, Domain Admins, Enterprise Admins and Administrators. + V-93491 + SV-103577 + CCI-000185 + CCI-002470 + Install the US DoD CCEB Interoperability Root CA cross-certificate on unclassified systems. -The default permissions listed below satisfy this requirement. +Issued To - Issued By - Thumbprint -Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions. +DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 -CREATOR OWNER - Special permissions +DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - 929BF3196896994C0A201DF4A5B71F603FEFBF2E -SELF - Special permissions +Administrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. -Authenticated Users - Read, Special permissions - -The special permissions for Authenticated Users are Read types. - -SYSTEM - Full Control - -Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions +The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. + + + + This is applicable to unclassified systems. It is NA for others. -Enterprise Admins - Full Control +Open "PowerShell" as an administrator. -Key Admins - Special permissions +Execute the following command: -Enterprise Key Admins - Special permissions +Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions +If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. -Pre-Windows 2000 Compatible Access - Special permissions +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 +NotAfter: 8/26/2022 9:07:50 AM -The special permissions for Pre-Windows 2000 Compatible Access are Read types. +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E +NotAfter: 9/27/2019 -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions - - - - This applies to domain controllers. It is NA for other systems. +Alternately, use the Certificates MMC snap-in: -Review the permissions on the Domain Controllers OU. +Run "MMC". -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +Select "File", "Add/Remove Snap-in". -Select "Advanced Features" in the "View" menu if not previously selected. +Select "Certificates" and click "Add". -Select the "Domain Controllers" OU (folder in folder icon). +Select "Computer account" and click "Next". -Right-click and select "Properties". +Select "Local computer: (the computer this console is running on)" and click "Finish". -Select the "Security" tab. +Click "OK". -If the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding. +Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates". -The default permissions listed below satisfy this requirement. +For each certificate with "US DoD CCEB Interoperability Root CA ..." under "Issued By": -Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions and are not a finding. +Right-click on the certificate and select "Open". -The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "View" or "Edit" button. +Select the "Details" Tab. -Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. +Scroll to the bottom and select "Thumbprint". -CREATOR OWNER - Special permissions +If the certificate below is not listed or the value for the "Thumbprint" field is not as noted, this is a finding. -SELF - Special permissions +Issued To: DoD Root CA 3 +Issued By: US DoD CCEB Interoperability Root CA 2 +Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 +Valid to: Friday, August 26, 2022 -Authenticated Users - Read, Special permissions +Issued To: DoD Root CA 3 +Issued By: US DoD CCEB Interoperability Root CA 2 +Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E +Valid: Friday, September 27, 2019 + + + + + SRG-OS-000067-GPOS-00035 + <GroupDescription></GroupDescription> + + WN19-SO-000350 + Windows Server 2019 users must be required to enter a password to access private keys stored on the computer. + <VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. -The special permissions for Authenticated Users are Read types. +The cornerstone of the PKI is the private key used to encrypt or digitally sign information. -If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. +If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. -SYSTEM - Full Control +Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93493 + SV-103579 + CCI-000186 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "System cryptography: Force strong key protection for user keys stored on the computer" to "User must enter a password each time they use a key". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Cryptography\ -Enterprise Admins - Full Control +Value Name: ForceKeyProtection -Key Admins - Special permissions +Type: REG_DWORD +Value: 0x00000002 (2) + + + + + SRG-OS-000073-GPOS-00041 + <GroupDescription></GroupDescription> + + WN19-SO-000300 + Windows Server 2019 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 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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93467 + SV-103553 + CCI-000196 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Enterprise Key Admins - Special permissions +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions +Value Name: NoLMHash -Pre-Windows 2000 Compatible Access - Special permissions +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000074-GPOS-00042 + <GroupDescription></GroupDescription> + + WN19-SO-000180 + Windows Server 2019 unencrypted passwords must not be sent to third-party Server Message Block (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 determine 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93469 + SV-103555 + CCI-000197 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -The Special permissions for Pre-Windows 2000 Compatible Access are Read types. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. +Value Name: EnablePlainTextPassword -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions +Value Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000076-GPOS-00044 <GroupDescription></GroupDescription> - - WN19-DC-000110 - Windows Server 2019 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions. - <VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. + + WN19-00-000020 + Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days. + <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. -For Active Directory, the OU objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a denial of service (DoS) to authorized users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Maintain the Allow type permissions on domain-defined OUs to be at least as restrictive as the defaults below. + V-93473 + SV-103559 + CCI-000199 + Change the built-in Administrator account password at least every "60" days. -Document any additional permissions above Read with the ISSO if an approved distributed administration model (help desk or other user support staff) is implemented. +Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this. + + + + Review the password last set date for the built-in Administrator account. -CREATOR OWNER - Special permissions +Domain controllers: -Self - Special permissions +Open "PowerShell". -Authenticated Users - Read, Special permissions +Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". -The special permissions for Authenticated Users are Read type. +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. -SYSTEM - Full Control +Member servers and standalone systems: -Domain Admins - Full Control +Open "Command Prompt". -Enterprise Admins - Full Control +Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. -Key Admins - Special permissions +(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) -Enterprise Key Admins - Special permissions +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. + + + + + SRG-OS-000076-GPOS-00044 + <GroupDescription></GroupDescription> + + WN19-00-000210 + Windows Server 2019 passwords must be configured to expire. + <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93475 + SV-103561 + CCI-000199 + Configure all enabled user account passwords to expire. -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions +Uncheck "Password never expires" for all enabled user accounts in Active Directory Users and Computers for domain accounts and Users in Computer Management for member servers and standalone systems. Document any exceptions with the ISSO. + + + + Review the password never expires status for enabled user accounts. -Pre-Windows 2000 Compatible Access - Special permissions +Open "PowerShell". -The special permissions for Pre-Windows 2000 Compatible Access are for Read types. +Domain Controllers: -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions - - - - This applies to domain controllers. It is NA for other systems. +Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". -Review the permissions on domain-defined OUs. +Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. -Ensure "Advanced Features" is selected in the "View" menu. +Member servers and standalone systems: -For each OU that is defined (folder in folder icon) excluding the Domain Controllers OU: +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. -Right-click the OU and select "Properties". +Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). -Select the "Security" tab. +If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding. + + + + + SRG-OS-000078-GPOS-00046 + <GroupDescription></GroupDescription> + + WN19-00-000050 + Windows Server 2019 manually managed application 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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103547 + V-93461 + CCI-000205 + Establish a policy that requires application/service account passwords that are manually managed to be at least 15 characters in length. Ensure the policy is enforced. + + + + Determine if manually managed application/service accounts exist. If none exist, this is NA. -If the Allow type permissions on the OU are not at least as restrictive as those below, this is a finding. +Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. -The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "Edit" or "View" button. +If such a policy does not exist or has not been implemented, this is a finding. + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN19-00-000130 + Windows Server 2019 local volumes must use a format that supports NTFS attributes. + <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 a file system that supports NTFS attributes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-92991 + SV-103079 + CCI-000213 + Format volumes to use NTFS or ReFS. + + + + Open "Computer Management". -Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. +Select "Disk Management" under "Storage". -CREATOR OWNER - Special permissions +For each local volume, if the file system does not indicate "NTFS", this is a finding. -Self - Special permissions +"ReFS" (resilient file system) is also acceptable and would not be a finding. -Authenticated Users - Read, Special permissions +This does not apply to system partitions such the Recovery and EFI System Partition. + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN19-00-000180 + Windows Server 2019 non-administrative accounts or groups must only have print permissions on printer shares. + <VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103081 + V-92993 + CCI-000213 + Configure the permissions on shared printers to restrict standard users to only have Print permissions. + + + + Open "Printers & scanners" in "Settings". -The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. +If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) -SYSTEM - Full Control +For each printer: -Domain Admins - Full Control +Select the printer and "Manage". -Enterprise Admins - Full Control +Select "Printer Properties". -Key Admins - Special permissions +Select the "Sharing" tab. -Enterprise Key Admins - Special permissions +If "Share this printer" is checked, select the "Security" tab. -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions +If any standard user accounts or groups have permissions other than "Print", this is a finding. -Pre-Windows 2000 Compatible Access - Special permissions - -The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. - -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions - -If an ISSO-approved distributed administration model (help desk or other user support staff) is implemented, permissions above Read may be allowed for groups documented by the ISSO. - -If any OU with improper permissions includes identification or authentication data (e.g., accounts, passwords, or password hash data) used by systems to determine access control, the severity is CAT I (e.g., OUs that include user accounts, including service/application accounts). +The default is for the "Everyone" group to be given "Print" permission. -If an OU with improper permissions does not include identification and authentication data used by systems to determine access control, the severity is CAT II (e.g., Workstation, Printer OUs). +"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000090 - Windows Server 2019 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 Events records events such as the access of a password hash or the Password Policy Checking API being called. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000270 + Windows Server 2019 must have the roles and features required by the system documented. + <VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + SV-103467 + V-93381 + CCI-000381 + Document the roles and features required for the system to operate. Uninstall any that are not required. + + + + Required roles and features will vary based on the function of the individual system. -Compare the "AuditPol" settings with the following: +Roles and features specifically required to be disabled per the STIG are identified in separate requirements. -If the system does not audit the following, this is a finding: +If the organization has not documented the roles and features required for the system(s), this is a finding. -Account Management >> Other Account Management Events - Success +The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State". - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000140 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000320 + Windows Server 2019 must not have the Fax Server role installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93383 + SV-103469 + CCI-000381 + Uninstall the "Fax Server" role. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the role. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -Detailed Tracking >> Process Creation - Success +Deselect "Fax Server" on the "Roles" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Fax". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000260 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000340 + Windows Server 2019 must not have the Peer Name Resolution Protocol installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103471 + V-93385 + CCI-000381 + Uninstall the "Peer Name Resolution Protocol" feature. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the feature. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -Policy Change >> Audit Policy Change - Success +Deselect "Peer Name Resolution Protocol" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq PNRP". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000270 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000350 + Windows Server 2019 must not have Simple TCP/IP Services installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93387 + SV-103473 + CCI-000381 + Uninstall the "Simple TCP/IP Services" feature. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the feature. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -Policy Change >> Audit Policy Change - Failure +Deselect "Simple TCP/IP Services" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Simple-TCPIP". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000280 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000370 + Windows Server 2019 must not have the TFTP Client installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103475 + V-93389 + CCI-000381 + Uninstall the "TFTP Client" feature. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the feature. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -Policy Change >> Authentication Policy Change - Success +Deselect "TFTP Client" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq TFTP-Client". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000290 - Windows Server 2019 must be configured to audit Policy Change - Authorization 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. - -Authorization Policy Change records events related to changes in user rights, such as "Create a token object". - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000380 + Windows Server 2019 must not the Server Message Block (SMB) v1 protocol installed. + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> "Audit Authorization 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93391 + SV-103477 + CCI-000381 + Uninstall the SMBv1 protocol. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Open "Windows PowerShell" with elevated privileges (run as administrator). -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Enter "Uninstall-WindowsFeature -Name FS-SMB1 -Restart". +(Omit the Restart parameter if an immediate restart of the system cannot be done.) -Enter "AuditPol /get /category:*" +Alternately: -Compare the "AuditPol" settings with the following: +Start "Server Manager". -If the system does not audit the following, this is a finding. +Select the server with the feature. -Policy Change >> Authorization Policy Change - Success - - - - - SRG-OS-000327-GPOS-00127 - <GroupDescription></GroupDescription> - - WN19-AU-000300 - Windows Server 2019 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. +Scroll down to "ROLES AND FEATURES" in the right pane. -Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs". +Select "Remove Roles and Features" from the drop-down "TASKS" list. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. +Select the appropriate server on the "Server Selection" page and click "Next". -Use the "AuditPol" tool to review the current Audit Policy configuration: +Deselect "SMB 1.0/CIFS File Sharing Support" on the "Features" page. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Click "Next" and "Remove" as prompted. + + + + Different methods are available to disable SMBv1 on Windows Server 2019. This is the preferred method, however if WN19-00-000390 and WN19-00-000400 are configured, this is NA. -Enter "AuditPol /get /category:*" +Open "Windows PowerShell" with elevated privileges (run as administrator). -Compare the "AuditPol" settings with the following: +Enter "Get-WindowsFeature -Name FS-SMB1". -If the system does not audit the following, this is a finding. +If "Installed State" is "Installed", this is a finding. -Privilege Use >> Sensitive Privilege Use - Success +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000310 - Windows Server 2019 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". - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000390 + Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server. + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103479 + V-93393 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 Server" to "Disabled". -Use the "AuditPol" tool to review the current Audit Policy configuration: +The system must be restarted for the change to take effect. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +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. + + + + Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. -Enter "AuditPol /get /category:*" +If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ -If the system does not audit the following, this is a finding. +Value Name: SMB1 -Privilege Use >> Sensitive Privilege Use - Failure +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000320 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000400 + Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client. + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93395 + SV-103481 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 client driver" to "Enabled" with "Disable driver (recommended)" selected for "Configure MrxSmb10 driver". -Use the "AuditPol" tool to review the current Audit Policy configuration: +The system must be restarted for the changes to take effect. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +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. + + + + Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. -Enter "AuditPol /get /category:*" +If the following registry value is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ -If the system does not audit the following, this is a finding. +Value Name: Start -System >> IPsec Driver - Success +Type: REG_DWORD +Value: 0x00000004 (4) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000330 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000410 + Windows Server 2019 must not have Windows PowerShell 2.0 installed. + <VulnDiscussion>Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93397 + SV-103483 + CCI-000381 + Uninstall the "Windows PowerShell 2.0 Engine". -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the feature. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -System >> IPsec Driver - Failure +Deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq PowerShell-v2". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000340 - Windows Server 2019 must be configured to audit System - Other System 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. - -Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000010 + Windows Server 2019 must prevent the display of slide shows on the lock screen. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + V-93399 + SV-103485 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> Control Panel >> Personalization >> "Prevent enabling lock screen slide show" to "Enabled". + + + + Verify the registry value below. -Enter "AuditPol /get /category:*" +If it does not exist or is not configured as specified, this is a finding. -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\ -If the system does not audit the following, this is a finding. +Value Name: NoLockScreenSlideshow -System >> Other System Events - Success +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000350 - Windows Server 2019 must be configured to audit System - Other System 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. - -Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000020 + Windows Server 2019 must have WDigest Authentication 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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + SV-103487 + V-93401 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "WDigest Authentication (disabling may require KB2871997)" to "Disabled". -Enter "AuditPol /get /category:*" +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: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\ -If the system does not audit the following, this is a finding. +Value Name: UseLogonCredential -System >> Other System Events - Failure +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000360 - Windows Server 2019 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. + + WN19-CC-000150 + Windows Server 2019 downloading print driver packages over HTTP 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 will prevent uncontrolled updates to the system. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + SV-103489 + V-93403 + CCI-000381 + Configure 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: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ -If the system does not audit the following, this is a finding. +Value Name: DisableWebPnPDownload -System >> Security State Change - Success +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000370 - Windows Server 2019 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. + + WN19-CC-000160 + Windows Server 2019 printing over HTTP 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 will prevent uncontrolled updates to the system. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + SV-103491 + V-93405 + CCI-000381 + Configure 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: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ -If the system does not audit the following, this is a finding. +Value Name: DisableHTTPPrinting -System >> Security System Extension - Success +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000380 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000170 + Windows Server 2019 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 in to 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + SV-103493 + V-93407 + CCI-000381 + Configure 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. -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ -If the system does not audit the following, this is a finding. +Value Name: DontDisplayNetworkSelectionUI -System >> System Integrity - Success +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000390 - Windows Server 2019 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. + + WN19-CC-000200 + Windows Server 2019 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 will prevent uncontrolled updates to the system. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + V-93409 + SV-103495 + CCI-000381 + Configure 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: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\ -If the system does not audit the following, this is a finding. +Value Name: DisableInventory -System >> System Integrity - Failure +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-DC-000170 - Windows Server 2019 Active Directory Group Policy objects must be configured with proper audit settings. - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000300 + Windows Server 2019 Windows Defender SmartScreen must be enabled. + <VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the audit settings for Group Policy objects to include the following: + V-93411 + SV-103497 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Configure Windows Defender SmartScreen" to "Enabled" with either option "Warn" or "Warn and prevent bypass" selected. -This can be done at the Policy level in Active Directory to apply to all group policies. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +Windows 2019 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer. + + + + This is applicable to unclassified systems; for other systems, this is NA. -Select "Advanced Features" from the "View" Menu. +If the following registry value does not exist or is not configured as specified, this is a finding: -Navigate to [Domain] >> System >> Policies in the left panel. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ -Right click "Policies", select "Properties". +Value Name: EnableSmartScreen -Select the "Security" tab. +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN19-CC-000400 + Windows Server 2019 must disable Basic authentication for RSS feeds over HTTP. + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93413 + SV-103499 + CCI-000381 + The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. -Select the "Advanced" button. +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> "Turn on Basic feed authentication over HTTP" to "Not Configured" or "Disabled". + + + + The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. -Select the "Auditing" tab. +If the registry value name below does not exist, this is not a finding. -Type - Fail -Principal - Everyone -Access - Full Control -Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects +If it exists and is configured with a value of "0", this is not a finding. -The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. +If it exists and is configured with a value of "1", this is a finding. -Type - Success -Principal - Everyone -Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) -Inherited from - Parent Object -Applies to - Descendant groupPolicyContainer objects +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ -Two instances with the following summary information will be listed: +Value Name: AllowBasicAuthInClear -Type - Success -Principal - Everyone -Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) -Inherited from - Parent Object -Applies to - Descendant Organization Unit Objects - - - - This applies to domain controllers. It is NA for other systems. +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN19-CC-000410 + Windows Server 2019 must prevent Indexing of encrypted files. + <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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93415 + SV-103501 + CCI-000381 + Configure 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: -Review the auditing configuration for all Group Policy objects. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\ -Open "Group Policy Management" (available from various menus or run "gpmc.msc"). +Value Name: AllowIndexingEncryptedStoresOrItems -Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN19-DC-000130 + Windows Server 2019 domain controllers must run on a machine dedicated to that function. + <VulnDiscussion>Executing application servers on the same host machine with a directory server may substantially weaken the security of the directory server. Web or database server applications usually require the addition of many programs and accounts, increasing the attack surface of the computer. -For each Group Policy object: +Some applications require the addition of privileged accounts, providing potential sources of compromise. Some applications (such as Microsoft Exchange) may require the use of network ports or services conflicting with the directory server. In this case, non-standard ports might be selected, and this could interfere with intrusion detection or prevention 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103503 + V-93417 + CCI-000381 + Remove additional roles or applications such as web, database, and email from the domain controller. + + + + This applies to domain controllers, it is NA for other systems. -Select the Group Policy object item in the left pane. +Review the installed roles the domain controller is supporting. -Select the "Delegation" tab in the right pane. +Start "Server Manager". -Select the "Advanced" button. +Select "AD DS" in the left pane and the server name under "Servers" to the right. -Select the "Advanced" button again and then the "Auditing" tab. +Select "Add (or Remove) Roles and Features" from "Tasks" in the "Roles and Features" section. (Cancel before any changes are made.) -If the audit settings for any Group Policy object are not at least as inclusive as those below, this is a finding: +Determine if any additional server roles are installed. A basic domain controller setup will include the following: -Type - Fail -Principal - Everyone -Access - Full Control -Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects +- Active Directory Domain Services +- DNS Server +- File and Storage Services -The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. +If any roles not requiring installation on a domain controller are installed, this is a finding. -Type - Success -Principal - Everyone -Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) -Inherited from - Parent Object -Applies to - Descendant groupPolicyContainer objects +A Domain Name System (DNS) server integrated with the directory server (e.g., AD-integrated DNS) is an acceptable application. However, the DNS server must comply with the DNS STIG security requirements. -Two instances with the following summary information will be listed: +Run "Programs and Features". -Type - Success -Principal - Everyone -Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) -Inherited from - Parent Object -Applies to - Descendant Organization Unit Objects +Review installed applications. + +If any applications are installed that are not required for the domain controller, this is a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000096-GPOS-00050 <GroupDescription></GroupDescription> - - WN19-DC-000180 - Windows Server 2019 Active Directory Domain object must be configured with proper audit settings. - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000330 + Windows Server 2019 must not have the Microsoft FTP service installed unless required by the organization. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select the domain being reviewed in the left pane. - -Right-click the domain name and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -Configure the audit settings for Domain object to include the following: + SV-103507 + V-93421 + CCI-000382 + Uninstall the "FTP Server" role. -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only +Start "Server Manager". -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Select the server with the role. -Two instances with the following summary information will be listed: +Scroll down to "ROLES AND FEATURES" in the right pane. -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - None -Applies to - Special +Select "Remove Roles and Features" from the drop-down "TASKS" list. -Type - Success -Principal - Domain Users -Access - All extended rights -Inherited from - None -Applies to - This object only +Select the appropriate server on the "Server Selection" page and click "Next". -Type - Success -Principal - Administrators -Access - All extended rights -Inherited from - None -Applies to - This object only +Deselect "FTP Server" under "Web Server (IIS)" on the "Roles" page. -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner.) - - - - This applies to domain controllers. It is NA for other systems. +Click "Next" and "Remove" as prompted. + + + + If the server has the role of an FTP server, this is NA. -Review the auditing configuration for the Domain object. +Open "PowerShell". -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +Enter "Get-WindowsFeature | Where Name -eq Web-Ftp-Service". -Ensure "Advanced Features" is selected in the "View" menu. +If "Installed State" is "Installed", this is a finding. -Select the domain being reviewed in the left pane. +An Installed State of "Available" or "Removed" is not a finding. -Right-click the domain name and select "Properties". +If the system has the role of an FTP server, this must be documented with the ISSO. + + + + + SRG-OS-000096-GPOS-00050 + <GroupDescription></GroupDescription> + + WN19-00-000360 + Windows Server 2019 must not have the Telnet Client installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93423 + SV-103509 + CCI-000382 + Uninstall the "Telnet Client" feature. -Select the "Security" tab. +Start "Server Manager". -Select the "Advanced" button and then the "Auditing" tab. +Select the server with the feature. -If the audit settings on the Domain object are not at least as inclusive as those below, this is a finding: +Scroll down to "ROLES AND FEATURES" in the right pane. -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only +Select "Remove Roles and Features" from the drop-down "TASKS" list. -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Select the appropriate server on the "Server Selection" page and click "Next". -Two instances with the following summary information will be listed: +Deselect "Telnet Client" on the "Features" page. -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - None -Applies to - Special +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". -Type - Success -Principal - Domain Users -Access - All extended rights -Inherited from - None -Applies to - This object only +Enter "Get-WindowsFeature | Where Name -eq Telnet-Client". -Type - Success -Principal - Administrators -Access - All extended rights -Inherited from - None -Applies to - This object only +If "Installed State" is "Installed", this is a finding. -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner) +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000104-GPOS-00051 <GroupDescription></GroupDescription> - - WN19-DC-000190 - Windows Server 2019 Active Directory Infrastructure object must be configured with proper audit settings. - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000070 + Windows Server 2019 shared user accounts must not be permitted. + <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 nonrepudiation or individual accountability for system access and resource usage.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + SV-103523 + V-93437 + CCI-000764 + Remove unapproved shared accounts from the system. -Ensure "Advanced Features" is selected in the "View" menu. +Document required shared accounts with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. + + + + Determine whether any shared accounts exist. If no shared accounts exist, this is NA. -Select the domain being reviewed in the left pane. +Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. -Right-click the "Infrastructure" object in the right pane and select "Properties". +If unapproved shared accounts exist, this is a finding. + + + + + SRG-OS-000104-GPOS-00051 + <GroupDescription></GroupDescription> + + WN19-00-000200 + Windows Server 2019 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. 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103525 + V-93439 + CCI-000764 + Configure all enabled accounts to require passwords. -Select the "Security" tab. +The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account. + + + + Review the password required status for enabled user accounts. -Select the "Advanced" button and then the "Auditing" tab. +Open "PowerShell". -Configure the audit settings for Infrastructure object to include the following: +Domain Controllers: -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None +Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) +If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. -Two instances with the following summary information will be listed: +Member servers and standalone systems: -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) - - - - This applies to domain controllers. It is NA for other systems. +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. -Review the auditing configuration for Infrastructure object. +Exclude disabled accounts (e.g., DefaultAccount, Guest). -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. + + + + + SRG-OS-000105-GPOS-00052 + <GroupDescription></GroupDescription> + + WN19-DC-000310 + Windows Server 2019 Active Directory user accounts, including administrators, must be configured to require the use of a Common Access Card (CAC), Personal Identity Verification (PIV)-compliant hardware token, or Alternate Logon Token (ALT) for user authentication. + <VulnDiscussion>Smart cards such as the CAC support a two-factor authentication technique. This provides a higher level of trust in the asserted identity than use of the username and password for authentication. -Ensure "Advanced Features" is selected in the "View" menu. +Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103527 + V-93441 + CCI-000765 + CCI-000766 + CCI-000767 + CCI-000768 + CCI-001948 + Configure all user accounts, including administrator accounts, in Active Directory to enable the option "Smart card is required for interactive logon". -Select the domain being reviewed in the left pane. +Run "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): -Right-click the "Infrastructure" object in the right pane and select "Properties". +Select the OU where the user accounts are located. (By default this is the Users node; however, accounts may be under other organization-defined OUs.) -Select the "Security" tab. +Right-click the user account and select "Properties". -Select the "Advanced" button and then the "Auditing" tab. +Select the "Account" tab. -If the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding: +Check "Smart card is required for interactive logon" in the "Account Options" area. + + + + This applies to domain controllers. It is NA for other systems. -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None +Open "PowerShell". -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Enter the following: -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) +"Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name" +("DistinguishedName" may be substituted for "Name" for more detailed output.) -Two instances with the following summary information will be listed: +If any user accounts, including administrators, are listed, this is a finding. -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) + +Alternately: + +To view sample accounts in "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): + +Select the Organizational Unit (OU) where the user accounts are located. (By default, this is the Users node; however, accounts may be under other organization-defined OUs.) + +Right-click the sample user account and select "Properties". + +Select the "Account" tab. + +If any user accounts, including administrators, do not have "Smart card is required for interactive logon" checked in the "Account Options" area, this is a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000112-GPOS-00057 <GroupDescription></GroupDescription> - - WN19-DC-000200 - Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings. - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + + WN19-DC-000020 + Windows Server 2019 Kerberos user logon restrictions must be enforced. + <VulnDiscussion>This policy setting determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer. The policy is enabled by default, which is the most secure setting for validating that access to target resources is not circumvented. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select the "Domain Controllers OU" under the domain being reviewed in the left pane. - -Right-click the "Domain Controllers OU" object and select "Properties". - -Select the "Security" tab. + V-93443 + SV-103529 + CCI-001941 + CCI-001942 + Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Enforce user logon restrictions" to "Enabled". + + + + This applies to domain controllers. It is NA for other systems. -Select the "Advanced" button and then the "Auditing" tab. +Verify the following is configured in the Default Domain Policy: -Configure the audit settings for Domain Controllers OU object to include the following: +Open "Group Policy Management". -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Right-click on the "Default Domain Policy". -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: all create, delete and modify permissions) +Select "Edit". -Type - Success -Principal - Everyone -Access - Write all properties -Inherited from - None -Applies to - This object and all descendant objects +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. -Two instances with the following summary information will be listed: +If the "Enforce user logon restrictions" is not set to "Enabled", this is a finding. + + + + + SRG-OS-000112-GPOS-00057 + <GroupDescription></GroupDescription> + + WN19-DC-000030 + Windows Server 2019 Kerberos service ticket maximum lifetime must be limited to 600 minutes or less. + <VulnDiscussion>This setting determines the maximum amount of time (in minutes) that a granted session ticket can be used to access a particular service. Session tickets are used only to authenticate new connections with servers. Ongoing operations are not interrupted if the session ticket used to authenticate the connection expires during the connection. -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objects - - - +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103531 + V-93445 + CCI-001942 + CCI-001941 + Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for service ticket" to a maximum of "600" minutes, but not "0", which equates to "Ticket doesn't expire". + + + This applies to domain controllers. It is NA for other systems. -Review the auditing configuration for the Domain Controller OU object. +Verify the following is configured in the Default Domain Policy: -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +Open "Group Policy Management". -Ensure "Advanced Features" is selected in the "View" menu. +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). -Select the "Domain Controllers OU" under the domain being reviewed in the left pane. +Right-click on the "Default Domain Policy". -Right-click the "Domain Controllers OU" object and select "Properties". +Select "Edit". -Select the "Security" tab. +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. -Select the "Advanced" button and then the "Auditing" tab. +If the value for "Maximum lifetime for service ticket" is "0" or greater than "600" minutes, this is a finding. + + + + + SRG-OS-000112-GPOS-00057 + <GroupDescription></GroupDescription> + + WN19-DC-000040 + Windows Server 2019 Kerberos user ticket lifetime must be limited to 10 hours or less. + <VulnDiscussion>In Kerberos, there are two types of tickets: Ticket Granting Tickets (TGTs) and Service Tickets. Kerberos tickets have a limited lifetime so the time an attacker has to implement an attack is limited. This policy controls how long TGTs can be renewed. With Kerberos, the user's initial authentication to the domain controller results in a TGT, which is then used to request Service Tickets to resources. Upon startup, each computer gets a TGT before requesting a service ticket to the domain controller and any other computers it needs to access. For services that start up under a specified user account, users must always get a TGT first and then get Service Tickets to all computers and services accessed. -If the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding: +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93447 + SV-103533 + CCI-001941 + CCI-001942 + Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for user ticket" to a maximum of "10" hours but not "0", which equates to "Ticket doesn't expire". + + + + This applies to domain controllers. It is NA for other systems. -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object and all descendant objects +Verify the following is configured in the Default Domain Policy: -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Open "Group Policy Management". -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: all create, delete and modify permissions) +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). -Type - Success -Principal - Everyone -Access - Write all properties -Inherited from - None -Applies to - This object and all descendant objects +Right-click on the "Default Domain Policy". -Two instances with the following summary information will be listed: +Select "Edit". -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objects +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. + +If the value for "Maximum lifetime for user ticket" is "0" or greater than "10" hours, this is a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000112-GPOS-00057 <GroupDescription></GroupDescription> - - WN19-DC-000210 - Windows Server 2019 Active Directory AdminSDHolder object must be configured with proper audit settings. - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + + WN19-DC-000050 + Windows Server 2019 Kerberos policy user ticket renewal maximum lifetime must be limited to seven days or less. + <VulnDiscussion>This setting determines the period of time (in days) during which a user's Ticket Granting Ticket (TGT) may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + SV-103535 + V-93449 + CCI-001942 + CCI-001941 + Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for user ticket renewal" to a maximum of "7" days or less. + + + + This applies to domain controllers. It is NA for other systems. -Ensure "Advanced Features" is selected in the "View" menu. +Verify the following is configured in the Default Domain Policy: -Select "System" under the domain being reviewed in the left pane. +Open "Group Policy Management". -Right-click the "AdminSDHolder" object in the right pane and select "Properties". +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). -Select the "Security" tab. +Right-click on the "Default Domain Policy". -Select the "Advanced" button and then the "Auditing" tab. +Select "Edit". -Configure the audit settings for AdminSDHolder object to include the following: +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Write all properties, Modify permissions, Modify owner) - -Two instances with the following summary information will be listed: +If the "Maximum lifetime for user ticket renewal" is greater than "7" days, this is a finding. + + + + + SRG-OS-000112-GPOS-00057 + <GroupDescription></GroupDescription> + + WN19-DC-000060 + Windows Server 2019 computer clock synchronization tolerance must be limited to five minutes or less. + <VulnDiscussion>This setting determines the maximum time difference (in minutes) that Kerberos will tolerate between the time on a client's clock and the time on a server's clock while still considering the two clocks synchronous. In order to prevent replay attacks, Kerberos uses timestamps as part of its protocol definition. For timestamps to work properly, the clocks of the client and the server need to be in sync as much as possible. -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objects - - - +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93451 + SV-103537 + CCI-001941 + CCI-001942 + Configure the policy value in the Default Domain Policy for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum tolerance for computer clock synchronization" to a maximum of "5" minutes or less. + + + This applies to domain controllers. It is NA for other systems. -Review the auditing configuration for the "AdminSDHolder" object. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select "System" under the domain being reviewed in the left pane. - -Right-click the "AdminSDHolder" object in the right pane and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. +Verify the following is configured in the Default Domain Policy: -If the audit settings on the "AdminSDHolder" object are not at least as inclusive as those below, this is a finding: +Open "Group Policy Management". -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Right-click on the "Default Domain Policy". -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Write all properties, Modify permissions, Modify owner) +Select "Edit". -Two instances with the following summary information will be listed: +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objects +If the "Maximum tolerance for computer clock synchronization" is greater than "5" minutes, this is a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000118-GPOS-00060 <GroupDescription></GroupDescription> - - WN19-DC-000220 - Windows Server 2019 Active Directory RID Manager$ object must be configured with proper audit settings. - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000190 + Windows Server 2019 outdated or unused accounts must be removed or disabled. + <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, disabled 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select "System" under the domain being reviewed in the left pane. - -Right-click the "RID Manager$" object in the right pane and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -Configure the audit settings for RID Manager$ object to include the following: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None - (Access - Special = Write all properties, All extended rights, Change RID master) - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) - - - - This applies to domain controllers. It is NA for other systems. - -Review the auditing configuration for the "RID Manager$" object. + V-93457 + SV-103543 + CCI-000795 + Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days. + + + + Open "Windows PowerShell". -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +Domain Controllers: -Ensure "Advanced Features" is selected in the "View" menu. +Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" -Select "System" under the domain being reviewed in the left pane. +This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. -Right-click the "RID Manager$" object in the right pane and select "Properties". +Member servers and standalone systems: -Select the "Security" tab. +Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) -Select the "Advanced" button and then the "Auditing" tab. +"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { + $user = ([ADSI]$_.Path) + $lastLogin = $user.Properties.LastLogin.Value + $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 + if ($lastLogin -eq $null) { + $lastLogin = 'Never' + } + Write-Host $user.Name $lastLogin $enabled +}" -If the audit settings on the "RID Manager$" object are not at least as inclusive as those below, this is a finding: +This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). +For example: User1 10/31/2015 5:49:56 AM True -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None +Review the list of accounts returned by the above queries to determine the finding validity for each account reported. -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Exclude the following accounts: -Type - Success -Principal - Everyone -Access - Special -Inherited from - None - (Access - Special = Write all properties, All extended rights, Change RID master) +- Built-in administrator account (Renamed, SID ending in 500) +- Built-in guest account (Renamed, Disabled, SID ending in 501) +- Application accounts -Two instances with the following summary information will be listed: +If any enabled accounts have not been logged on to within the past 35 days, this is a finding. -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) +Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000120-GPOS-00061 <GroupDescription></GroupDescription> - - WN19-DC-000240 - Windows Server 2019 must be configured to audit DS Access - Directory Service Access 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 Directory Service Access records events related to users accessing an Active Directory object. + + WN19-SO-000290 + Windows Server 2019 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites. + <VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Access" with "Success" selected. - - - - This applies to domain controllers. It is NA for other systems. - -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93495 + SV-103581 + CCI-000803 + Configure 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: -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +AES128_HMAC_SHA1 +AES256_HMAC_SHA1 +Future encryption types -Enter "AuditPol /get /category:*" +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\ -If the system does not audit the following, this is a finding. +Value Name: SupportedEncryptionTypes -DS Access >> Directory Service Access - Success +Value Type: REG_DWORD +Value: 0x7ffffff8 (2147483640) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000123-GPOS-00064 <GroupDescription></GroupDescription> - - WN19-DC-000250 - Windows Server 2019 must be configured to audit DS Access - Directory Service Access 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. + + WN19-00-000310 + Windows Server 2019 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours. + <VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. -Audit Directory Service Access records events related to users accessing an Active Directory object. +Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Access" with "Failure" selected. - - - - This applies to domain controllers. It is NA for other systems. + V-92977 + SV-103065 + CCI-001682 + Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours. -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. +Domain accounts can be configured with an account expiration date, under "Account" properties. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. + + + + Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. -Enter "AuditPol /get /category:*" +If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. -Compare the "AuditPol" settings with the following: +Domain Controllers: -If the system does not audit the following, this is a finding. +Open "PowerShell". -DS Access >> Directory Service Access - Failure +Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". + +If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. + +Member servers and standalone systems: + +Open "Command Prompt". + +Run "Net user [username]", where [username] is the name of the emergency account. + +If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000125-GPOS-00065 <GroupDescription></GroupDescription> - - WN19-DC-000260 - Windows Server 2019 must be configured to audit DS Access - Directory Service Changes 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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000470 + Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Changes" with "Success" selected. - - - - This applies to domain controllers. It is NA for other systems. - -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93503 + SV-103589 + CCI-000877 + Configure 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: -Use the "AuditPol" tool to review the current Audit Policy configuration: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Value Name: AllowBasic -Enter "AuditPol /get /category:*" - -Compare the "AuditPol" settings with the following: - -If the system does not audit the following, this is a finding. - -DS Access >> Directory Service Changes - Success +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000125-GPOS-00065 <GroupDescription></GroupDescription> - - WN19-DC-000270 - Windows Server 2019 must be configured to audit DS Access - Directory Service Changes 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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000490 + Windows Server 2019 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. Disallowing Digest authentication will reduce this potential.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Changes" with "Failure" selected. - - - - This applies to domain controllers. It is NA for other systems. - -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + SV-103591 + V-93505 + CCI-000877 + Configure 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: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -If the system does not audit the following, this is a finding. +Value Name: AllowDigest -DS Access >> Directory Service Changes - Failure +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000023-GPOS-00006 + + SRG-OS-000125-GPOS-00065 <GroupDescription></GroupDescription> - - WN19-SO-000130 - Windows Server 2019 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. - -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000500 + Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000048 - CCI-000050 - CCI-001384 - CCI-001385 - CCI-001386 - CCI-001387 - CCI-001388 - Configure 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. - - - + V-93507 + SV-103593 + CCI-000877 + Configure 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 -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ - -Value Name: LegalNoticeText - -Value Type: REG_SZ -Value: See message text below - -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. +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ --This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. +Value Name: AllowBasic --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. +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000023-GPOS-00006 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-SO-000140 - Windows Server 2019 title for legal banner dialog box must be configured with the appropriate text. - <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. - -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000240 + Windows Server 2019 administrator accounts must not be enumerated during elevation. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000048 - CCI-001384 - CCI-001385 - CCI-001386 - CCI-001387 - CCI-001388 - Configure 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 an organization-defined equivalent. - -If an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN19-SO-000150. - - - + V-93517 + SV-103603 + CCI-001084 + Configure 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 -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ - -Value Name: LegalNoticeCaption - -Value Type: REG_SZ -Value: See message title options below - -"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ -If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. +Value Name: EnumerateAdministrators -Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required. +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000062-GPOS-00031 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-SO-000050 - Windows Server 2019 must force audit policy subcategory settings to override audit policy category settings. - <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></IAControls> + + WN19-SO-000390 + Windows Server 2019 UIAccess applications must not be allowed to prompt for elevation without using 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 prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000169 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93521 + SV-103607 + CCI-001084 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" to "Disabled". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\Lsa\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: SCENoApplyLegacyAuditPolicy +Value Name: EnableUIADesktopToggle Value Type: REG_DWORD -Value: 0x00000001 (1) +Value: 0x00000000 (0) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-AU-000070 - Windows Server 2019 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></IAControls> + + WN19-SO-000400 + Windows Server 2019 User Account Control must, at a 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: + SV-103609 + V-93523 + CCI-001084 + Configure 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". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +The more secure option for this setting, "Prompt for credentials on the secure desktop", would also be acceptable. + + + + UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). -Enter "AuditPol /get /category:*" +If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -If the system does not audit the following, this is a finding. +Value Name: ConsentPromptBehaviorAdmin -Account Logon >> Credential Validation - Success +Value Type: REG_DWORD +Value: 0x00000002 (2) (Prompt for consent on the secure desktop) +0x00000001 (1) (Prompt for credentials on the secure desktop) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-AU-000080 - Windows Server 2019 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></IAControls> + + WN19-SO-000420 + Windows Server 2019 User 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + SV-103611 + V-93525 + CCI-001084 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -Enter "AuditPol /get /category:*" +If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -If the system does not audit the following, this is a finding. +Value Name: EnableInstallerDetection -Account Logon >> Credential Validation - Failure +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000474-GPOS-00219 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-AU-000130 - Windows Server 2019 must be configured to audit Detailed Tracking - Plug and Play 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. - -Plug and Play activity records events related to the successful connection of external devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000430 + Windows Server 2019 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations. + <VulnDiscussion>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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> "Audit PNP Activity" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + V-93527 + SV-103613 + CCI-001084 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -Enter "AuditPol /get /category:*" +If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -If the system does not audit the following, this is a finding. +Value Name: EnableSecureUIAPaths -Detailed Tracking >> Plug and Play Events - Success +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-AU-000170 - Windows Server 2019 must be configured to audit Logon/Logoff - Group Membership 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 Group Membership records information related to the group membership of a user's logon token.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000450 + Windows Server 2019 User Account Control (UAC) must virtualize file and registry write failures to per-user locations. + <VulnDiscussion>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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Group Membership" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + V-93529 + SV-103615 + CCI-001084 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -Enter "AuditPol /get /category:*" +If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -If the system does not audit the following, this is a finding. +Value Name: EnableVirtualization -Logon/Logoff >> Group Membership - Success +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000138-GPOS-00069 <GroupDescription></GroupDescription> - - WN19-AU-000210 - Windows Server 2019 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 that have administrative privileges and can be used to elevate processes. - -Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000230 + Windows Server 2019 non-system-created file shares must limit access to groups that require it. + <VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103617 + V-93531 + CCI-001090 + If a non-system-created share is required on a system, configure the share and NTFS permissions to limit access to the specific groups or accounts that require it. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Remove any unnecessary non-system-created shares. + + + + If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Run "Computer Management". -Enter "AuditPol /get /category:*" +Navigate to System Tools >> Shared Folders >> Shares. -Compare the "AuditPol" settings with the following: +Right-click any non-system-created shares. -If the system does not audit the following, this is a finding. +Select "Properties". -Logon/Logoff >> Special Logon - Success +Select the "Share Permissions" tab. + +If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. + +Select the "Security" tab. + +If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000138-GPOS-00069 <GroupDescription></GroupDescription> - - WN19-AU-000220 - Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. + + WN19-CC-000350 + Windows Server 2019 Remote Desktop Services must prevent drive redirection. + <VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103619 + V-93533 + CCI-001090 + Configure 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: -Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: fDisableCdm + +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000138-GPOS-00069 + <GroupDescription></GroupDescription> + + WN19-DC-000120 + Windows Server 2019 data files owned by users must be on a different logical partition from the directory server data files. + <VulnDiscussion>When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. + +The directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93535 + SV-103621 + CCI-001090 + Move shares used to store files owned by users to a different logical partition than the directory server data files. + + + + This applies to domain controllers. It is NA for other systems. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Run "Regedit". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". -Enter "AuditPol /get /category:*" +Note the directory locations in the values for "DSA Database file". -Compare the "AuditPol" settings with the following: +Open "Command Prompt". -If the system does not audit the following, this is a finding. +Enter "net share". -Object Access >> Other Object Access Events - Success +Note the logical drive(s) or file system partition for any organization-created data shares. + +Ignore system shares (e.g., NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) should not be ignored. + +If user shares are located on the same logical partition as the directory server data files, this is a finding. - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000138-GPOS-00069 <GroupDescription></GroupDescription> - - WN19-AU-000230 - Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. - -Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000230 + Windows Server 2019 must not allow anonymous enumeration of shares. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93537 + SV-103623 + CCI-001090 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Use the "AuditPol" tool to review the current Audit Policy configuration: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Value Name: RestrictAnonymous -Enter "AuditPol /get /category:*" +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000138-GPOS-00069 + <GroupDescription></GroupDescription> + + WN19-SO-000250 + Windows Server 2019 must restrict anonymous access to Named Pipes and Shares. + <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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93539 + SV-103625 + CCI-001090 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -If the system does not audit the following, this is a finding. +Value Name: RestrictNullSessAccess -Object Access >> Other Object Access Events - Failure +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000474-GPOS-00219 + + SRG-OS-000163-GPOS-00072 <GroupDescription></GroupDescription> - - WN19-AU-000240 - Windows Server 2019 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. - -Removable Storage auditing under Object Access 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></IAControls> + + WN19-DC-000160 + Windows Server 2019 directory service must be configured to terminate LDAP-based network connections to the directory server after five minutes of inactivity. + <VulnDiscussion>The failure to terminate inactive network connections increases the risk of a successful attack on the directory server. The longer an established session is in progress, the more time an attacker has to hijack the session, implement a means to passively intercept data, or compromise any protections on client access. For example, if an attacker gains control of a client computer, an existing (already authenticated) session with the directory server could allow access to the directory. The lack of confidentiality protection in LDAP-based sessions increases exposure to this vulnerability.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103595 + V-93509 + CCI-001133 + Configure the directory service to terminate LDAP-based network connections to the directory server after 5 minutes of inactivity. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Open an elevated "Command prompt" (run as administrator). -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Enter "ntdsutil". -Enter "AuditPol /get /category:*" +At the "ntdsutil:" prompt, enter "LDAP policies". -Compare the "AuditPol" settings with the following: +At the "ldap policy:" prompt, enter "connections". -If the system does not audit the following, this is a finding. +At the "server connections:" prompt, enter "connect to server [host-name]" (where [host-name] is the computer name of the domain controller). -Object Access >> Removable Storage - Success +At the "server connections:" prompt, enter "q". -Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. +At the "ldap policy:" prompt, enter "Set MaxConnIdleTime to 300". + +Enter "Commit Changes" to save. + +Enter "Show values" to verify changes. + +Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit. + + + + This applies to domain controllers. It is NA for other systems. + +Open an elevated "Command Prompt" (run as administrator). + +Enter "ntdsutil". + +At the "ntdsutil:" prompt, enter "LDAP policies". + +At the "ldap policy:" prompt, enter "connections". + +At the "server connections:" prompt, enter "connect to server [host-name]" +(where [host-name] is the computer name of the domain controller). + +At the "server connections:" prompt, enter "q". + +At the "ldap policy:" prompt, enter "show values". + +If the value for MaxConnIdleTime is greater than "300" (5 minutes) or is not specified, this is a finding. + +Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit. + +Alternately, Dsquery can be used to display MaxConnIdleTime: + +Open "Command Prompt (Admin)". +Enter the following command (on a single line). + +dsquery * "cn=Default Query Policy,cn=Query-Policies,cn=Directory Service, cn=Windows NT,cn=Services,cn=Configuration,dc=[forest-name]" -attr LDAPAdminLimits + +The quotes are required and dc=[forest-name] is the fully qualified LDAP name of the domain being reviewed (e.g., dc=disaost,dc=mil). + +If the results do not specify a "MaxConnIdleTime" or it has a value greater than "300" (5 minutes), this is a finding. - - SRG-OS-000474-GPOS-00219 + + SRG-OS-000185-GPOS-00079 <GroupDescription></GroupDescription> - - WN19-AU-000250 - Windows Server 2019 must be configured to audit Object Access - Removable Storage failures. + + WN19-00-000250 + Windows Server 2019 systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. + <VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. + +Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). + +Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93515 + SV-103601 + CCI-001199 + CCI-002475 + CCI-002476 + Configure systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data to employ encryption to protect the confidentiality and integrity of all information at rest. + + + + Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. + +If they do not, this is a finding. + + + + + SRG-OS-000191-GPOS-00080 + <GroupDescription></GroupDescription> + + WN19-00-000290 + Windows Server 2019 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Host Based Security System (HBSS) is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). + <VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103653 + V-93567 + CCI-001233 + Install a DoD-approved ESS software and ensure it is operating continuously. + + + + Verify DoD-approved ESS software is installed and properly operating. Ask the site ISSM for documentation of the ESS software installation and configuration. + +If the ISSM is not able to provide a documented configuration for an installed ESS or if the ESS software is not properly maintained or used, this is a finding. + +Note: Example of documentation can be a copy of the site's CCB approved Software Baseline with version of software noted or a memo from the ISSM stating current ESS software and version. + + + + + SRG-OS-000240-GPOS-00090 + <GroupDescription></GroupDescription> + + WN19-AU-000150 + Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. -Removable Storage auditing under Object Access 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></IAControls> +Account Lockout events can be used to identify potentially malicious logon attempts. + +Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure 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. - - - + SV-103075 + V-92987 + CCI-001404 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -6181,36 +6339,36 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Object Access >> Removable Storage - Failure - -Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. +Logon/Logoff >> Account Lockout - Success - - SRG-OS-000472-GPOS-00217 + + SRG-OS-000240-GPOS-00090 <GroupDescription></GroupDescription> - - WN19-AU-000180 - Windows Server 2019 must be configured to audit logoff successes. + + WN19-AU-000160 + Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. -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. +Account Lockout events can be used to identify potentially malicious logon attempts. -Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Logoff" with "Success" selected. - - - + V-92989 + SV-103077 + CCI-000172 + CCI-001404 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -6223,7591 +6381,8193 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Logoff - Success +Logon/Logoff >> Account Lockout - Failure - - SRG-OS-000042-GPOS-00020 + + SRG-OS-000257-GPOS-00098 <GroupDescription></GroupDescription> - - WN19-CC-000090 - Windows Server 2019 command 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. + + WN19-AU-000060 + Windows Server 2019 Event Viewer must be protected from unauthorized modification and deletion. + <VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. -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> +Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. + +Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000135 - Configure 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: + SV-103283 + V-93195 + CCI-001494 + CCI-001495 + Configure the permissions on the "Eventvwr.exe" file to prevent modification by any groups or accounts other than TrustedInstaller. The default permissions listed below satisfy this requirement: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute -Value Name: ProcessCreationIncludeCmdLine_Enabled +The default location is the "%SystemRoot%\System32" folder. + + + + Navigate to "%SystemRoot%\System32". -Value Type: REG_DWORD -Value: 0x00000001 (1) +View the permissions on "Eventvwr.exe". + +If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. + +The default permissions below satisfy this requirement: + +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute - - SRG-OS-000042-GPOS-00020 + + SRG-OS-000312-GPOS-00122 <GroupDescription></GroupDescription> - - WN19-CC-000460 - Windows Server 2019 PowerShell script block logging 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. + + WN19-00-000140 + Windows Server 2019 permissions for the system drive root directory (usually C:\) 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. -Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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> +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000135 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> "Turn on PowerShell Script Block Logging" to "Enabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93019 + SV-103107 + CCI-002165 + Maintain the default permissions for the system drive's root directory and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ +Default Permissions +C:\ +Type - "Allow" for all +Inherited from - "None" for all -Value Name: EnableScriptBlockLogging +Principal - Access - Applies to -Value Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000341-GPOS-00132 - <GroupDescription></GroupDescription> - - WN19-CC-000270 - Windows Server 2019 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001849 - Configure 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 write events directly to an audit server, this is NA. +SYSTEM - Full control - This folder, subfolders, and files +Administrators - Full control - This folder, subfolders, and files +Users - Read & execute - This folder, subfolders, and files +Users - Create folders/append data - This folder and subfolders +Users - Create files/write data - Subfolders only +CREATOR OWNER - Full Control - Subfolders and files only + + + + The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). -If the following registry value does not exist or is not configured as specified, this is a finding: +Review the permissions for the system drive's root directory (usually C:\). 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. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Application\ +If permissions are not as restrictive as the default permissions listed below, this is a finding. -Value Name: MaxSize +Viewing in File Explorer: -Type: REG_DWORD -Value: 0x00008000 (32768) (or greater) - - - - - SRG-OS-000341-GPOS-00132 - <GroupDescription></GroupDescription> - - WN19-CC-000280 - Windows Server 2019 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001849 - Configure 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 write events directly to an audit server, this is NA. +View the Properties of the system drive's root directory. -If the following registry value does not exist or is not configured as specified, this is a finding: +Select the "Security" tab, and the "Advanced" button. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\ +Default permissions: +C:\ +Type - "Allow" for all +Inherited from - "None" for all -Value Name: MaxSize +Principal - Access - Applies to -Type: REG_DWORD -Value: 0x00030000 (196608) (or greater) - - - - - SRG-OS-000341-GPOS-00132 - <GroupDescription></GroupDescription> - - WN19-CC-000290 - Windows Server 2019 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001849 - Configure 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 write events directly to an audit server, this is NA. +SYSTEM - Full control - This folder, subfolders, and files +Administrators - Full control - This folder, subfolders, and files +Users - Read & execute - This folder, subfolders, and files +Users - Create folders/append data - This folder and subfolders +Users - Create files/write data - Subfolders only +CREATOR OWNER - Full Control - Subfolders and files only -If the following registry value does not exist or is not configured as specified, this is a finding: +Alternately, use icacls: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\ +Open "Command Prompt (Admin)". -Value Name: MaxSize +Enter "icacls" followed by the directory: -Type: REG_DWORD -Value: 0x00008000 (32768) (or greater) - - - - - SRG-OS-000342-GPOS-00133 - <GroupDescription></GroupDescription> - - WN19-AU-000010 - Windows Server 2019 audit records must be backed up to a different system or media than the system being audited. - <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001851 - Establish and implement a process for backing up log data to another system or media other than the system being audited. - - - - Determine if a process to back up log data to a different system or media than the system being audited has been implemented. +"icacls c:\" -If it has not, this is a finding. - - - - - SRG-OS-000479-GPOS-00224 - <GroupDescription></GroupDescription> - - WN19-AU-000020 - Windows Server 2019 must, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly. - <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001851 - Configure the system to, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly. - - - - Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. +The following results should be displayed: -If they are not, this is a finding. +c:\ +NT AUTHORITY\SYSTEM:(OI)(CI)(F) +BUILTIN\Administrators:(OI)(CI)(F) +BUILTIN\Users:(OI)(CI)(RX) +BUILTIN\Users:(CI)(AD) +BUILTIN\Users:(CI)(IO)(WD) +CREATOR OWNER:(OI)(CI)(IO)(F) +Successfully processed 1 files; Failed processing 0 files - - SRG-OS-000355-GPOS-00143 + + SRG-OS-000312-GPOS-00122 <GroupDescription></GroupDescription> - - WN19-00-000440 - The Windows Server 2019 time service must synchronize with an appropriate DoD time source. - <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> + + WN19-00-000150 + Windows Server 2019 permissions for program file 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. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001891 - Configure the system to synchronize time with an appropriate DoD time source. + V-93021 + SV-103109 + CCI-002165 + Maintain the default permissions for the program file directories and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). -Domain-joined systems use NT5DS to synchronize time from other systems in the domain by default. +Default permissions: +\Program Files and \Program Files (x86) +Type - "Allow" for all +Inherited from - "None" for all -If 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 appropriate DoD time server. +Principal - Access - Applies to -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. - - - - Review the Windows time service configuration. +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + + + + The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). -Open an elevated "Command Prompt" (run as administrator). +Review the permissions for the program file directories (Program Files and Program Files [x86]). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. -Enter "W32tm /query /configuration". +If permissions are not as restrictive as the default permissions listed below, this is a finding. -Domain-joined systems (excluding the domain controller with the PDC emulator role): +Viewing in File Explorer: -If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. +For each folder, view the Properties. -Other systems: +Select the "Security" tab, and the "Advanced" button. -If systems are configured with a "Type" of "NTP", including standalone systems and the domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. +Default permissions: +\Program Files and \Program Files (x86) +Type - "Allow" for all +Inherited from - "None" for all -To determine the domain controller with the PDC Emulator role: +Principal - Access - Applies to -Open "PowerShell". +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files -Enter "Get-ADDomain | FT PDCEmulator". +Alternately, use icacls: + +Open a Command prompt (admin). + +Enter "icacls" followed by the directory: + +'icacls "c:\program files"' +'icacls "c:\program files (x86)"' + +The following results should be displayed for each when entered: + +c:\program files (c:\program files (x86)) +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) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +Successfully processed 1 files; Failed processing 0 files - - SRG-OS-000057-GPOS-00027 + + SRG-OS-000312-GPOS-00122 <GroupDescription></GroupDescription> - - WN19-AU-000030 - Windows Server 2019 permissions 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. + + WN19-00-000160 + Windows Server 2019 permissions for the Windows installation directory 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. -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000162 - CCI-000163 - CCI-000164 - Configure the permissions on the Application event log file (Application.evtx) to prevent access by non-privileged accounts. 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" folder. - -If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". - - - - Navigate to the Application event log file. + SV-103111 + V-93023 + CCI-002165 + Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. +Default permissions: +Type - "Allow" for all +Inherited from - "None" for all -If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: +Principal - Access - Applies to -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control - - - - - SRG-OS-000057-GPOS-00027 - <GroupDescription></GroupDescription> - - WN19-AU-000040 - Windows Server 2019 permissions 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. +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + + + + The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000162 - CCI-000163 - CCI-000164 - Configure the permissions on the Security event log file (Security.evtx) to prevent access by non-privileged accounts. The default permissions listed below satisfy this requirement: +Review the permissions for the Windows installation directory (usually C:\Windows). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control +If permissions are not as restrictive as the default permissions listed below, this is a finding: -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. +Viewing in File Explorer: -If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". - - - - Navigate to the Security event log file. +For each folder, view the Properties. -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. +Select the "Security" tab and the "Advanced" button. -If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: +Default permissions: +\Windows +Type - "Allow" for all +Inherited from - "None" for all -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + +Alternately, use icacls: + +Open a Command prompt (admin). + +Enter "icacls" followed by the directory: + +"icacls c:\windows" + +The following results should be displayed for each when entered: + +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) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +Successfully processed 1 files; Failed processing 0 files - - SRG-OS-000057-GPOS-00027 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-AU-000050 - Windows Server 2019 permissions 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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000170 + Windows Server 2019 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained. + <VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000162 - CCI-000163 - CCI-000164 - Configure the permissions on the System event log file (System.evtx) to prevent access by non-privileged accounts. The default permissions listed below satisfy this requirement: + SV-103113 + V-93025 + CCI-002235 + Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive. -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control +The default permissions of the higher-level keys are noted below. -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. +HKEY_LOCAL_MACHINE\SECURITY -If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". - - - - Navigate to the System event log file. +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +SYSTEM - Full Control - This key and subkeys +Administrators - Special - This key and subkeys -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. +HKEY_LOCAL_MACHINE\SOFTWARE -If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - This key and subkeys +ALL APPLICATION PACKAGES - Read - This key and subkeys -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control - - - - - SRG-OS-000257-GPOS-00098 - <GroupDescription></GroupDescription> - - WN19-AU-000060 - Windows Server 2019 Event Viewer must be protected from unauthorized modification and deletion. - <VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. +HKEY_LOCAL_MACHINE\SYSTEM -Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - Subkeys only +ALL APPLICATION PACKAGES - Read - This key and subkeys -Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001494 - CCI-001495 - Configure the permissions on the "Eventvwr.exe" file to prevent modification by any groups or accounts other than TrustedInstaller. The default permissions listed below satisfy this requirement: +Microsoft has also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID. +S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 + + + + Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. -TrustedInstaller - Full Control -Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute +If any non-privileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. -The default location is the "%SystemRoot%\System32" folder. - - - - Navigate to "%SystemRoot%\System32". +If permissions are not as restrictive as the default permissions listed below, this is a finding: -View the permissions on "Eventvwr.exe". +Run "Regedit". -If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. +Right-click on the registry areas noted below. -The default permissions below satisfy this requirement: +Select "Permissions" and the "Advanced" button. -TrustedInstaller - Full Control -Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute - - - - - SRG-OS-000362-GPOS-00149 - <GroupDescription></GroupDescription> - - WN19-CC-000420 - Windows Server 2019 must prevent users 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001812 - Configure 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: +HKEY_LOCAL_MACHINE\SECURITY -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +SYSTEM - Full Control - This key and subkeys +Administrators - Special - This key and subkeys -Value Name: EnableUserControl +HKEY_LOCAL_MACHINE\SOFTWARE -Type: REG_DWORD -Value: 0x00000000 (0) +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - This key and subkeys +ALL APPLICATION PACKAGES - Read - This key and subkeys + +HKEY_LOCAL_MACHINE\SYSTEM + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - Subkeys only +ALL APPLICATION PACKAGES - Read - This key and subkeys + +Other examples under the noted keys may also be sampled. There may be some instances where non-privileged groups have greater than Read permission. + +Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID, this is currently not a finding. +S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 + +If the defaults have not been changed, these are not a finding. - - SRG-OS-000362-GPOS-00149 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-CC-000430 - Windows Server 2019 must disable the Windows Installer Always install with elevated privileges option. - <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></IAControls> + + WN19-DC-000010 + Windows Server 2019 must only allow administrators responsible for the domain controller to 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 using only accounts with the minimum level of authority necessary. + +Standard user accounts must not be members of the built-in 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001812 - Configure 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: + SV-103115 + V-93027 + CCI-002235 + Configure the Administrators group to include only administrator groups or accounts that are responsible for the system. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ +Remove any standard user accounts. + + + + This applies to domain controllers. A separate version applies to other systems. -Value Name: AlwaysInstallElevated +Review the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group. -Type: REG_DWORD -Value: 0x00000000 (0) +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. + +If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding. - - SRG-OS-000363-GPOS-00150 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-00-000220 - Windows Server 2019 system files must be monitored for unauthorized changes. - <VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code 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> + + WN19-DC-000070 + Windows Server 2019 permissions on the Active Directory data files must only allow System and Administrators access. + <VulnDiscussion>Improper access permissions for directory data-related files could allow unauthorized users to read, modify, or delete directory data or audit trails.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001744 - Monitor the system for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools. - - - - Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. + SV-103117 + V-93029 + CCI-002235 + Maintain the permissions on NTDS database and log files as follows: -If system files are not monitored for unauthorized changes, this is a finding. +NT AUTHORITY\SYSTEM:(I)(F) +BUILTIN\Administrators:(I)(F) -A properly configured HBSS Policy Auditor 5.2 or later File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. The Asset module within HBSS does not meet this requirement. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-00-000030 - Windows Server 2019 administrative accounts must 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 account. +(I) - permission inherited from parent container +(F) - full access + + + + This applies to domain controllers. It is NA for other systems. -Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to not access the Internet or use applications such as email. +Run "Regedit". -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. +Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". -Whitelisting can be used to enforce the policy to ensure compliance.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. Ensure the policy is enforced. +Note the directory locations in the values for: -The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. - - - - Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. +Database log files path +DSA Database file -If it does not, this is a finding. +By default, they will be \Windows\NTDS. -The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-00-000040 - Windows Server 2019 members 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions. - - - - If no accounts are members of the Backup Operators group, this is NA. +If the locations are different, the following will need to be run for each. -Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. +Open "Command Prompt (Admin)". -If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding. +Navigate to the NTDS directory (\Windows\NTDS by default). + +Run "icacls *.*". + +If the permissions on each file are not as restrictive as the following, this is a finding: + +NT AUTHORITY\SYSTEM:(I)(F) +BUILTIN\Administrators:(I)(F) + +(I) - permission inherited from parent container +(F) - full access - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-00-000060 - Windows Server 2019 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization. - <VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account passwords.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000080 + Windows Server 2019 Active Directory SYSVOL directory must have the proper access control permissions. + <VulnDiscussion>Improper access permissions for directory data files could allow unauthorized users to read, modify, or delete directory data. + +The SYSVOL directory contains public files (to the domain) such as policies and logon scripts. Data in shared subdirectories are replicated to all domain controllers in a 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization. - -It is recommended that system-managed service accounts be used whenever possible. - - - - Determine if manually managed application/service accounts exist. If none exist, this is NA. + V-93031 + SV-103119 + CCI-002235 + Maintain the permissions on the SYSVOL directory. Do not allow greater than "Read & execute" permissions for standard user accounts or groups. The defaults below meet this requirement: -If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. +C:\Windows\SYSVOL +Type - "Allow" for all +Inherited from - "None" for all -Identify manually managed application/service accounts. +Principal - Access - Applies to -To determine the date a password was last changed: +Authenticated Users - Read & execute - This folder, subfolder, and files +Server Operators - Read & execute- This folder, subfolder, and files +Administrators - Special - This folder only (Special = Basic Permissions: all selected except Full control) +CREATOR OWNER - Full control - Subfolders and files only +Administrators - Full control - Subfolders and files only +SYSTEM - Full control - This folder, subfolders, and files + + + + This applies to domain controllers. It is NA for other systems. -Domain controllers: +Open a command prompt. -Open "PowerShell". +Run "net share". -Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. +Make note of the directory location of the SYSVOL share. -If the "PasswordLastSet" date is more than one year old, this is a finding. +By default, this will be \Windows\SYSVOL\sysvol. For this requirement, permissions will be verified at the first SYSVOL directory level. +If any standard user accounts or groups have greater than "Read & execute" permissions, this is a finding. -Member servers and standalone systems: +The default permissions noted below meet this requirement: Open "Command Prompt". -Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. +Run "icacls c:\Windows\SYSVOL". -If the "Password Last Set" date is more than one year old, this is a finding. +The following results should be displayed: + +NT AUTHORITY\Authenticated Users:(RX) +NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(GR,GE) +BUILTIN\Server Operators:(RX) +BUILTIN\Server Operators:(OI)(CI)(IO)(GR,GE) +BUILTIN\Administrators:(M,WDAC,WO) +BUILTIN\Administrators:(OI)(CI)(IO)(F) +NT AUTHORITY\SYSTEM:(F) +NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) +CREATOR OWNER:(OI)(CI)(IO)(F) + +(RX) - Read & execute + +Run "icacls /help" to view definitions of other permission codes. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-DC-000430 - The password for the krbtgt account on a domain must be reset at least every 180 days. - <VulnDiscussion>The krbtgt account acts as a service account for the Kerberos Key Distribution Center (KDC) service. The account and password are created when a domain is created and the password is typically not changed. If the krbtgt account is compromised, attackers can create valid Kerberos Ticket Granting Tickets (TGT). + + WN19-DC-000090 + Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions. + <VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems relying on the directory service. -The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and the amount of time equal to or greater than the maximum Kerberos ticket lifetime, and changing again reduces the risk of issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +For Active Directory (AD), the Group Policy objects require special attention. In a distributed administration model (i.e., help desk), Group Policy objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for Group Policy objects, this could allow an intruder to change the security policy applied to all domain client computers (workstations and servers).</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Reset the password for the krbtgt account a least every 180 days. The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and changing again reduces the risk of issues. Changing twice in rapid succession forces clients to re-authenticate (including application services) but is desired if a compromise is suspected. - -PowerShell scripts are available to accomplish this such as at the following link: + V-93033 + SV-103121 + CCI-002235 + Maintain the permissions on Group Policy objects to not allow greater than "Read" and "Apply group policy" for standard user accounts or groups. The default permissions below meet this requirement: -https://gallery.technet.microsoft.com/Reset-the-krbtgt-account-581a9e51 +Authenticated Users - Read, Apply group policy, Special permissions -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +The special permissions for Authenticated Users are for Read-type Properties. -Select "Advanced Features" in the "View" menu if not previously selected. +CREATOR OWNER - Special permissions +SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions +Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions -Select the "Users" node. +Document any other access permissions that allow the objects to be updated with the ISSO. -Right click on the krbtgt account and select "Reset password" +The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on created Group Policy objects. + + + + This applies to domain controllers. It is NA for other systems. -Enter a password that meets password complexity requirements. +Review the permissions on Group Policy objects. -Clear the "User must change password at next logon" check box. +Open "Group Policy Management" (available from various menus or run "gpmc.msc"). -The system will automatically change this to a system-generated complex password. - - - - This requirement is applicable to domain controllers; it is NA for other systems. +Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). -Open "Windows PowerShell". +For each Group Policy object: -Enter "Get-ADUser krbtgt -Property PasswordLastSet". +Select the Group Policy object item in the left pane. -If the "PasswordLastSet" date is more than 180 days old, this is a finding. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-00-000090 - Windows Server 2019 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use. - <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.) +Select the "Delegation" tab in the right pane. -The TPM must be enabled in the firmware. +Select the "Advanced" button. -Run "tpm.msc" for configuration options in Windows. - - - - For standalone systems, this is NA. +Select each Group or user name. -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. +View the permissions. -Verify the system has a TPM and it is ready for use. +If any standard user accounts or groups have "Allow" permissions greater than "Read" and "Apply group policy", this is a finding. -Run "tpm.msc". +Other access permissions that allow the objects to be updated are considered findings unless specifically documented by the ISSO. -Review the sections in the center pane. +The default permissions noted below satisfy this requirement. -"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". +The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next "Advanced" button, the desired Permission entry, and the "Edit" button. -TPM Manufacturer Information - Specific Version = 2.0 or 1.2 +Authenticated Users - Read, Apply group policy, Special permissions -If a TPM is not found or is not ready for use, this is a finding. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-00-000100 - Windows Server 2019 must be maintained at a supported servicing level. - <VulnDiscussion>Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Update the system to a Version 1809 (Build 17763.xxx) or greater. - - - - Open "Command Prompt". +The special permissions for Authenticated Users are for Read-type Properties. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. -Enter "winver.exe". +The special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties: -If the "About Windows" dialog box does not display "Microsoft Windows Server Version 1809 (Build 17763.xxx)" or greater, this is a finding. +CREATOR OWNER - Special permissions +SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions +Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions -Preview versions must not be used in a production environment. +The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on organization created Group Policy objects. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-00-000110 - Windows Server 2019 must use an anti-virus program. - <VulnDiscussion>Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Install an anti-virus solution on the system. - - - - Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution. + + WN19-DC-000100 + Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions. + <VulnDiscussion>When Active Directory objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. -If there is no anti-virus solution installed on the system, this is a finding. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-00-000120 - Windows Server 2019 must have a host-based intrusion detection or prevention system. - <VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +The Domain Controllers OU object requires special attention as the Domain Controllers are central to the configuration and management of the domain. Inappropriate access permissions defined for the Domain Controllers OU could allow an intruder or unauthorized personnel to make changes that could lead to the compromise of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Install a HIDS or HIPS on each server. - - - - Determine whether there is a HIDS or HIPS on each server. + V-93035 + SV-103123 + CCI-002235 + Limit the permissions on the Domain Controllers OU to restrict changes to System, Domain Admins, Enterprise Admins and Administrators. -If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. +The default permissions listed below satisfy this requirement. -A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. +Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions. -If a HIDS is not installed on the system, this is a finding. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-00-000240 - Windows Server 2019 must have software certificate installation files removed. - <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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Remove any certificate installation files (*.p12 and *.pfx) found on a system. +CREATOR OWNER - Special permissions -Note: This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. - - - - Search all drives for *.p12 and *.pfx files. +SELF - Special permissions -If any files with these extensions exist, this is a finding. +Authenticated Users - Read, Special permissions -This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. 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. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-00-000420 - Windows Server 2019 FTP servers must be configured to prevent anonymous logons. - <VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. +The special permissions for Authenticated Users are Read types. -Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure the FTP service to prevent anonymous logons. +SYSTEM - Full Control -Open "Internet Information Services (IIS) Manager". +Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions -Select the server. +Enterprise Admins - Full Control -Double-click "FTP Authentication". +Key Admins - Special permissions -Select "Anonymous Authentication". +Enterprise Key Admins - Special permissions -Select "Disabled" under "Actions". - - - - If FTP is not installed on the system, this is NA. +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions -Open "Internet Information Services (IIS) Manager". +Pre-Windows 2000 Compatible Access - Special permissions -Select the server. +The special permissions for Pre-Windows 2000 Compatible Access are Read types. -Double-click "FTP Authentication". +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions + + + + This applies to domain controllers. It is NA for other systems. -If the "Anonymous Authentication" status is "Enabled", this is a finding. +Review the permissions on the Domain Controllers OU. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Select "Advanced Features" in the "View" menu if not previously selected. + +Select the "Domain Controllers" OU (folder in folder icon). + +Right-click and select "Properties". + +Select the "Security" tab. + +If the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding. + +The default permissions listed below satisfy this requirement. + +Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions and are not a finding. + +The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "View" or "Edit" button. + +Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. + +CREATOR OWNER - Special permissions + +SELF - Special permissions + +Authenticated Users - Read, Special permissions + +The special permissions for Authenticated Users are Read types. + +If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +SYSTEM - Full Control + +Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Enterprise Admins - Full Control + +Key Admins - Special permissions + +Enterprise Key Admins - Special permissions + +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Pre-Windows 2000 Compatible Access - Special permissions + +The Special permissions for Pre-Windows 2000 Compatible Access are Read types. + +If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-00-000430 - Windows Server 2019 FTP servers must be configured to prevent access to the system drive. - <VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000110 + Windows Server 2019 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions. + <VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. + +For Active Directory, the OU objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a denial of service (DoS) to authorized users.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system. - - - - If FTP is not installed on the system, this is NA. + SV-103125 + V-93037 + CCI-002235 + Maintain the Allow type permissions on domain-defined OUs to be at least as restrictive as the defaults below. -Open "Internet Information Services (IIS) Manager". +Document any additional permissions above Read with the ISSO if an approved distributed administration model (help desk or other user support staff) is implemented. -Select "Sites" under the server name. +CREATOR OWNER - Special permissions -For any sites with a Binding that lists FTP, right-click the site and select "Explore". +Self - Special permissions -If the site is not defined to a specific folder for shared FTP resources, this is a finding. +Authenticated Users - Read, Special permissions -If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding. +The special permissions for Authenticated Users are Read type. + +SYSTEM - Full Control + +Domain Admins - Full Control + +Enterprise Admins - Full Control + +Key Admins - Special permissions + +Enterprise Key Admins - Special permissions + +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Pre-Windows 2000 Compatible Access - Special permissions + +The special permissions for Pre-Windows 2000 Compatible Access are for Read types. + +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions + + + + This applies to domain controllers. It is NA for other systems. + +Review the permissions on domain-defined OUs. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +For each OU that is defined (folder in folder icon) excluding the Domain Controllers OU: + +Right-click the OU and select "Properties". + +Select the "Security" tab. + +If the Allow type permissions on the OU are not at least as restrictive as those below, this is a finding. + +The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "Edit" or "View" button. + +Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. + +CREATOR OWNER - Special permissions + +Self - Special permissions + +Authenticated Users - Read, Special permissions + +The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +SYSTEM - Full Control + +Domain Admins - Full Control + +Enterprise Admins - Full Control + +Key Admins - Special permissions + +Enterprise Key Admins - Special permissions + +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Pre-Windows 2000 Compatible Access - Special permissions + +The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions + +If an ISSO-approved distributed administration model (help desk or other user support staff) is implemented, permissions above Read may be allowed for groups documented by the ISSO. + +If any OU with improper permissions includes identification or authentication data (e.g., accounts, passwords, or password hash data) used by systems to determine access control, the severity is CAT I (e.g., OUs that include user accounts, including service/application accounts). + +If an OU with improper permissions does not include identification and authentication data used by systems to determine access control, the severity is CAT II (e.g., Workstation, Printer OUs). - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-00-000460 - Windows Server 2019 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS. - <VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000090 + Windows Server 2019 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 Events records events such as the access of a password hash or the Password Policy Checking API being called. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode. - - - - Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must run in "UEFI" mode. + V-93089 + SV-103177 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". +Use the "AuditPol" tool to review the current Audit Policy configuration: -Run "System Information". +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding. +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 - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-00-000470 - Windows Server 2019 must have Secure Boot enabled. - <VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000140 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Enable Secure Boot in the system firmware. - - - - Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must have Secure Boot enabled. + V-93091 + SV-103179 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Run "System Information". +Use the "AuditPol" tool to review the current Audit Policy configuration: -Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -On server core installations, run the following PowerShell command: +Enter "AuditPol /get /category:*" -Confirm-SecureBootUEFI +Compare the "AuditPol" settings with the following: -If a value of "True" is not returned, this is a finding. +If the system does not audit the following, this is a finding. + +Detailed Tracking >> Process Creation - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000030 - Windows Server 2019 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing. - <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></IAControls> + + WN19-AU-000260 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. + SV-103181 + V-93093 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: +Use the "AuditPol" tool to review the current Audit Policy configuration: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Name: DisableIPSourceRouting +Enter "AuditPol /get /category:*" -Type: REG_DWORD -Value: 0x00000002 (2) +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Policy Change >> Audit Policy Change - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000040 - Windows Server 2019 source routing must be configured to the highest protection level to prevent Internet Protocol (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> + + WN19-AU-000270 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. + SV-103183 + V-93095 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: +Use the "AuditPol" tool to review the current Audit Policy configuration: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Name: DisableIPSourceRouting +Enter "AuditPol /get /category:*" -Value Type: REG_DWORD -Value: 0x00000002 (2) +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Policy Change >> Audit Policy Change - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000050 - Windows Server 2019 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 the 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> + + WN19-AU-000280 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" to "Disabled". + V-93097 + SV-103185 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: +Use the "AuditPol" tool to review the current Audit Policy configuration: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Name: EnableICMPRedirect +Enter "AuditPol /get /category:*" -Value Type: REG_DWORD -Value: 0x00000000 (0) +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Policy Change >> Authentication Policy Change - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000070 - Windows Server 2019 insecure logons to an SMB server must be disabled. - <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000290 + Windows Server 2019 must be configured to audit Policy Change - Authorization 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. + +Authorization Policy Change records events related to changes in user rights, such as "Create a token object". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Lanman Workstation >> "Enable insecure guest logons" to "Disabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93099 + SV-103187 + CCI-002234 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> "Audit Authorization 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: AllowInsecureGuestAuth +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Type: REG_DWORD -Value: 0x00000000 (0) +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 >> Authorization Policy Change - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000080 - Windows Server 2019 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares. - <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000300 + Windows Server 2019 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". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Network Provider >> "Hardened UNC Paths" to "Enabled" with at least the following configured in "Hardened UNC Paths" (click the "Show" button to display): - -Value Name: \\*\SYSVOL -Value: RequireMutualAuthentication=1, RequireIntegrity=1 + V-93101 + SV-103189 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Value Name: \\*\NETLOGON -Value: RequireMutualAuthentication=1, RequireIntegrity=1 - - - - This requirement is applicable to domain-joined systems. For standalone systems, this is NA. +Use the "AuditPol" tool to review the current Audit Policy configuration: -If the following registry values do not exist or are not configured as specified, this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ +Enter "AuditPol /get /category:*" -Value Name: \\*\NETLOGON -Value Type: REG_SZ -Value: RequireMutualAuthentication=1, RequireIntegrity=1 +Compare the "AuditPol" settings with the following: -Value Name: \\*\SYSVOL -Value Type: REG_SZ -Value: RequireMutualAuthentication=1, RequireIntegrity=1 +If the system does not audit the following, this is a finding. -Additional entries would not be a finding. +Privilege Use >> Sensitive Privilege Use - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000100 - Windows Server 2019 must be configured to enable Remote host allows delegation of non-exportable credentials. - <VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000310 + Windows Server 2019 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". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Remote host allows delegation of non-exportable credentials" to "Enabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93103 + SV-103191 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: AllowProtectedCreds +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Type: REG_DWORD -Value: 0x00000001 (1) +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 - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000110 - Windows Server 2019 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection. - <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000320 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Secure Boot" or "Secure Boot and DMA Protection" selected. + V-93105 + SV-103193 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: +Use the "AuditPol" tool to review the current Audit Policy configuration: -https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard - - - - For standalone systems, this is NA. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. +Enter "AuditPol /get /category:*" -Open "PowerShell" with elevated privileges (run as administrator). +Compare the "AuditPol" settings with the following: -Enter the following: +If the system does not audit the following, this is a finding. -"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" +System >> IPsec Driver - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN19-AU-000330 + Windows Server 2019 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. -If "RequiredSecurityProperties" does not include a value of "2" indicating "Secure Boot" (e.g., "{1, 2}"), this is a finding. +IPsec Driver records events related to the IPsec Driver, such as dropped packets. -If "Secure Boot and DMA Protection" is configured, "3" will also be displayed in the results (e.g., "{1, 2, 3}"). +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93107 + SV-103195 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If "VirtualizationBasedSecurityStatus" is not a value of "2" indicating "Running", this is a finding. +Use the "AuditPol" tool to review the current Audit Policy configuration: -Alternately: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Run "System Information". +Enter "AuditPol /get /category:*" -Under "System Summary", verify the following: +Compare the "AuditPol" settings with the following: -If "Device Guard Virtualization based security" does not display "Running", this is a finding. +If the system does not audit the following, this is a finding. -If "Device Guard Required Security Properties" does not display "Base Virtualization Support, Secure Boot", this is a finding. +System >> IPsec Driver - Failure + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN19-AU-000340 + Windows Server 2019 must be configured to audit System - Other System 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. -If "Secure Boot and DMA Protection" is configured, "DMA Protection" will also be displayed (e.g., "Base Virtualization Support, Secure Boot, DMA Protection"). +Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. -The policy settings referenced in the Fix section will configure the following registry values. However, due to hardware requirements, the registry values alone do not ensure proper function. +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103197 + V-93109 + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: EnableVirtualizationBasedSecurity -Value Type: REG_DWORD -Value: 0x00000001 (1) +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Name: RequirePlatformSecurityFeatures -Value Type: REG_DWORD -Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) +Enter "AuditPol /get /category:*" -A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: +Compare the "AuditPol" settings with the following: -https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard +If the system does not audit the following, this is a finding. + +System >> Other System Events - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000130 - Windows Server 2019 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad. - <VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls> + + WN19-AU-000350 + Windows Server 2019 must be configured to audit System - Other System 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. + +Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). - -If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> "Boot-Start Driver Initialization Policy" to "Not Configured" or "Enabled" with any option other than "All" selected. - - - - The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). + V-93111 + SV-103199 + CCI-002234 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If the registry value name below does not exist, this is not a finding. +Use the "AuditPol" tool to review the current Audit Policy configuration: -If it exists and is configured with a value of "0x00000007 (7)", this is a finding. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ +Enter "AuditPol /get /category:*" -Value Name: DriverLoadPolicy +Compare the "AuditPol" settings with the following: -Value Type: REG_DWORD -Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) +If the system does not audit the following, this is a finding. -Possible values for this setting are: -8 - Good only -1 - Good and unknown -3 - Good, unknown and bad but critical -7 - All (which includes "bad" and would be a finding) +System >> Other System Events - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000140 - Windows Server 2019 group policy objects must be reprocessed even if they have not changed. - <VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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> + + WN19-AU-000360 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Group Policy >> "Configure registry policy processing" to "Enabled" with the option "Process even if the Group Policy objects have not changed" selected. - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103201 + V-93113 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: NoGPOListChanges +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000180 - Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (on battery). - <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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: +Enter "AuditPol /get /category:*" -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ +Compare the "AuditPol" settings with the following: -Value Name: DCSettingIndex +If the system does not audit the following, this is a finding. -Type: REG_DWORD -Value: 0x00000001 (1) +System >> Security State Change - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000190 - Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (plugged in). - <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> + + WN19-AU-000370 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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: + V-93115 + SV-103203 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: ACSettingIndex +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000250 - Windows Server 2019 Telemetry must be configured to Security or Basic. - <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Data Collection and Preview Builds>> "Allow Telemetry" to "Enabled" with "0 - Security [Enterprise Only]" or "1 - Basic" selected in "Options". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Enter "AuditPol /get /category:*" -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DataCollection\ +Compare the "AuditPol" settings with the following: -Value Name: AllowTelemetry +If the system does not audit the following, this is a finding. -Type: REG_DWORD -Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic) +System >> Security System Extension - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000260 - Windows Server 2019 Windows Update must not obtain updates from other PCs on the Internet. - <VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000380 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Delivery Optimization >> "Download Mode" to "Enabled" with any option except "Internet" selected. + V-93117 + SV-103205 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Acceptable selections include: +Use the "AuditPol" tool to review the current Audit Policy configuration: -Bypass (100) -Group (2) -HTTP only (0) -LAN (1) -Simple (99) - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\ +Enter "AuditPol /get /category:*" -Value Name: DODownloadMode +Compare the "AuditPol" settings with the following: -Value Type: REG_DWORD -Value: 0x00000000 (0) - No peering (HTTP Only) -0x00000001 (1) - Peers on same NAT only (LAN) -0x00000002 (2) - Local Network / Private group peering (Group) -0x00000063 (99) - Simple download mode, no peering (Simple) -0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) +If the system does not audit the following, this is a finding. -A value of 0x00000003 (3), Internet, is a finding. +System >> System Integrity - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000320 - Windows Server 2019 Turning 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></IAControls> + + WN19-AU-000390 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - The default behavior is for File Explorer heap termination on corruption to be disabled. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off heap termination on corruption" to "Not Configured" or "Disabled". - - - - The default behavior is for File Explorer heap termination on corruption to be enabled. + V-93119 + SV-103207 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If the registry Value Name below does not exist, this is not a finding. +Use the "AuditPol" tool to review the current Audit Policy configuration: -If it exists and is configured with a value of "0", this is not a finding. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -If it exists and is configured with a value of "1", this is a finding. +Enter "AuditPol /get /category:*" -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ +Compare the "AuditPol" settings with the following: -Value Name: NoHeapTerminationOnCorruption +If the system does not audit the following, this is a finding. -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) +System >> System Integrity - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000330 - Windows Server 2019 File Explorer shell protocol must run in protected mode. - <VulnDiscussion>The shell protocol will limit the set of folders that 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> + + WN19-DC-000170 + Windows Server 2019 Active Directory Group Policy objects must be configured with proper audit settings. + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - The default behavior is for shell protected mode to be turned on for File Explorer. + V-93121 + SV-103209 + CCI-000172 + CCI-002234 + Configure the audit settings for Group Policy objects to include the following: -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off shell protocol protected mode" to "Not Configured" or "Disabled". - - - - The default behavior is for shell protected mode to be turned on for File Explorer. +This can be done at the Policy level in Active Directory to apply to all group policies. -If the registry value name below does not exist, this is not a finding. +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -If it exists and is configured with a value of "0", this is not a finding. +Select "Advanced Features" from the "View" Menu. -If it exists and is configured with a value of "1", this is a finding. +Navigate to [Domain] >> System >> Policies in the left panel. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ +Right click "Policies", select "Properties". -Value Name: PreXPSP2ShellProtocolBehavior +Select the "Security" tab. -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000390 - Windows Server 2019 must prevent attachments 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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: +Select the "Advanced" button. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ +Select the "Auditing" tab. -Value Name: DisableEnclosureDownload +Type - Fail +Principal - Everyone +Access - Full Control +Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects -Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000440 - Windows Server 2019 users must be notified if a web-based program attempts to install software. - <VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. +The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> "Prevent Internet Explorer security prompt for Windows Installer scripts" to "Not Configured" or "Disabled". - - - - The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. +Type - Success +Principal - Everyone +Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) +Inherited from - Parent Object +Applies to - Descendant groupPolicyContainer objects -If the registry value name below does not exist, this is not a finding. +Two instances with the following summary information will be listed: -If it exists and is configured with a value of "0", this is not a finding. +Type - Success +Principal - Everyone +Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) +Inherited from - Parent Object +Applies to - Descendant Organization Unit Objects + + + + This applies to domain controllers. It is NA for other systems. -If it exists and is configured with a value of "1", this is a finding. +Review the auditing configuration for all Group Policy objects. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ +Open "Group Policy Management" (available from various menus or run "gpmc.msc"). -Value Name: SafeForScripting +Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - - - - - SRG-OS-000480-GPOS-00229 - <GroupDescription></GroupDescription> - - WN19-CC-000450 - Windows Server 2019 must disable automatically signing in the last interactive user after a system-initiated restart. - <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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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. +For each Group Policy object: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Select the Group Policy object item in the left pane. -Value Name: DisableAutomaticRestartSignOn +Select the "Delegation" tab in the right pane. -Value Type: REG_DWORD -Value: 0x00000001 (1) +Select the "Advanced" button. + +Select the "Advanced" button again and then the "Auditing" tab. + +If the audit settings for any Group Policy object are not at least as inclusive as those below, this is a finding: + +Type - Fail +Principal - Everyone +Access - Full Control +Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects + +The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. + +Type - Success +Principal - Everyone +Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) +Inherited from - Parent Object +Applies to - Descendant groupPolicyContainer objects + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) +Inherited from - Parent Object +Applies to - Descendant Organization Unit Objects - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-DC-000150 - Windows Server 2019 directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access. - <VulnDiscussion>To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000180 + Windows Server 2019 Active Directory Domain object must be configured with proper audit settings. + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure directory data (outside the root DSE) of a non-public directory to prevent anonymous access. + SV-103211 + V-93123 + CCI-002234 + CCI-000172 + Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -For AD, there are multiple configuration items that could enable anonymous access. +Ensure "Advanced Features" is selected in the "View" menu. -Changing the access permissions on the domain naming context object (from the secure defaults) could enable anonymous access. If the check procedures indicate this is the cause, the process that was used to change the permissions should be reversed. This could have been through the Windows Support Tools ADSI Edit console (adsiedit.msc). +Select the domain being reviewed in the left pane. -The dsHeuristics option is used. This is addressed in check V-8555 in the AD Forest STIG. - - - +Right-click the domain name and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +Configure the audit settings for Domain object to include the following: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - None +Applies to - Special + +Type - Success +Principal - Domain Users +Access - All extended rights +Inherited from - None +Applies to - This object only + +Type - Success +Principal - Administrators +Access - All extended rights +Inherited from - None +Applies to - This object only + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner.) + + + This applies to domain controllers. It is NA for other systems. -Open "Command Prompt" (not elevated). +Review the auditing configuration for the Domain object. -Run "ldp.exe". +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -From the "Connection menu", select "Bind". +Ensure "Advanced Features" is selected in the "View" menu. -Clear the User, Password, and Domain fields. +Select the domain being reviewed in the left pane. -Select "Simple bind" for the Bind type and click "OK". +Right-click the domain name and select "Properties". -Confirmation of anonymous access will be displayed at the end: +Select the "Security" tab. -res = ldap_simple_bind_s -Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON' +Select the "Advanced" button and then the "Auditing" tab. -From the "Browse" menu, select "Search". +If the audit settings on the Domain object are not at least as inclusive as those below, this is a finding: -In the Search dialog, enter the DN of the domain naming context (generally something like "dc=disaost,dc=mil") in the Base DN field. +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only -Clear the Attributes field and select "Run". +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -Error messages should display related to Bind and user not authenticated. +Two instances with the following summary information will be listed: -If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding. +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - None +Applies to - Special -The following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access. +Type - Success +Principal - Domain Users +Access - All extended rights +Inherited from - None +Applies to - This object only -Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. +Type - Success +Principal - Administrators +Access - All extended rights +Inherited from - None +Applies to - This object only -Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address. +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-DC-000330 - Windows Server 2019 domain controllers must be configured to allow reset of machine account passwords. - <VulnDiscussion>Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000190 + Windows Server 2019 Active Directory Infrastructure object must be configured with proper audit settings. + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain controller: Refuse machine account password changes" to "Disabled". - - - + SV-103213 + V-93125 + CCI-000172 + CCI-002234 + Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select the domain being reviewed in the left pane. + +Right-click the "Infrastructure" object in the right pane and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +Configure the audit settings for Infrastructure object to include the following: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) + + + This applies to domain controllers. It is NA for other systems. -If the following registry value does not exist or is not configured as specified, this is a finding: +Review the auditing configuration for Infrastructure object. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Value Name: RefusePasswordChange +Ensure "Advanced Features" is selected in the "View" menu. -Value Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000020 - Windows Server 2019 must prevent local accounts with blank passwords from being used 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 does 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Select the domain being reviewed in the left pane. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ +Right-click the "Infrastructure" object in the right pane and select "Properties". -Value Name: LimitBlankPasswordUse +Select the "Security" tab. -Value Type: REG_DWORD -Value: 0x00000001 (1) +Select the "Advanced" button and then the "Auditing" tab. + +If the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-SO-000100 - Windows Server 2019 maximum age for machine account passwords must be configured to 30 days or less. - <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 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> + + WN19-DC-000200 + Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings. + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - This is the default configuration for this setting (30 days). + SV-103215 + V-93127 + CCI-002234 + CCI-000172 + Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Configure 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). - - - - This is the default configuration for this setting (30 days). +Ensure "Advanced Features" is selected in the "View" menu. -If the following registry value does not exist or is not configured as specified, this is a finding: +Select the "Domain Controllers OU" under the domain being reviewed in the left pane. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ - -Value Name: MaximumPasswordAge - -Value Type: REG_DWORD -Value: 0x0000001e (30) (or less, but not 0) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000150 - Windows Server 2019 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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". - - - - 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 NT\CurrentVersion\Winlogon\ - -Value Name: scremoveoption - -Value Type: REG_SZ -Value: 1 (Lock Workstation) or 2 (Force Logoff) - -If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000210 - Windows Server 2019 must not allow anonymous SID/Name translation. - <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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Allow anonymous SID/Name translation" to "Disabled". - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. - -If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000220 - Windows Server 2019 must not allow anonymous enumeration of Security Account Manager (SAM) accounts. - <VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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". - - - - 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\Lsa\ - -Value Name: RestrictAnonymousSAM - -Value Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000240 - Windows Server 2019 must be configured to prevent anonymous users from having the same permissions as the Everyone group. - <VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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". - - - - 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\Lsa\ - -Value Name: EveryoneIncludesAnonymous - -Value Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000260 - Windows Server 2019 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously. - <VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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". - - - - 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\LSA\ - -Value Name: UseMachineId - -Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000270 - Windows Server 2019 must prevent NTLM 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network security: Allow LocalSystem NULL session fallback" 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: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ - -Value Name: allownullsessionfallback - -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000280 - Windows Server 2019 must prevent PKU2U authentication using online identities. - <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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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". - - - - 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\LSA\pku2u\ - -Value Name: AllowOnlineID - -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000310 - Windows Server 2019 LAN Manager authentication level must be configured 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 standalone 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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". - - - - 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\Lsa\ - -Value Name: LmCompatibilityLevel - -Value Type: REG_DWORD -Value: 0x00000005 (5) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000320 - Windows Server 2019 must be configured to at least negotiate signing for LDAP client signing. - <VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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. - - - - 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\Services\LDAP\ - -Value Name: LDAPClientIntegrity - -Value Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000330 - Windows Server 2019 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption. - <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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). - - - - 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\Lsa\MSV1_0\ - -Value Name: NTLMMinClientSec - -Value Type: REG_DWORD -Value: 0x20080000 (537395200) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000340 - Windows Server 2019 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption. - <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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). - - - - 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\Lsa\MSV1_0\ - -Value Name: NTLMMinServerSec - -Value Type: REG_DWORD -Value: 0x20080000 (537395200) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-SO-000370 - Windows Server 2019 default permissions of global system objects must be strengthened. - <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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Right-click the "Domain Controllers OU" object and select "Properties". -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\ +Select the "Security" tab. -Value Name: ProtectionMode +Select the "Advanced" button and then the "Auditing" tab. -Value Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-UC-000010 - Windows Server 2019 must preserve zone information when saving attachments. - <VulnDiscussion>Attachments from outside sources may contain malicious code. 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - The default behavior is for Windows to mark file attachments with their zone information. +Configure the audit settings for Domain Controllers OU object to include the following: -If this needs to be corrected, configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager >> "Do not preserve zone information in file attachments" to "Not Configured" or "Disabled". - - - - The default behavior is for Windows to mark file attachments with their zone information. +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None -If the registry Value Name below does not exist, this is not a finding. +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -If it exists and is configured with a value of "2", this is not a finding. +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: all create, delete and modify permissions) -If it exists and is configured with a value of "1", this is a finding. +Type - Success +Principal - Everyone +Access - Write all properties +Inherited from - None +Applies to - This object and all descendant objects -Registry Hive: HKEY_CURRENT_USER -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ +Two instances with the following summary information will be listed: -Value Name: SaveZoneInformation +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objects + + + + This applies to domain controllers. It is NA for other systems. -Value Type: REG_DWORD -Value: 0x00000002 (2) (or if the Value Name does not exist) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-EP-000010 - Windows Server 2019 Exploit Protection system-level mitigation, Data Execution Prevention (DEP), must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Data Execution Prevention (DEP)", are enabled by default at the system level. DEP prevents code from being run from data-only memory pages. If this is turned off, Windows may be subject to various exploits.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Ensure Exploit Protection system-level mitigation, "Data Execution Prevention (DEP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. +Review the auditing configuration for the Domain Controller OU object. -Open "Windows Defender Security Center". +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Select "App & browser control". +Ensure "Advanced Features" is selected in the "View" menu. -Select "Exploit protection settings". +Select the "Domain Controllers OU" under the domain being reviewed in the left pane. -Under "System settings", configure "Data Execution Prevention (DEP)" to "On by default" or "Use default (<On>)". +Right-click the "Domain Controllers OU" object and select "Properties". -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn DEP on (other system level EP requirements can be combined under <SystemConfig>): +Select the "Security" tab. -<SystemConfig> - <DEP Enable="true"></DEP> -</SystemConfig> +Select the "Advanced" button and then the "Auditing" tab. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. +If the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding: -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object and all descendant objects -Run "Windows PowerShell" with elevated privileges (run as administrator). +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -Enter "Get-ProcessMitigation -System". +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: all create, delete and modify permissions) -If the status of "DEP: Enable" is "OFF", this is a finding. +Type - Success +Principal - Everyone +Access - Write all properties +Inherited from - None +Applies to - This object and all descendant objects -Values that would not be a finding include: +Two instances with the following summary information will be listed: -ON -NOTSET (Default configuration) +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objects - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-EP-000030 - Windows Server 2019 Exploit Protection system-level mitigation, Control flow guard (CFG), must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Control flow guard (CFG)", are enabled by default at the system level. CFG ensures flow integrity for indirect calls. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000210 + Windows Server 2019 Active Directory AdminSDHolder object must be configured with proper audit settings. + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure Exploit Protection system-level mitigation, "Control flow guard (CFG)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". + SV-103217 + V-93129 + CCI-000172 + CCI-002234 + Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Select "App & browser control". - -Select "Exploit protection settings". +Ensure "Advanced Features" is selected in the "View" menu. -Under "System settings", configure "Control flow guard (CFG)" to "On by default" or "Use default (<On>)". +Select "System" under the domain being reviewed in the left pane. -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn CFG on (other system level EP requirements can be combined under <SystemConfig>): +Right-click the "AdminSDHolder" object in the right pane and select "Properties". -<SystemConfig> - <ControlFlowGuard Enable="true"></ControlFlowGuard> -</SystemConfig> +Select the "Security" tab. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. +Select the "Advanced" button and then the "Auditing" tab. -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". +Configure the audit settings for AdminSDHolder object to include the following: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only -Enter "Get-ProcessMitigation -System". +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -If the status of "CFG: Enable" is "OFF", this is a finding. +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Write all properties, Modify permissions, Modify owner) -Values that would not be a finding include: +Two instances with the following summary information will be listed: -ON -NOTSET (Default configuration) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-EP-000040 - Windows Server 2019 Exploit Protection system-level mitigation, Validate exception chains (SEHOP), must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate exception chains (SEHOP)", are enabled by default at the system level. SEHOP (structured exception handling overwrite protection) ensures the integrity of an exception chain during exception dispatch. If this is turned off, Windows may be subject to various exploits.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Ensure Exploit Protection system-level mitigation, "Validate exception chains (SEHOP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objects + + + + This applies to domain controllers. It is NA for other systems. -Open "Windows Defender Security Center". +Review the auditing configuration for the "AdminSDHolder" object. -Select "App & browser control". +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Select "Exploit protection settings". +Ensure "Advanced Features" is selected in the "View" menu. -Under "System settings", configure "Validate exception chains (SEHOP)" to "On by default" or "Use default (<On>)". +Select "System" under the domain being reviewed in the left pane. -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn SEHOP on (other system level EP requirements can be combined under <SystemConfig>): +Right-click the "AdminSDHolder" object in the right pane and select "Properties". -<SystemConfig> - <SEHOP Enable="true"></SEHOP> -</SystemConfig> +Select the "Security" tab. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. +Select the "Advanced" button and then the "Auditing" tab. -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". +If the audit settings on the "AdminSDHolder" object are not at least as inclusive as those below, this is a finding: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only -Enter "Get-ProcessMitigation -System". +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -If the status of "SEHOP: Enable" is "OFF", this is a finding. +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Write all properties, Modify permissions, Modify owner) -Values that would not be a finding include: +Two instances with the following summary information will be listed: -ON -NOTSET (Default configuration) +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objects - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-EP-000050 - Windows Server 2019 Exploit Protection system-level mitigation, Validate heap integrity, must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate heap integrity", are enabled by default at the system level. "Validate heap integrity" terminates a process when heap corruption is detected. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000220 + Windows Server 2019 Active Directory RID Manager$ object must be configured with proper audit settings. + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure Exploit Protection system-level mitigation, "Validate heap integrity" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". + V-93131 + SV-103219 + CCI-002234 + CCI-000172 + Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Select "Exploit protection settings". +Ensure "Advanced Features" is selected in the "View" menu. -Under "System settings", configure "Validate heap integrity" to "On by default" or "Use default (<On>)". +Select "System" under the domain being reviewed in the left pane. -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Validate heap integrity on (other system level EP requirements can be combined under <SystemConfig>): +Right-click the "RID Manager$" object in the right pane and select "Properties". -<SystemConfig> - <Heap TerminateOnError="true"></Heap> -</SystemConfig> +Select the "Security" tab. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. +Select the "Advanced" button and then the "Auditing" tab. -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". +Configure the audit settings for RID Manager$ object to include the following: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None -Enter "Get-ProcessMitigation -System". +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -If the status of "Heap: TerminateOnError" is "OFF", this is a finding. +Type - Success +Principal - Everyone +Access - Special +Inherited from - None + (Access - Special = Write all properties, All extended rights, Change RID master) -Values that would not be a finding include: +Two instances with the following summary information will be listed: -ON -NOTSET (Default configuration) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-EP-000060 - Windows Server 2019 Exploit Protection mitigations must be configured for Acrobat.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Ensure the following mitigations are turned "ON" for Acrobat.exe: +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) + + + + This applies to domain controllers. It is NA for other systems. -DEP: -Enable: ON +Review the auditing configuration for the "RID Manager$" object. -ASLR: -BottomUp: ON -ForceRelocateImages: ON +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Ensure "Advanced Features" is selected in the "View" menu. -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Select "System" under the domain being reviewed in the left pane. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Right-click the "RID Manager$" object in the right pane and select "Properties". -This is applicable to unclassified systems, for other systems this is NA. +Select the "Security" tab. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Select the "Advanced" button and then the "Auditing" tab. -Enter "Get-ProcessMitigation -Name Acrobat.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +If the audit settings on the "RID Manager$" object are not at least as inclusive as those below, this is a finding: -If the following mitigations do not have a status of "ON", this is a finding: +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None -DEP: -Enable: ON +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -ASLR: -BottomUp: ON -ForceRelocateImages: ON +Type - Success +Principal - Everyone +Access - Special +Inherited from - None + (Access - Special = Write all properties, All extended rights, Change RID master) -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Two instances with the following summary information will be listed: -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-EP-000070 - Windows Server 2019 Exploit Protection mitigations must be configured for AcroRd32.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Ensure the following mitigations are turned "ON" for AcroRd32.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN19-DC-000240 + Windows Server 2019 must be configured to audit DS Access - Directory Service Access 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. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Audit Directory Service Access records events related to users accessing an Active Directory object. -This is applicable to unclassified systems, for other systems this is NA. +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103221 + V-93133 + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Access" with "Success" selected. + + + + This applies to domain controllers. It is NA for other systems. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Enter "Get-ProcessMitigation -Name AcroRd32.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Use the "AuditPol" tool to review the current Audit Policy configuration: -If the following mitigations do not have a status of "ON", this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -DEP: -Enable: ON +Enter "AuditPol /get /category:*" -ASLR: -BottomUp: ON -ForceRelocateImages: ON +Compare the "AuditPol" settings with the following: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +DS Access >> Directory Service Access - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-EP-000080 - Windows Server 2019 Exploit Protection mitigations must be configured for chrome.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000250 + Windows Server 2019 must be configured to audit DS Access - Directory Service Access 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 Directory Service Access records events related to users accessing an Active Directory object. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for chrome.exe: - -DEP: -Enable: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + SV-103223 + V-93135 + CCI-002234 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Access" with "Failure" selected. + + + + This applies to domain controllers. It is NA for other systems. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -This is applicable to unclassified systems, for other systems this is NA. +Use the "AuditPol" tool to review the current Audit Policy configuration: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Enter "Get-ProcessMitigation -Name chrome.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Enter "AuditPol /get /category:*" -If the following mitigations do not have a status of "ON", this is a finding: +Compare the "AuditPol" settings with the following: -DEP: -Enable: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +DS Access >> Directory Service Access - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-EP-000090 - Windows Server 2019 Exploit Protection mitigations must be configured for EXCEL.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000260 + Windows Server 2019 must be configured to audit DS Access - Directory Service Changes 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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for EXCEL.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. + V-93137 + SV-103225 + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Changes" with "Success" selected. + + + + This applies to domain controllers. It is NA for other systems. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Enter "Get-ProcessMitigation -Name EXCEL.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Use the "AuditPol" tool to review the current Audit Policy configuration: -If the following mitigations do not have a status of "ON", this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -DEP: -Enable: ON +Enter "AuditPol /get /category:*" -ASLR: -ForceRelocateImages: ON +Compare the "AuditPol" settings with the following: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +DS Access >> Directory Service Changes - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-EP-000100 - Windows Server 2019 Exploit Protection mitigations must be configured for firefox.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000270 + Windows Server 2019 must be configured to audit DS Access - Directory Service Changes 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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for firefox.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. + V-93139 + SV-103227 + CCI-002234 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Changes" with "Failure" selected. + + + + This applies to domain controllers. It is NA for other systems. -This is applicable to unclassified systems, for other systems this is NA. +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Use the "AuditPol" tool to review the current Audit Policy configuration: -Enter "Get-ProcessMitigation -Name firefox.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -If the following mitigations do not have a status of "ON", this is a finding: +Enter "AuditPol /get /category:*" -DEP: -Enable: ON +Compare the "AuditPol" settings with the following: -ASLR: -BottomUp: ON -ForceRelocateImages: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +DS Access >> Directory Service Changes - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000341-GPOS-00132 <GroupDescription></GroupDescription> - - WN19-EP-000110 - Windows Server 2019 Exploit Protection mitigations must be configured for FLTLDR.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000270 + Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for FLTLDR.EXE: - -DEP: -Enable: ON - -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Child Process: -DisallowChildProcessCreation: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + SV-103265 + V-93177 + CCI-001849 + Configure 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 write events directly to an audit server, this is NA. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +If the following registry value does not exist or is not configured as specified, this is a finding: -This is applicable to unclassified systems, for other systems this is NA. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Application\ -Run "Windows PowerShell" with elevated privileges (run as administrator). +Value Name: MaxSize -Enter "Get-ProcessMitigation -Name FLTLDR.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater) + + + + + SRG-OS-000341-GPOS-00132 + <GroupDescription></GroupDescription> + + WN19-CC-000280 + Windows Server 2019 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103267 + V-93179 + CCI-001849 + Configure 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 write events directly to an audit server, this is NA. -If the following mitigations do not have a status of "ON", this is a finding: +If the following registry value does not exist or is not configured as specified, this is a finding: -DEP: -Enable: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\ -ImageLoad: -BlockRemoteImageLoads: ON +Value Name: MaxSize -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Type: REG_DWORD +Value: 0x00030000 (196608) (or greater) + + + + + SRG-OS-000341-GPOS-00132 + <GroupDescription></GroupDescription> + + WN19-CC-000290 + Windows Server 2019 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103269 + V-93181 + CCI-001849 + Configure 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 write events directly to an audit server, this is NA. -Child Process: -DisallowChildProcessCreation: ON +If the following registry value does not exist or is not configured as specified, this is a finding: -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\ + +Value Name: MaxSize + +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000342-GPOS-00133 <GroupDescription></GroupDescription> - - WN19-EP-000120 - Windows Server 2019 Exploit Protection mitigations must be configured for GROOVE.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000010 + Windows Server 2019 audit records must be backed up to a different system or media than the system being audited. + <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for GROOVE.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON + V-93183 + SV-103271 + CCI-001851 + Establish and implement a process for backing up log data to another system or media other than the system being audited. + + + + Determine if a process to back up log data to a different system or media than the system being audited has been implemented. -Child Process: -DisallowChildProcessCreation: ON +If it has not, this is a finding. + + + + + SRG-OS-000355-GPOS-00143 + <GroupDescription></GroupDescription> + + WN19-00-000440 + The Windows Server 2019 time service must synchronize with an appropriate DoD time source. + <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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93187 + SV-103275 + CCI-001891 + Configure the system to synchronize time with an appropriate DoD time source. -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Domain-joined systems use NT5DS to synchronize time from other systems in the domain by default. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +If 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 appropriate DoD time server. -This is applicable to unclassified systems, for other systems this is NA. +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. + + + + Review the Windows time service configuration. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Open an elevated "Command Prompt" (run as administrator). -Enter "Get-ProcessMitigation -Name GROOVE.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Enter "W32tm /query /configuration". -If the following mitigations do not have a status of "ON", this is a finding: +Domain-joined systems (excluding the domain controller with the PDC emulator role): -DEP: -Enable: ON +If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. -ASLR: -ForceRelocateImages: ON +Other systems: -ImageLoad: -BlockRemoteImageLoads: ON +If systems are configured with a "Type" of "NTP", including standalone systems and the domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +To determine the domain controller with the PDC Emulator role: -Child Process: -DisallowChildProcessCreation: ON +Open "PowerShell". -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Enter "Get-ADDomain | FT PDCEmulator". - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000362-GPOS-00149 <GroupDescription></GroupDescription> - - WN19-EP-000130 - Windows Server 2019 Exploit Protection mitigations must be configured for iexplore.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000420 + Windows Server 2019 must prevent users 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for iexplore.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). + V-93199 + SV-103287 + CCI-001812 + Configure 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: -Enter "Get-ProcessMitigation -Name iexplore.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -If the following mitigations do not have a status of "ON", this is a finding: +Value Name: EnableUserControl -DEP: -Enable: ON +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000362-GPOS-00149 + <GroupDescription></GroupDescription> + + WN19-CC-000430 + Windows Server 2019 must disable the Windows Installer Always install with elevated privileges option. + <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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93201 + SV-103289 + CCI-001812 + Configure 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: -ASLR: -BottomUp: ON -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: AlwaysInstallElevated -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000363-GPOS-00150 <GroupDescription></GroupDescription> - - WN19-EP-000140 - Windows Server 2019 Exploit Protection mitigations must be configured for INFOPATH.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000220 + Windows Server 2019 system files must be monitored for unauthorized changes. + <VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for INFOPATH.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON + V-93203 + SV-103291 + CCI-001744 + Monitor the system for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools. + + + + Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If system files are not monitored for unauthorized changes, this is a finding. -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +A properly configured and approved DoD HBSS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. + + + + + SRG-OS-000368-GPOS-00154 + <GroupDescription></GroupDescription> + + WN19-CC-000210 + Windows Server 2019 Autoplay 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 media is inserted into 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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93373 + SV-103459 + CCI-001764 + Configure 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: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -This is applicable to unclassified systems, for other systems this is NA. +Value Name: NoAutoplayfornonVolume -Run "Windows PowerShell" with elevated privileges (run as administrator). +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000368-GPOS-00154 + <GroupDescription></GroupDescription> + + WN19-CC-000220 + Windows Server 2019 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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93375 + SV-103461 + CCI-001764 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Set the default behavior for AutoRun" to "Enabled" with "Do not execute any autorun commands" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Enter "Get-ProcessMitigation -Name INFOPATH.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ -If the following mitigations do not have a status of "ON", this is a finding: +Value Name: NoAutorun -DEP: -Enable: ON +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000368-GPOS-00154 + <GroupDescription></GroupDescription> + + WN19-CC-000230 + Windows Server 2019 AutoPlay 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 media is inserted into 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. Enabling this policy disables 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93377 + SV-103463 + CCI-001764 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Turn off AutoPlay" to "Enabled" with "All Drives" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: NoDriveTypeAutoRun -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Type: REG_DWORD +Value: 0x000000ff (255) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000370-GPOS-00155 <GroupDescription></GroupDescription> - - WN19-EP-000150 - Windows Server 2019 Exploit Protection mitigations must be configured for java.exe, javaw.exe, and javaws.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000080 + Windows Server 2019 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. + <VulnDiscussion>Using a whitelist provides a configuration management method to allow 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for java.exe, javaw.exe, and javaws.exe: + V-93379 + SV-103465 + CCI-001774 + Configure an application whitelisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. -DEP: -Enable: ON +Configuration of whitelisting applications will vary by the program. AppLocker is a whitelisting application built into Windows Server. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If AppLocker is used, it is configured through group policy in Computer Configuration >> Windows Settings >> Security Settings >> Application Control Policies >> AppLocker. -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm + + + + This is applicable to unclassified systems. For other systems, this is NA. -This 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +If an application whitelisting program is not in use on the system, this is a finding. -Enter "Get-ProcessMitigation -Name [application name]" with each of the following substituted for [application name]: -java.exe, javaw.exe, and javaws.exe -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Configuration of whitelisting applications will vary by the program. -If the following mitigations do not have a status of "ON" for each, this is a finding: +AppLocker is a whitelisting application built into Windows Server. A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules. -DEP: -Enable: ON +If AppLocker is used, perform the following to view the configuration of AppLocker: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Open "PowerShell". -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If the AppLocker PowerShell module has not been imported previously, 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" at the following link: + +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000373-GPOS-00157 <GroupDescription></GroupDescription> - - WN19-EP-000160 - Windows Server 2019 Exploit Protection mitigations must be configured for lync.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000340 + Windows Server 2019 must not save passwords 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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for lync.exe: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON + V-93425 + SV-103511 + CCI-002038 + Configure 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: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Name: DisablePasswordSaving -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000373-GPOS-00157 + <GroupDescription></GroupDescription> + + WN19-CC-000360 + Windows Server 2019 Remote 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. -This is applicable to unclassified systems, for other systems this is NA. +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93427 + SV-103513 + CCI-002038 + Configure 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: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Enter "Get-ProcessMitigation -Name lync.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Value Name: fPromptForPassword -If the following mitigations do not have a status of "ON", this is a finding: +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000373-GPOS-00157 + <GroupDescription></GroupDescription> + + WN19-CC-000520 + Windows Server 2019 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. -DEP: -Enable: ON +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103515 + V-93429 + CCI-002038 + Configure 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: -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: DisableRunAs -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000373-GPOS-00157 <GroupDescription></GroupDescription> - - WN19-EP-000170 - Windows Server 2019 Exploit Protection mitigations must be configured for MSACCESS.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000380 + Windows Server 2019 User 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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for MSACCESS.EXE: + SV-103517 + V-93431 + CCI-002038 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -DEP: -Enable: ON +If the following registry value does not exist or is not configured as specified, this is a finding: -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: FilterAdministratorToken -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000373-GPOS-00157 + <GroupDescription></GroupDescription> + + WN19-SO-000410 + Windows Server 2019 User Account Control must automatically deny standard user requests for elevation. + <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93433 + SV-103519 + CCI-002038 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -This is applicable to unclassified systems, for other systems this is NA. +If the following registry value does not exist or is not configured as specified, this is a finding: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Enter "Get-ProcessMitigation -Name MSACCESS.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Value Name: ConsentPromptBehaviorUser -If the following mitigations do not have a status of "ON", this is a finding: +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000373-GPOS-00157 + <GroupDescription></GroupDescription> + + WN19-SO-000440 + Windows Server 2019 User 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. -DEP: -Enable: ON +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93435 + SV-103521 + CCI-002038 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -ASLR: -ForceRelocateImages: ON +If the following registry value does not exist or is not configured as specified, this is a finding: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: EnableLUA + +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000379-GPOS-00164 + <GroupDescription></GroupDescription> + + WN19-SO-000090 + Windows Server 2019 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 the 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93455 + SV-103541 + CCI-001967 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain member: Disable machine account password changes" 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: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Name: DisablePasswordChange + +Value Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000393-GPOS-00173 <GroupDescription></GroupDescription> - - WN19-EP-000180 - Windows Server 2019 Exploit Protection mitigations must be configured for MSPUB.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000480 + Windows Server 2019 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. + +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for MSPUB.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON + SV-103585 + V-93499 + CCI-002890 + CCI-003123 + Configure 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: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Name: AllowUnencryptedTraffic -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000393-GPOS-00173 + <GroupDescription></GroupDescription> + + WN19-CC-000510 + Windows Server 2019 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. -This is applicable to unclassified systems, for other systems this is NA. +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103587 + V-93501 + CCI-002890 + CCI-003123 + Configure 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: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -Enter "Get-ProcessMitigation -Name MSPUB.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Value Name: AllowUnencryptedTraffic -If the following mitigations do not have a status of "ON", this is a finding: +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000396-GPOS-00176 + <GroupDescription></GroupDescription> + + WN19-DC-000140 + Windows Server 2019 must use separate, NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level when replication data traverses a network cleared to a lower level than the data. + <VulnDiscussion>Directory data that is not appropriately encrypted is subject to compromise. Commercial-grade encryption does not provide adequate protection when the classification level of directory data in transit is higher than the level of 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93513 + SV-103599 + CCI-002450 + Configure NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level that transfer replication data through a network cleared to a lower level than the data. + + + + This applies to domain controllers. It is NA for other systems. -DEP: -Enable: ON +Review the organization network diagram(s) or documentation to determine the level of classification for the network(s) over which replication data is transmitted. -ASLR: -ForceRelocateImages: ON +Determine the classification level of the Windows domain controller. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the classification level of the Windows domain controller is higher than the level of the networks, review the organization network diagram(s) and directory implementation documentation to determine if NSA-approved encryption is used to protect the replication network traffic. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If the classification level of the Windows domain controller is higher than the level of the network traversed and NSA-approved encryption is not used, this is a finding. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000420-GPOS-00186 <GroupDescription></GroupDescription> - - WN19-EP-000190 - Windows Server 2019 Exploit Protection mitigations must be configured for OIS.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000060 + Windows Server 2019 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 server's 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for OIS.EXE: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON + SV-103627 + V-93541 + CCI-002385 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" to "Enabled". -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netbt\Parameters\ -This is applicable to unclassified systems, for other systems this is NA. +Value Name: NoNameReleaseOnDemand -Run "Windows PowerShell" with elevated privileges (run as administrator). +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-DC-000320 + Windows Server 2019 domain controllers must require LDAP access signing. + <VulnDiscussion>Unsigned network traffic is susceptible to man-in-the-middle attacks, where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. The risk of an attacker pulling this off can be decreased by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPsec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man-in-the-middle attacks extremely difficult. -Enter "Get-ProcessMitigation -Name OIS.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93545 + SV-103631 + CCI-002418 + CCI-002421 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain controller: LDAP server signing requirements" to "Require signing". + + + + This applies to domain controllers. It is NA for other systems. -If the following mitigations do not have a status of "ON", this is a finding: +If the following registry value does not exist or is not configured as specified, this is a finding: -DEP: -Enable: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\NTDS\Parameters\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: LDAPServerIntegrity -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Type: REG_DWORD +Value: 0x00000002 (2) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000423-GPOS-00187 <GroupDescription></GroupDescription> - - WN19-EP-000200 - Windows Server 2019 Exploit Protection mitigations must be configured for OneDrive.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000060 + Windows Server 2019 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled. + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for OneDrive.exe: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON + V-93547 + SV-103633 + CCI-002421 + CCI-002418 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Value Name: RequireSignOrSeal -This is applicable to unclassified systems, for other systems this is NA. +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000070 + Windows Server 2019 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to enabled. + <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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93549 + SV-103635 + CCI-002418 + CCI-002421 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Enter "Get-ProcessMitigation -Name OneDrive.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -If the following mitigations do not have a status of "ON", this is a finding: +Value Name: SealSecureChannel -DEP: -Enable: ON +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000080 + Windows Server 2019 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled. + <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. -ASLR: -ForceRelocateImages: ON +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93551 + SV-103637 + CCI-002421 + CCI-002418 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -ImageLoad: -BlockRemoteImageLoads: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: SignSecureChannel -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000423-GPOS-00187 <GroupDescription></GroupDescription> - - WN19-EP-000210 - Windows Server 2019 Exploit Protection mitigations must be configured for OUTLOOK.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000110 + Windows Server 2019 must be configured to require a strong session key. + <VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for OUTLOOK.EXE: - -DEP: -Enable: ON + SV-103639 + V-93553 + CCI-002418 + CCI-002421 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: RequireStrongKey -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Type: REG_DWORD +Value: 0x00000001 (1) -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +This setting may prevent a system from being joined to a domain if not configured consistently between systems. + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000160 + Windows Server 2019 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled. + <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. -This is applicable to unclassified systems, for other systems this is NA. +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93555 + SV-103641 + CCI-002421 + CCI-002418 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network client: Digitally sign communications (always)" to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -Enter "Get-ProcessMitigation -Name OUTLOOK.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Value Name: RequireSecuritySignature -If the following mitigations do not have a status of "ON", this is a finding: +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000170 + Windows Server 2019 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled. + <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. -DEP: -Enable: ON +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93557 + SV-103643 + CCI-002418 + CCI-002421 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: EnableSecuritySignature -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000423-GPOS-00187 <GroupDescription></GroupDescription> - - WN19-EP-000220 - Windows Server 2019 Exploit Protection mitigations must be configured for plugin-container.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000190 + Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled. + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for plugin-container.exe: + SV-103645 + V-93559 + CCI-002421 + CCI-002418 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network server: Digitally sign communications (always)" to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -DEP: -Enable: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: RequireSecuritySignature -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000200 + Windows Server 2019 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled. + <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. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93561 + SV-103647 + CCI-002418 + CCI-002421 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -This is applicable to unclassified systems, for other systems this is NA. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Run "Windows PowerShell" with elevated privileges (run as administrator). +Value Name: EnableSecuritySignature -Enter "Get-ProcessMitigation -Name plugin-container.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000425-GPOS-00189 + <GroupDescription></GroupDescription> + + WN19-00-000260 + Windows Server 2019 must implement protection methods such as TLS, encrypted VPNs, or IPsec if the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. + <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. -If the following mitigations do not have a status of "ON", this is a finding: +Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. -DEP: -Enable: ON +Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93543 + SV-103629 + CCI-002422 + CCI-002420 + Configure protection methods such as TLS, encrypted VPNs, or IPsec when the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. + + + + If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If protection methods have not been implemented, this is a finding. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000433-GPOS-00192 <GroupDescription></GroupDescription> - - WN19-EP-000230 - Windows Server 2019 Exploit Protection mitigations must be configured for POWERPNT.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000310 + Windows Server 2019 Explorer Data Execution Prevention must be enabled. + <VulnDiscussion>Data Execution Prevention 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for POWERPNT.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. + SV-103649 + V-93563 + CCI-002824 + The default behavior is for data execution prevention to be turned on for File Explorer. -Run "Windows PowerShell" with elevated privileges (run as administrator). +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off Data Execution Prevention for Explorer" to "Not Configured" or "Disabled". + + + + The default behavior is for Data Execution Prevention to be turned on for File Explorer. -Enter "Get-ProcessMitigation -Name POWERPNT.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +If the registry value name below does not exist, this is not a finding. -If the following mitigations do not have a status of "ON", this is a finding: +If it exists and is configured with a value of "0", this is not a finding. -DEP: -Enable: ON +If it exists and is configured with a value of "1", this is a finding. -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: NoDataExecutionPrevention -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000433-GPOS-00193 <GroupDescription></GroupDescription> - - WN19-EP-000240 - Windows Server 2019 Exploit Protection mitigations must be configured for PPTVIEW.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000020 + Windows Server 2019 Exploit Protection system-level mitigation, Randomize memory allocations (Bottom-Up ASLR), must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for PPTVIEW.EXE: - -DEP: -Enable: ON + V-93565 + SV-103651 + CCI-002824 + Ensure Exploit Protection system-level mitigation, "Randomize memory allocations (Bottom-Up ASLR)" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. -ASLR: -ForceRelocateImages: ON +Open "Windows Defender Security Center". -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Select "App & browser control". -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Select "Exploit protection settings". -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Under "System settings", configure "Randomize memory allocations (Bottom-Up ASLR)" to "On by default" or "Use default (<On>)". -This is applicable to unclassified systems, for other systems this is NA. +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Bottom-Up ASLR on (other system level EP requirements can be combined under <SystemConfig>): -Run "Windows PowerShell" with elevated privileges (run as administrator). +<SystemConfig> + <ASLR BottomUp="true" HighEntropy="true"></ASLR> +</SystemConfig> -Enter "Get-ProcessMitigation -Name PPTVIEW.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. -If the following mitigations do not have a status of "ON", this is a finding: +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". -DEP: -Enable: ON +Run "Windows PowerShell" with elevated privileges (run as administrator). -ASLR: -ForceRelocateImages: ON +Enter "Get-ProcessMitigation -System". -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the status of "ASLR: BottomUp" is "OFF", this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Values that would not be a finding include: + +ON +NOTSET (Default configuration) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000470-GPOS-00214 <GroupDescription></GroupDescription> - - WN19-EP-000250 - Windows Server 2019 Exploit Protection mitigations must be configured for VISIO.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000070 + Windows Server 2019 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for VISIO.EXE: + SV-103241 + V-93153 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -DEP: -Enable: ON +Use the "AuditPol" tool to review the current Audit Policy configuration: -ASLR: -ForceRelocateImages: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter "AuditPol /get /category:*" -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Compare the "AuditPol" settings with the following: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +If the system does not audit the following, this is a finding. -This is applicable to unclassified systems, for other systems this is NA. +Account Logon >> Credential Validation - Success + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN19-AU-000080 + Windows Server 2019 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103243 + V-93155 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Enter "Get-ProcessMitigation -Name VISIO.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Use the "AuditPol" tool to review the current Audit Policy configuration: -If the following mitigations do not have a status of "ON", this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -DEP: -Enable: ON +Enter "AuditPol /get /category:*" -ASLR: -ForceRelocateImages: ON +Compare the "AuditPol" settings with the following: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Account Logon >> Credential Validation - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000470-GPOS-00214 <GroupDescription></GroupDescription> - - WN19-EP-000260 - Windows Server 2019 Exploit Protection mitigations must be configured for VPREVIEW.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000170 + Windows Server 2019 must be configured to audit Logon/Logoff - Group Membership 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 Group Membership records information related to the group membership of a user's logon token.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for VPREVIEW.EXE: + V-93159 + SV-103247 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Group Membership" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -DEP: -Enable: ON +Use the "AuditPol" tool to review the current Audit Policy configuration: -ASLR: -ForceRelocateImages: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter "AuditPol /get /category:*" -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Compare the "AuditPol" settings with the following: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +If the system does not audit the following, this is a finding. -This is applicable to unclassified systems, for other systems this is NA. +Logon/Logoff >> Group Membership - Success + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN19-AU-000210 + Windows Server 2019 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Special Logon records special logons that have administrative privileges and can be used to elevate processes. -Enter "Get-ProcessMitigation -Name VPREVIEW.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93161 + SV-103249 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If the following mitigations do not have a status of "ON", this is a finding: +Use the "AuditPol" tool to review the current Audit Policy configuration: -DEP: -Enable: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -ASLR: -ForceRelocateImages: ON +Enter "AuditPol /get /category:*" -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Compare the "AuditPol" settings with the following: -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Special Logon - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000470-GPOS-00214 <GroupDescription></GroupDescription> - - WN19-EP-000270 - Windows Server 2019 Exploit Protection mitigations must be configured for WINWORD.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000220 + Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. + +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for WINWORD.EXE: + SV-103251 + V-93163 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -DEP: -Enable: ON +Use the "AuditPol" tool to review the current Audit Policy configuration: -ASLR: -ForceRelocateImages: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter "AuditPol /get /category:*" -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Compare the "AuditPol" settings with the following: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +If the system does not audit the following, this is a finding. -This is applicable to unclassified systems, for other systems this is NA. +Object Access >> Other Object Access Events - Success + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN19-AU-000230 + Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103253 + V-93165 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Enter "Get-ProcessMitigation -Name WINWORD.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Use the "AuditPol" tool to review the current Audit Policy configuration: -If the following mitigations do not have a status of "ON", this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -DEP: -Enable: ON +Enter "AuditPol /get /category:*" -ASLR: -ForceRelocateImages: ON +Compare the "AuditPol" settings with the following: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Object Access >> Other Object Access Events - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000472-GPOS-00217 <GroupDescription></GroupDescription> - - WN19-EP-000280 - Windows Server 2019 Exploit Protection mitigations must be configured for wmplayer.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000180 + Windows Server 2019 must be configured to audit 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. + +Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for wmplayer.exe: - -DEP: -Enable: ON - -Payload: -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. + V-93171 + SV-103259 + CCI-000172 + CCI-000366 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Use the "AuditPol" tool to review the current Audit Policy configuration: -Enter "Get-ProcessMitigation -Name wmplayer.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -If the following mitigations do not have a status of "ON", this is a finding: +Enter "AuditPol /get /category:*" -DEP: -Enable: ON +Compare the "AuditPol" settings with the following: -Payload: -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Logon/Logoff >> Logoff - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000474-GPOS-00219 <GroupDescription></GroupDescription> - - WN19-EP-000290 - Windows Server 2019 Exploit Protection mitigations must be configured for wordpad.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000130 + Windows Server 2019 must be configured to audit Detailed Tracking - Plug and Play 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. + +Plug and Play activity records events related to the successful connection of external devices.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for wordpad.exe: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. + V-93157 + SV-103245 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> "Audit PNP Activity" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Use the "AuditPol" tool to review the current Audit Policy configuration: -Enter "Get-ProcessMitigation -Name wordpad.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -If the following mitigations do not have a status of "ON", this is a finding: +Enter "AuditPol /get /category:*" -DEP: -Enable: ON +Compare the "AuditPol" settings with the following: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Detailed Tracking >> Plug and Play Events - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000474-GPOS-00219 <GroupDescription></GroupDescription> - - WN19-00-000010 - Windows Server 2019 users with Administrative privileges 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> + + WN19-AU-000240 + Windows Server 2019 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. + +Removable Storage auditing under Object Access 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure each user with administrative privileges 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. + SV-103255 + V-93167 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding. +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - Success + +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. - - SRG-OS-000368-GPOS-00154 + + SRG-OS-000474-GPOS-00219 <GroupDescription></GroupDescription> - - WN19-CC-000210 - Windows Server 2019 Autoplay 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 media is inserted into 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></IAControls> + + WN19-AU-000250 + Windows Server 2019 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. + +Removable Storage auditing under Object Access 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001764 - Configure 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: + SV-103257 + V-93169 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: NoAutoplayfornonVolume +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Type: REG_DWORD -Value: 0x00000001 (1) +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 - Failure + +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. - - SRG-OS-000368-GPOS-00154 + + SRG-OS-000478-GPOS-00223 <GroupDescription></GroupDescription> - - WN19-CC-000220 - Windows Server 2019 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></IAControls> + + WN19-SO-000360 + Windows Server 2019 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing. + <VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001764 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Set the default behavior for AutoRun" to "Enabled" with "Do not execute any autorun commands" selected. - - - + SV-103597 + V-93511 + CCI-002450 + Configure 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". + + + 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\Explorer\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ -Value Name: NoAutorun +Value Name: Enabled -Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_DWORD +Value: 0x00000001 (1) + +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; otherwise. the browser will not be able to connect to a secure site. - - SRG-OS-000368-GPOS-00154 + + SRG-OS-000479-GPOS-00224 <GroupDescription></GroupDescription> - - WN19-CC-000230 - Windows Server 2019 AutoPlay 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 media is inserted into 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. Enabling this policy disables 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> + + WN19-AU-000020 + Windows Server 2019 must, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly. + <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001764 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Turn off AutoPlay" to "Enabled" with "All Drives" 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\Microsoft\Windows\CurrentVersion\policies\Explorer\ - -Value Name: NoDriveTypeAutoRun + SV-103273 + V-93185 + CCI-001851 + Configure the system to, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly. + + + + Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. -Type: REG_DWORD -Value: 0x000000ff (255) +If they are not, this is a finding. - - SRG-OS-000370-GPOS-00155 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000080 - Windows Server 2019 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. - <VulnDiscussion>Using a whitelist provides a configuration management method to allow 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> + + WN19-00-000010 + Windows Server 2019 users with Administrative privileges 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001774 - 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 Server. - -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" at the following link: - -https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm - - - - This 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. - -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 Server. 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". + V-93369 + SV-103457 + CCI-000366 + Ensure each user with administrative privileges 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. -If the AppLocker PowerShell module has not been imported previously, execute the following first: +If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-00-000030 + Windows Server 2019 administrative accounts must 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 account. -Import-Module AppLocker +Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to not access the Internet or use applications such as email. -Execute the following command, substituting [c:\temp\file.xml] with a location and file name appropriate for the system: +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. -Get-AppLockerPolicy -Effective -XML > c:\temp\file.xml +Whitelisting can be used to enforce the policy to ensure compliance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93205 + SV-103293 + CCI-000366 + Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. Ensure the policy is enforced. -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. +The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. + + + + Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. -Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: +If it does not, this is a finding. -https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm +The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000270 - Windows Server 2019 must have the roles and features required by the system documented. - <VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000040 + Windows Server 2019 members 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Document the roles and features required for the system to operate. Uninstall any that are not required. - - - - Required roles and features will vary based on the function of the individual system. - -Roles and features specifically required to be disabled per the STIG are identified in separate requirements. + V-93207 + SV-103295 + CCI-000366 + Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions. + + + + If no accounts are members of the Backup Operators group, this is NA. -If the organization has not documented the roles and features required for the system(s), this is a finding. +Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. -The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State". +If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000320 - Windows Server 2019 must not have the Fax Server role installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + WN19-00-000060 + Windows Server 2019 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization. + <VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "Fax Server" role. + SV-103297 + V-93209 + CCI-000366 + Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization. -Start "Server Manager". +It is recommended that system-managed service accounts be used whenever possible. + + + + Determine if manually managed application/service accounts exist. If none exist, this is NA. -Select the server with the role. +If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. -Scroll down to "ROLES AND FEATURES" in the right pane. +Identify manually managed application/service accounts. -Select "Remove Roles and Features" from the drop-down "TASKS" list. +To determine the date a password was last changed: -Select the appropriate server on the "Server Selection" page and click "Next". +Domain controllers: -Deselect "Fax Server" on the "Roles" page. +Open "PowerShell". -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. -Enter "Get-WindowsFeature | Where Name -eq Fax". +If the "PasswordLastSet" date is more than one year old, this is a finding. + + +Member servers and standalone systems: + +Open "Command Prompt". -If "Installed State" is "Installed", this is a finding. +Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. -An Installed State of "Available" or "Removed" is not a finding. +If the "Password Last Set" date is more than one year old, this is a finding. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000340 - Windows Server 2019 must not have the Peer Name Resolution Protocol installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + WN19-00-000090 + Windows Server 2019 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use. + <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "Peer Name Resolution Protocol" feature. + V-93213 + SV-103301 + CCI-000366 + Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.) -Start "Server Manager". - -Select the server with the feature. +The TPM must be enabled in the firmware. -Scroll down to "ROLES AND FEATURES" in the right pane. +Run "tpm.msc" for configuration options in Windows. + + + + For standalone systems, this is NA. -Select "Remove Roles and Features" from the drop-down "TASKS" list. +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. -Select the appropriate server on the "Server Selection" page and click "Next". +Verify the system has a TPM and it is ready for use. -Deselect "Peer Name Resolution Protocol" on the "Features" page. +Run "tpm.msc". -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +Review the sections in the center pane. -Enter "Get-WindowsFeature | Where Name -eq PNRP". +"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". -If "Installed State" is "Installed", this is a finding. +TPM Manufacturer Information - Specific Version = 2.0 or 1.2 -An Installed State of "Available" or "Removed" is not a finding. +If a TPM is not found or is not ready for use, this is a finding. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000350 - Windows Server 2019 must not have Simple TCP/IP Services installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + WN19-00-000100 + Windows Server 2019 must be maintained at a supported servicing level. + <VulnDiscussion>Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "Simple TCP/IP Services" feature. - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "Simple TCP/IP Services" on the "Features" page. - -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". + SV-103303 + V-93215 + CCI-000366 + Update the system to a Version 1809 (Build 17763.xxx) or greater. + + + + Open "Command Prompt". -Enter "Get-WindowsFeature | Where Name -eq Simple-TCPIP". +Enter "winver.exe". -If "Installed State" is "Installed", this is a finding. +If the "About Windows" dialog box does not display "Microsoft Windows Server Version 1809 (Build 17763.xxx)" or greater, this is a finding. -An Installed State of "Available" or "Removed" is not a finding. +Preview versions must not be used in a production environment. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000370 - Windows Server 2019 must not have the TFTP Client installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + WN19-00-000110 + Windows Server 2019 must use an anti-virus program. + <VulnDiscussion>Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "TFTP Client" feature. + SV-103305 + V-93217 + CCI-000366 + If no anti-virus software is in use, install Windows Defender or third-party anti-virus. -Start "Server Manager". +Open "PowerShell". -Select the server with the feature. +Enter "Install-WindowsFeature -Name Windows-Defender”. -Scroll down to "ROLES AND FEATURES" in the right pane. +For third-party anti-virus, install per anti-virus instructions and disable Windows Defender. -Select "Remove Roles and Features" from the drop-down "TASKS" list. +Open "PowerShell". -Select the appropriate server on the "Server Selection" page and click "Next". +Enter "Uninstall-WindowsFeature -Name Windows-Defender”. + + + + + Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution. -Deselect "TFTP Client" on the "Features" page. +If there is no anti-virus solution installed on the system, this is a finding. -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +Verify if Windows Defender is in use or enabled: -Enter "Get-WindowsFeature | Where Name -eq TFTP-Client". +Open "PowerShell". -If "Installed State" is "Installed", this is a finding. +Enter “get-service | where {$_.DisplayName -Like "*Defender*"} | Select Status,DisplayName” -An Installed State of "Available" or "Removed" is not a finding. +Verify if third-party anti-virus is in use or enabled: + +Open "PowerShell". + +Enter "get-service | where {$_.DisplayName -Like "*mcafee*"} | Select Status,DisplayName” + +Enter "get-service | where {$_.DisplayName -Like "*symantec*"} | Select Status,DisplayName” + - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000380 - Windows Server 2019 must not the Server Message Block (SMB) v1 protocol installed. - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000120 + Windows Server 2019 must have a host-based intrusion detection or prevention system. + <VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the SMBv1 protocol. + SV-103307 + V-93219 + CCI-000366 + Install a HIDS or HIPS on each server. + + + + Determine whether there is a HIDS or HIPS on each server. -Open "Windows PowerShell" with elevated privileges (run as administrator). +If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. -Enter "Uninstall-WindowsFeature -Name FS-SMB1 -Restart". -(Omit the Restart parameter if an immediate restart of the system cannot be done.) +A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. -Alternately: +If a HIDS is not installed on the system, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-00-000240 + Windows Server 2019 must have software certificate installation files removed. + <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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93221 + SV-103309 + CCI-000366 + Remove any certificate installation files (*.p12 and *.pfx) found on a system. -Start "Server Manager". +Note: This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. + + + + Search all drives for *.p12 and *.pfx files. -Select the server with the feature. +If any files with these extensions exist, this is a finding. -Scroll down to "ROLES AND FEATURES" in the right pane. +This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. 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. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-00-000420 + Windows Server 2019 FTP servers must be configured to prevent anonymous logons. + <VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. -Select "Remove Roles and Features" from the drop-down "TASKS" list. +Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93223 + SV-103311 + CCI-000366 + Configure the FTP service to prevent anonymous logons. -Select the appropriate server on the "Server Selection" page and click "Next". +Open "Internet Information Services (IIS) Manager". -Deselect "SMB 1.0/CIFS File Sharing Support" on the "Features" page. +Select the server. -Click "Next" and "Remove" as prompted. - - - - Different methods are available to disable SMBv1 on Windows Server 2019. This is the preferred method, however if WN19-00-000390 and WN19-00-000400 are configured, this is NA. +Double-click "FTP Authentication". -Open "Windows PowerShell" with elevated privileges (run as administrator). +Select "Anonymous Authentication". -Enter "Get-WindowsFeature -Name FS-SMB1". +Select "Disabled" under "Actions". + + + + If FTP is not installed on the system, this is NA. -If "Installed State" is "Installed", this is a finding. +Open "Internet Information Services (IIS) Manager". -An Installed State of "Available" or "Removed" is not a finding. +Select the server. + +Double-click "FTP Authentication". + +If the "Anonymous Authentication" status is "Enabled", this is a finding. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000390 - Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server. - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000430 + Windows Server 2019 FTP servers must be configured to prevent access to the system drive. + <VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 Server" to "Disabled". - -The system must be restarted for the change to take effect. + V-93225 + SV-103313 + CCI-000366 + Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system. + + + + If FTP is not installed on the system, this is NA. -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. - - - - Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. +Open "Internet Information Services (IIS) Manager". -If the following registry value does not exist or is not configured as specified, this is a finding: +Select "Sites" under the server name. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ +For any sites with a Binding that lists FTP, right-click the site and select "Explore". -Value Name: SMB1 +If the site is not defined to a specific folder for shared FTP resources, this is a finding. -Type: REG_DWORD -Value: 0x00000000 (0) +If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000400 - Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client. - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000460 + Windows Server 2019 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS. + <VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 client driver" to "Enabled" with "Disable driver (recommended)" selected for "Configure MrxSmb10 driver". - -The system must be restarted for the changes to take effect. - -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. - - - - Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. - -If the following registry value is not configured as specified, this is a finding: + V-93229 + SV-103317 + CCI-000366 + Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode. + + + + Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must run in "UEFI" mode. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ +Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". -Value Name: Start +Run "System Information". -Type: REG_DWORD -Value: 0x00000004 (4) +Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000410 - Windows Server 2019 must not have Windows PowerShell 2.0 installed. - <VulnDiscussion>Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000470 + Windows Server 2019 must have Secure Boot enabled. + <VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "Windows PowerShell 2.0 Engine". - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". + SV-103319 + V-93231 + CCI-000366 + Enable Secure Boot in the system firmware. + + + + Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must have Secure Boot enabled. -Deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell" on the "Features" page. +Run "System Information". -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. -Enter "Get-WindowsFeature | Where Name -eq PowerShell-v2". +On server core installations, run the following PowerShell command: -If "Installed State" is "Installed", this is a finding. +Confirm-SecureBootUEFI -An Installed State of "Available" or "Removed" is not a finding. +If a value of "True" is not returned, this is a finding. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000010 - Windows Server 2019 must prevent the display of slide shows on the lock screen. - <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> + + WN19-CC-000030 + Windows Server 2019 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> Control Panel >> Personalization >> "Prevent enabling lock screen slide show" to "Enabled". - - - - Verify the registry value below. + SV-103321 + V-93233 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. -If it does not exist or is not configured as specified, this is a finding. +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: \SOFTWARE\Policies\Microsoft\Windows\Personalization\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ -Value Name: NoLockScreenSlideshow +Value Name: DisableIPSourceRouting -Value Type: REG_DWORD -Value: 0x00000001 (1) +Type: REG_DWORD +Value: 0x00000002 (2) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000020 - Windows Server 2019 must have WDigest Authentication 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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is enforced.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000040 + Windows Server 2019 source routing must be configured to the highest protection level to prevent Internet Protocol (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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "WDigest Authentication (disabling may require KB2871997)" to "Disabled". + SV-103323 + V-93235 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. -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. - - - +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ -Value Name: UseLogonCredential +Value Name: DisableIPSourceRouting -Type: REG_DWORD -Value: 0x00000000 (0) +Value Type: REG_DWORD +Value: 0x00000002 (2) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000150 - Windows Server 2019 downloading print driver packages over HTTP 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 will prevent 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> + + WN19-CC-000050 + Windows Server 2019 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 the 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure 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". - - - + SV-103325 + V-93237 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" to "Disabled". + +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ -Value Name: DisableWebPnPDownload +Value Name: EnableICMPRedirect -Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000160 - Windows Server 2019 printing over HTTP 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 will prevent 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> + + WN19-CC-000070 + Windows Server 2019 insecure logons to an SMB server must be disabled. + <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Internet Communication Management >> Internet Communication settings >> "Turn off printing over HTTP" to "Enabled". - - - + SV-103327 + V-93239 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Lanman Workstation >> "Enable insecure guest logons" 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\Printers\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation\ -Value Name: DisableHTTPPrinting +Value Name: AllowInsecureGuestAuth Type: REG_DWORD -Value: 0x00000001 (1) +Value: 0x00000000 (0) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000170 - Windows Server 2019 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 in to Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000080 + Windows Server 2019 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares. + <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure 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. + SV-103329 + V-93241 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Network Provider >> "Hardened UNC Paths" to "Enabled" with at least the following configured in "Hardened UNC Paths" (click the "Show" button to display): + +Value Name: \\*\SYSVOL +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Value Name: \\*\NETLOGON +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + + + + This requirement is applicable to domain-joined systems. For standalone systems, 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\Windows\System\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ -Value Name: DontDisplayNetworkSelectionUI +Value Name: \\*\NETLOGON +Value Type: REG_SZ +Value: RequireMutualAuthentication=1, RequireIntegrity=1 -Value Type: REG_DWORD -Value: 0x00000001 (1) +Value Name: \\*\SYSVOL +Value Type: REG_SZ +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Additional entries would not be a finding. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000200 - Windows Server 2019 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 will prevent 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></IAControls> + + WN19-CC-000100 + Windows Server 2019 must be configured to enable Remote host allows delegation of non-exportable credentials. + <VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Application Compatibility >> "Turn off Inventory Collector" to "Enabled". - - - + V-93243 + SV-103331 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Remote host allows delegation of non-exportable 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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ -Value Name: DisableInventory +Value Name: AllowProtectedCreds Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000300 - Windows Server 2019 Windows Defender SmartScreen must be enabled. - <VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000110 + Windows Server 2019 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection. + <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Configure Windows Defender SmartScreen" to "Enabled" with either option "Warn" or "Warn and prevent bypass" selected. + V-93245 + SV-103333 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Secure Boot" or "Secure Boot and DMA Protection" selected. -Windows 2019 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer. - - - - This is applicable to unclassified systems; for other systems, this is NA. +A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: -If the following registry value does not exist or is not configured as specified, this is a finding: +https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard + + + + For standalone systems, this is NA. + +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. + +Open "PowerShell" with elevated privileges (run as administrator). + +Enter the following: + +"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" + +If "RequiredSecurityProperties" does not include a value of "2" indicating "Secure Boot" (e.g., "{1, 2}"), this is a finding. + +If "Secure Boot and DMA Protection" is configured, "3" will also be displayed in the results (e.g., "{1, 2, 3}"). + +If "VirtualizationBasedSecurityStatus" is not a value of "2" indicating "Running", this is a finding. + +Alternately: + +Run "System Information". + +Under "System Summary", verify the following: + +If "Device Guard Virtualization based security" does not display "Running", this is a finding. + +If "Device Guard Required Security Properties" does not display "Base Virtualization Support, Secure Boot", this is a finding. + +If "Secure Boot and DMA Protection" is configured, "DMA Protection" will also be displayed (e.g., "Base Virtualization Support, Secure Boot, DMA Protection"). + +The policy settings referenced in the Fix section will configure the following registry values. However, due to hardware requirements, the registry values alone do not ensure proper function. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ -Value Name: EnableSmartScreen +Value Name: EnableVirtualizationBasedSecurity +Value Type: REG_DWORD +Value: 0x00000001 (1) +Value Name: RequirePlatformSecurityFeatures Value Type: REG_DWORD -Value: 0x00000001 (1) +Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) + +A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: + +https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000400 - Windows Server 2019 must disable Basic authentication for RSS feeds over HTTP. - <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000130 + Windows Server 2019 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad. + <VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. + V-93249 + SV-103337 + CCI-000366 + The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> "Turn on Basic feed authentication over HTTP" to "Not Configured" or "Disabled". - - - - The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. +If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> "Boot-Start Driver Initialization Policy" to "Not Configured" or "Enabled" with any option other than "All" selected. + + + + The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). If the registry value name below does not exist, this is not a finding. -If it exists and is configured with a value of "0", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. +If it exists and is configured with a value of "0x00000007 (7)", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ +Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ -Value Name: AllowBasicAuthInClear +Value Name: DriverLoadPolicy Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) +Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) + +Possible values for this setting are: +8 - Good only +1 - Good and unknown +3 - Good, unknown and bad but critical +7 - All (which includes "bad" and would be a finding) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000410 - Windows Server 2019 must prevent Indexing of encrypted files. - <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></IAControls> + + WN19-CC-000140 + Windows Server 2019 group policy objects must be reprocessed even if they have not changed. + <VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Search >> "Allow indexing of encrypted files" to "Disabled". - - - + V-93251 + SV-103339 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Group Policy >> "Configure registry policy processing" to "Enabled" with the option "Process even if the Group Policy objects have not changed" 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\Windows Search\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ -Value Name: AllowIndexingEncryptedStoresOrItems +Value Name: NoGPOListChanges -Value Type: REG_DWORD +Type: REG_DWORD Value: 0x00000000 (0) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000130 - Windows Server 2019 domain controllers must run on a machine dedicated to that function. - <VulnDiscussion>Executing application servers on the same host machine with a directory server may substantially weaken the security of the directory server. Web or database server applications usually require the addition of many programs and accounts, increasing the attack surface of the computer. - -Some applications require the addition of privileged accounts, providing potential sources of compromise. Some applications (such as Microsoft Exchange) may require the use of network ports or services conflicting with the directory server. In this case, non-standard ports might be selected, and this could interfere with intrusion detection or prevention services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000180 + Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (on battery). + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Remove additional roles or applications such as web, database, and email from the domain controller. - - - - This applies to domain controllers, it is NA for other systems. - -Review the installed roles the domain controller is supporting. - -Start "Server Manager". + V-93253 + SV-103341 + CCI-000366 + Configure 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: -Select "AD DS" in the left pane and the server name under "Servers" to the right. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ -Select "Add (or Remove) Roles and Features" from "Tasks" in the "Roles and Features" section. (Cancel before any changes are made.) +Value Name: DCSettingIndex -Determine if any additional server roles are installed. A basic domain controller setup will include the following: +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-CC-000190 + Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (plugged in). + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93255 + SV-103343 + CCI-000366 + Configure 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: -- Active Directory Domain Services -- DNS Server -- File and Storage Services +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ -If any roles not requiring installation on a domain controller are installed, this is a finding. +Value Name: ACSettingIndex -A Domain Name System (DNS) server integrated with the directory server (e.g., AD-integrated DNS) is an acceptable application. However, the DNS server must comply with the DNS STIG security requirements. +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-CC-000250 + Windows Server 2019 Telemetry must be configured to Security or Basic. + <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103345 + V-93257 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Data Collection and Preview Builds>> "Allow Telemetry" to "Enabled" with "0 - Security [Enterprise Only]" or "1 - Basic" selected in "Options". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Run "Programs and Features". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DataCollection\ -Review installed applications. +Value Name: AllowTelemetry -If any applications are installed that are not required for the domain controller, this is a finding. +Type: REG_DWORD +Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic) - - SRG-OS-000096-GPOS-00050 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000330 - Windows Server 2019 must not have the Microsoft FTP service installed unless required by the organization. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000260 + Windows Server 2019 Windows Update must not obtain updates from other PCs on the Internet. + <VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000382 - Uninstall the "FTP Server" role. - -Start "Server Manager". - -Select the server with the role. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". + SV-103347 + V-93259 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Delivery Optimization >> "Download Mode" to "Enabled" with any option except "Internet" selected. -Deselect "FTP Server" under "Web Server (IIS)" on the "Roles" page. - -Click "Next" and "Remove" as prompted. - - - - If the server has the role of an FTP server, this is NA. +Acceptable selections include: -Open "PowerShell". +Bypass (100) +Group (2) +HTTP only (0) +LAN (1) +Simple (99) + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Enter "Get-WindowsFeature | Where Name -eq Web-Ftp-Service". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\ -If "Installed State" is "Installed", this is a finding. +Value Name: DODownloadMode -An Installed State of "Available" or "Removed" is not a finding. +Value Type: REG_DWORD +Value: 0x00000000 (0) - No peering (HTTP Only) +0x00000001 (1) - Peers on same NAT only (LAN) +0x00000002 (2) - Local Network / Private group peering (Group) +0x00000063 (99) - Simple download mode, no peering (Simple) +0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) -If the system has the role of an FTP server, this must be documented with the ISSO. +A value of 0x00000003 (3), Internet, is a finding. - - SRG-OS-000096-GPOS-00050 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000360 - Windows Server 2019 must not have the Telnet Client installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + WN19-CC-000320 + Windows Server 2019 Turning 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000382 - Uninstall the "Telnet Client" feature. - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. + V-93261 + SV-103349 + CCI-000366 + The default behavior is for File Explorer heap termination on corruption to be disabled. -Select "Remove Roles and Features" from the drop-down "TASKS" list. +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off heap termination on corruption" to "Not Configured" or "Disabled". + + + + The default behavior is for File Explorer heap termination on corruption to be enabled. -Select the appropriate server on the "Server Selection" page and click "Next". +If the registry Value Name below does not exist, this is not a finding. -Deselect "Telnet Client" on the "Features" page. +If it exists and is configured with a value of "0", this is not a finding. -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +If it exists and is configured with a value of "1", this is a finding. -Enter "Get-WindowsFeature | Where Name -eq Telnet-Client". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -If "Installed State" is "Installed", this is a finding. +Value Name: NoHeapTerminationOnCorruption -An Installed State of "Available" or "Removed" is not a finding. +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) - - SRG-OS-000373-GPOS-00157 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000340 - Windows Server 2019 must not save passwords 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000330 + Windows Server 2019 File Explorer shell protocol must run in protected mode. + <VulnDiscussion>The shell protocol will limit the set of folders that 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002038 - Configure 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: + V-93263 + SV-103351 + CCI-000366 + The default behavior is for shell protected mode to be turned on for File Explorer. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off shell protocol protected mode" to "Not Configured" or "Disabled". + + + + The default behavior is for shell protected mode to be turned on for File Explorer. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ -Value Name: DisablePasswordSaving +Value Name: PreXPSP2ShellProtocolBehavior -Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) - - SRG-OS-000373-GPOS-00157 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000360 - Windows Server 2019 Remote 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000390 + Windows Server 2019 must prevent attachments 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002038 - Configure 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". - - - + V-93265 + SV-103353 + CCI-000366 + Configure 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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ -Value Name: fPromptForPassword +Value Name: DisableEnclosureDownload Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000373-GPOS-00157 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000520 - Windows Server 2019 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000440 + Windows Server 2019 users must be notified if a web-based program attempts to install software. + <VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002038 - Configure 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: + SV-103355 + V-93267 + CCI-000366 + The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> "Prevent Internet Explorer security prompt for Windows Installer scripts" to "Not Configured" or "Disabled". + + + + The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: DisableRunAs +Value Name: SafeForScripting -Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) - - SRG-OS-000373-GPOS-00157 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000380 - Windows Server 2019 User 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000150 + Windows Server 2019 directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access. + <VulnDiscussion>To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002038 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + SV-103359 + V-93271 + CCI-000366 + Configure directory data (outside the root DSE) of a non-public directory to prevent anonymous access. -If the following registry value does not exist or is not configured as specified, this is a finding: +For AD, there are multiple configuration items that could enable anonymous access. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Changing the access permissions on the domain naming context object (from the secure defaults) could enable anonymous access. If the check procedures indicate this is the cause, the process that was used to change the permissions should be reversed. This could have been through the Windows Support Tools ADSI Edit console (adsiedit.msc). -Value Name: FilterAdministratorToken +The dsHeuristics option is used. This is addressed in check V-8555 in the AD Forest STIG. + + + + This applies to domain controllers. It is NA for other systems. -Value Type: REG_DWORD -Value: 0x00000001 (1) +Open "Command Prompt" (not elevated). + +Run "ldp.exe". + +From the "Connection menu", select "Bind". + +Clear the User, Password, and Domain fields. + +Select "Simple bind" for the Bind type and click "OK". + +Confirmation of anonymous access will be displayed at the end: + +res = ldap_simple_bind_s +Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON' + +From the "Browse" menu, select "Search". + +In the Search dialog, enter the DN of the domain naming context (generally something like "dc=disaost,dc=mil") in the Base DN field. + +Clear the Attributes field and select "Run". + +Error messages should display related to Bind and user not authenticated. + +If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding. + +The following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access. + +Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. + +Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address. - - SRG-OS-000373-GPOS-00157 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000410 - Windows Server 2019 User Account Control must automatically deny standard user requests for elevation. - <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-DC-000330 + Windows Server 2019 domain controllers must be configured to allow reset of machine account passwords. + <VulnDiscussion>Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002038 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + V-93273 + SV-103361 + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain controller: Refuse machine account password changes" to "Disabled". + + + + This applies to domain controllers. It is NA for other systems. 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: ConsentPromptBehaviorUser +Value Name: RefusePasswordChange Value Type: REG_DWORD Value: 0x00000000 (0) - - SRG-OS-000373-GPOS-00157 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000440 - Windows Server 2019 User 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. + + WN19-DC-000430 + The password for the krbtgt account on a domain must be reset at least every 180 days. + <VulnDiscussion>The krbtgt account acts as a service account for the Kerberos Key Distribution Center (KDC) service. The account and password are created when a domain is created and the password is typically not changed. If the krbtgt account is compromised, attackers can create valid Kerberos Ticket Granting Tickets (TGT). -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and the amount of time equal to or greater than the maximum Kerberos ticket lifetime, and changing again reduces the risk of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002038 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + V-93211 + SV-103299 + CCI-000366 + Reset the password for the krbtgt account a least every 180 days. The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and changing again reduces the risk of issues. Changing twice in rapid succession forces clients to re-authenticate (including application services) but is desired if a compromise is suspected. -If the following registry value does not exist or is not configured as specified, this is a finding: +PowerShell scripts are available to accomplish this such as at the following link: + +https://gallery.technet.microsoft.com/Reset-the-krbtgt-account-581a9e51 + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Select "Advanced Features" in the "View" menu if not previously selected. + +Select the "Users" node. + +Right click on the krbtgt account and select "Reset password" + +Enter a password that meets password complexity requirements. + +Clear the "User must change password at next logon" check box. + +The system will automatically change this to a system-generated complex password. + + + + This requirement is applicable to domain controllers; it is NA for other systems. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Open "Windows PowerShell". -Value Name: EnableLUA +Enter "Get-ADUser krbtgt -Property PasswordLastSet". -Value Type: REG_DWORD -Value: 0x00000001 (1) +If the "PasswordLastSet" date is more than 180 days old, this is a finding. - - SRG-OS-000104-GPOS-00051 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000070 - Windows Server 2019 shared user accounts must not be permitted. - <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 nonrepudiation or individual accountability for system access and resource usage.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000010 + Windows Server 2019 Exploit Protection system-level mitigation, Data Execution Prevention (DEP), must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Data Execution Prevention (DEP)", are enabled by default at the system level. DEP prevents code from being run from data-only memory pages. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000764 - Remove unapproved shared accounts from the system. + V-93313 + SV-103401 + CCI-000366 + Ensure Exploit Protection system-level mitigation, "Data Execution Prevention (DEP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. -Document required shared accounts with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. - - - - Determine whether any shared accounts exist. If no shared accounts exist, this is NA. +Open "Windows Defender Security Center". -Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. +Select "App & browser control". -If unapproved shared accounts exist, this is a finding. - - - - - SRG-OS-000104-GPOS-00051 - <GroupDescription></GroupDescription> - - WN19-00-000200 - Windows Server 2019 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. 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000764 - Configure all enabled accounts to require passwords. +Select "Exploit protection settings". -The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account. - - - - Review the password required status for enabled user accounts. +Under "System settings", configure "Data Execution Prevention (DEP)" to "On by default" or "Use default (<On>)". -Open "PowerShell". +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn DEP on (other system level EP requirements can be combined under <SystemConfig>): -Domain Controllers: +<SystemConfig> + <DEP Enable="true"></DEP> +</SystemConfig> -Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. -Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". -If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. +Run "Windows PowerShell" with elevated privileges (run as administrator). -Member servers and standalone systems: +Enter "Get-ProcessMitigation -System". -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. +If the status of "DEP: Enable" is "OFF", this is a finding. -Exclude disabled accounts (e.g., DefaultAccount, Guest). +Values that would not be a finding include: -If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. +ON +NOTSET (Default configuration) - - SRG-OS-000105-GPOS-00052 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000310 - Windows Server 2019 Active Directory user accounts, including administrators, must be configured to require the use of a Common Access Card (CAC), Personal Identity Verification (PIV)-compliant hardware token, or Alternate Logon Token (ALT) for user authentication. - <VulnDiscussion>Smart cards such as the CAC support a two-factor authentication technique. This provides a higher level of trust in the asserted identity than use of the username and password for authentication. - -Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000030 + Windows Server 2019 Exploit Protection system-level mitigation, Control flow guard (CFG), must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Control flow guard (CFG)", are enabled by default at the system level. CFG ensures flow integrity for indirect calls. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000765 - CCI-000766 - CCI-000767 - CCI-000768 - CCI-001948 - Configure all user accounts, including administrator accounts, in Active Directory to enable the option "Smart card is required for interactive logon". - -Run "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): - -Select the OU where the user accounts are located. (By default this is the Users node; however, accounts may be under other organization-defined OUs.) - -Right-click the user account and select "Properties". + V-93315 + SV-103403 + CCI-000366 + Ensure Exploit Protection system-level mitigation, "Control flow guard (CFG)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. -Select the "Account" tab. +Open "Windows Defender Security Center". -Check "Smart card is required for interactive logon" in the "Account Options" area. - - - - This applies to domain controllers. It is NA for other systems. +Select "App & browser control". -Open "PowerShell". +Select "Exploit protection settings". -Enter the following: +Under "System settings", configure "Control flow guard (CFG)" to "On by default" or "Use default (<On>)". -"Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name" -("DistinguishedName" may be substituted for "Name" for more detailed output.) +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn CFG on (other system level EP requirements can be combined under <SystemConfig>): -If any user accounts, including administrators, are listed, this is a finding. +<SystemConfig> + <ControlFlowGuard Enable="true"></ControlFlowGuard> +</SystemConfig> +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. -Alternately: +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". -To view sample accounts in "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): +Run "Windows PowerShell" with elevated privileges (run as administrator). -Select the Organizational Unit (OU) where the user accounts are located. (By default, this is the Users node; however, accounts may be under other organization-defined OUs.) +Enter "Get-ProcessMitigation -System". -Right-click the sample user account and select "Properties". +If the status of "CFG: Enable" is "OFF", this is a finding. -Select the "Account" tab. +Values that would not be a finding include: -If any user accounts, including administrators, do not have "Smart card is required for interactive logon" checked in the "Account Options" area, this is a finding. +ON +NOTSET (Default configuration) - - SRG-OS-000112-GPOS-00057 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000020 - Windows Server 2019 Kerberos user logon restrictions must be enforced. - <VulnDiscussion>This policy setting determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer. The policy is enabled by default, which is the most secure setting for validating that access to target resources is not circumvented. - -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000040 + Windows Server 2019 Exploit Protection system-level mitigation, Validate exception chains (SEHOP), must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate exception chains (SEHOP)", are enabled by default at the system level. SEHOP (structured exception handling overwrite protection) ensures the integrity of an exception chain during exception dispatch. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001941 - CCI-001942 - Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Enforce user logon restrictions" to "Enabled". - - - - This applies to domain controllers. It is NA for other systems. + SV-103405 + V-93317 + CCI-000366 + Ensure Exploit Protection system-level mitigation, "Validate exception chains (SEHOP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. -Verify the following is configured in the Default Domain Policy: +Open "Windows Defender Security Center". -Open "Group Policy Management". +Select "App & browser control". -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). +Select "Exploit protection settings". -Right-click on the "Default Domain Policy". +Under "System settings", configure "Validate exception chains (SEHOP)" to "On by default" or "Use default (<On>)". -Select "Edit". +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn SEHOP on (other system level EP requirements can be combined under <SystemConfig>): -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. +<SystemConfig> + <SEHOP Enable="true"></SEHOP> +</SystemConfig> -If the "Enforce user logon restrictions" is not set to "Enabled", this is a finding. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. + +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -System". + +If the status of "SEHOP: Enable" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration) - - SRG-OS-000112-GPOS-00057 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000030 - Windows Server 2019 Kerberos service ticket maximum lifetime must be limited to 600 minutes or less. - <VulnDiscussion>This setting determines the maximum amount of time (in minutes) that a granted session ticket can be used to access a particular service. Session tickets are used only to authenticate new connections with servers. Ongoing operations are not interrupted if the session ticket used to authenticate the connection expires during the connection. - -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000050 + Windows Server 2019 Exploit Protection system-level mitigation, Validate heap integrity, must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate heap integrity", are enabled by default at the system level. "Validate heap integrity" terminates a process when heap corruption is detected. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001941 - CCI-001942 - Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for service ticket" to a maximum of "600" minutes, but not "0", which equates to "Ticket doesn't expire". - - - - This applies to domain controllers. It is NA for other systems. + SV-103407 + V-93319 + CCI-000366 + Ensure Exploit Protection system-level mitigation, "Validate heap integrity" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. -Verify the following is configured in the Default Domain Policy: +Open "Windows Defender Security Center". -Open "Group Policy Management". +Select "App & browser control". -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). +Select "Exploit protection settings". -Right-click on the "Default Domain Policy". +Under "System settings", configure "Validate heap integrity" to "On by default" or "Use default (<On>)". -Select "Edit". +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Validate heap integrity on (other system level EP requirements can be combined under <SystemConfig>): -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. +<SystemConfig> + <Heap TerminateOnError="true"></Heap> +</SystemConfig> -If the value for "Maximum lifetime for service ticket" is "0" or greater than "600" minutes, this is a finding. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. + +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -System". + +If the status of "Heap: TerminateOnError" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration) - - SRG-OS-000112-GPOS-00057 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000040 - Windows Server 2019 Kerberos user ticket lifetime must be limited to 10 hours or less. - <VulnDiscussion>In Kerberos, there are two types of tickets: Ticket Granting Tickets (TGTs) and Service Tickets. Kerberos tickets have a limited lifetime so the time an attacker has to implement an attack is limited. This policy controls how long TGTs can be renewed. With Kerberos, the user's initial authentication to the domain controller results in a TGT, which is then used to request Service Tickets to resources. Upon startup, each computer gets a TGT before requesting a service ticket to the domain controller and any other computers it needs to access. For services that start up under a specified user account, users must always get a TGT first and then get Service Tickets to all computers and services accessed. - -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000060 + Windows Server 2019 Exploit Protection mitigations must be configured for Acrobat.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001941 - CCI-001942 - Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for user ticket" to a maximum of "10" hours but not "0", which equates to "Ticket doesn't expire". - - - - This applies to domain controllers. It is NA for other systems. + V-93321 + SV-103409 + CCI-000366 + Ensure the following mitigations are turned "ON" for Acrobat.exe: -Verify the following is configured in the Default Domain Policy: +DEP: +Enable: ON -Open "Group Policy Management". +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Right-click on the "Default Domain Policy". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Select "Edit". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. +This is applicable to unclassified systems, for other systems this is NA. -If the value for "Maximum lifetime for user ticket" is "0" or greater than "10" hours, this is a finding. +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name Acrobat.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000112-GPOS-00057 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000050 - Windows Server 2019 Kerberos policy user ticket renewal maximum lifetime must be limited to seven days or less. - <VulnDiscussion>This setting determines the period of time (in days) during which a user's Ticket Granting Ticket (TGT) may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access. - -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000070 + Windows Server 2019 Exploit Protection mitigations must be configured for AcroRd32.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001941 - CCI-001942 - Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for user ticket renewal" to a maximum of "7" days or less. - - - - This applies to domain controllers. It is NA for other systems. - -Verify the following is configured in the Default Domain Policy: + V-93323 + SV-103411 + CCI-000366 + Ensure the following mitigations are turned "ON" for AcroRd32.exe: -Open "Group Policy Management". - -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). +DEP: +Enable: ON -Right-click on the "Default Domain Policy". +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Select "Edit". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -If the "Maximum lifetime for user ticket renewal" is greater than "7" days, this is a finding. - - - - - SRG-OS-000112-GPOS-00057 - <GroupDescription></GroupDescription> - - WN19-DC-000060 - Windows Server 2019 computer clock synchronization tolerance must be limited to five minutes or less. - <VulnDiscussion>This setting determines the maximum time difference (in minutes) that Kerberos will tolerate between the time on a client's clock and the time on a server's clock while still considering the two clocks synchronous. In order to prevent replay attacks, Kerberos uses timestamps as part of its protocol definition. For timestamps to work properly, the clocks of the client and the server need to be in sync as much as possible. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001941 - CCI-001942 - Configure the policy value in the Default Domain Policy for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum tolerance for computer clock synchronization" to a maximum of "5" minutes or less. - - - - This applies to domain controllers. It is NA for other systems. +This is applicable to unclassified systems, for other systems this is NA. -Verify the following is configured in the Default Domain Policy: +Run "Windows PowerShell" with elevated privileges (run as administrator). -Open "Group Policy Management". +Enter "Get-ProcessMitigation -Name AcroRd32.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). +If the following mitigations do not have a status of "ON", this is a finding: -Right-click on the "Default Domain Policy". +DEP: +Enable: ON -Select "Edit". +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -If the "Maximum tolerance for computer clock synchronization" is greater than "5" minutes, this is a finding. +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000379-GPOS-00164 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000090 - Windows Server 2019 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 the 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> + + WN19-EP-000080 + Windows Server 2019 Exploit Protection mitigations must be configured for chrome.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001967 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain member: Disable machine account password changes" to "Disabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103413 + V-93325 + CCI-000366 + Ensure the following mitigations are turned "ON" for chrome.exe: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ +DEP: +Enable: ON -Value Name: DisablePasswordChange +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Value Type: REG_DWORD -Value: 0x00000000 (0) +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name chrome.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000118-GPOS-00060 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000190 - Windows Server 2019 outdated or unused accounts must be removed or disabled. - <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, disabled until needed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000090 + Windows Server 2019 Exploit Protection mitigations must be configured for EXCEL.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000795 - Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days. - - - - Open "Windows PowerShell". + SV-103415 + V-93327 + CCI-000366 + Ensure the following mitigations are turned "ON" for EXCEL.EXE: -Domain Controllers: +DEP: +Enable: ON -Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" +ASLR: +ForceRelocateImages: ON -This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Member servers and standalone systems: +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { - $user = ([ADSI]$_.Path) - $lastLogin = $user.Properties.LastLogin.Value - $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 - if ($lastLogin -eq $null) { - $lastLogin = 'Never' - } - Write-Host $user.Name $lastLogin $enabled -}" +This is applicable to unclassified systems, for other systems this is NA. -This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). -For example: User1 10/31/2015 5:49:56 AM True +Run "Windows PowerShell" with elevated privileges (run as administrator). -Review the list of accounts returned by the above queries to determine the finding validity for each account reported. +Enter "Get-ProcessMitigation -Name EXCEL.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Exclude the following accounts: +If the following mitigations do not have a status of "ON", this is a finding: -- Built-in administrator account (Renamed, SID ending in 500) -- Built-in guest account (Renamed, Disabled, SID ending in 501) -- Application accounts +DEP: +Enable: ON -If any enabled accounts have not been logged on to within the past 35 days, this is a finding. +ASLR: +ForceRelocateImages: ON -Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000078-GPOS-00046 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000050 - Windows Server 2019 manually managed application 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></IAControls> + + WN19-EP-000100 + Windows Server 2019 Exploit Protection mitigations must be configured for firefox.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000205 - Establish a policy that requires application/service account passwords that are manually managed to be at least 15 characters in length. Ensure the policy is enforced. - - - - Determine if manually managed application/service accounts exist. If none exist, this is NA. + SV-103417 + V-93329 + CCI-000366 + Ensure the following mitigations are turned "ON" for firefox.exe: -Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. +DEP: +Enable: ON -If such a policy does not exist or has not been implemented, this is a finding. - - - - - SRG-OS-000073-GPOS-00041 - <GroupDescription></GroupDescription> - - WN19-SO-000300 - Windows Server 2019 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 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000196 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Value Name: NoLMHash +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Value Type: REG_DWORD -Value: 0x00000001 (1) +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name firefox.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000074-GPOS-00042 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000180 - Windows Server 2019 unencrypted passwords must not be sent to third-party Server Message Block (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 determine 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> + + WN19-EP-000110 + Windows Server 2019 Exploit Protection mitigations must be configured for FLTLDR.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000197 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93331 + SV-103419 + CCI-000366 + Ensure the following mitigations are turned "ON" for FLTLDR.EXE: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ +DEP: +Enable: ON -Value Name: EnablePlainTextPassword +ImageLoad: +BlockRemoteImageLoads: ON -Value Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000076-GPOS-00044 - <GroupDescription></GroupDescription> - - WN19-00-000020 - Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days. - <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000199 - Change the built-in Administrator account password at least every "60" days. +Child Process: +DisallowChildProcessCreation: ON -Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this. - - - - Review the password last set date for the built-in Administrator account. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Domain controllers: +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Open "PowerShell". +This is applicable to unclassified systems, for other systems this is NA. -Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". +Run "Windows PowerShell" with elevated privileges (run as administrator). -If the "PasswordLastSet" date is greater than "60" days old, this is a finding. +Enter "Get-ProcessMitigation -Name FLTLDR.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Member servers and standalone systems: +If the following mitigations do not have a status of "ON", this is a finding: -Open "Command Prompt". +DEP: +Enable: ON -Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. +ImageLoad: +BlockRemoteImageLoads: ON -(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -If the "PasswordLastSet" date is greater than "60" days old, this is a finding. +Child Process: +DisallowChildProcessCreation: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000076-GPOS-00044 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000210 - Windows Server 2019 passwords must be configured to expire. - <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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> + + WN19-EP-000120 + Windows Server 2019 Exploit Protection mitigations must be configured for GROOVE.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000199 - Configure all enabled user account passwords to expire. + SV-103421 + V-93333 + CCI-000366 + Ensure the following mitigations are turned "ON" for GROOVE.EXE: -Uncheck "Password never expires" for all enabled user accounts in Active Directory Users and Computers for domain accounts and Users in Computer Management for member servers and standalone systems. Document any exceptions with the ISSO. - - - - Review the password never expires status for enabled user accounts. +DEP: +Enable: ON -Open "PowerShell". +ASLR: +ForceRelocateImages: ON -Domain Controllers: +ImageLoad: +BlockRemoteImageLoads: ON -Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. +Child Process: +DisallowChildProcessCreation: ON -If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Member servers and standalone systems: +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. +This is applicable to unclassified systems, for other systems this is NA. -Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). +Run "Windows PowerShell" with elevated privileges (run as administrator). -If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding. +Enter "Get-ProcessMitigation -Name GROOVE.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +ImageLoad: +BlockRemoteImageLoads: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Child Process: +DisallowChildProcessCreation: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000066-GPOS-00034 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000280 - Windows Server 2019 domain controllers must have a PKI server certificate. - <VulnDiscussion>Domain controllers are part of the chain of trust for PKI authentications. Without the appropriate certificate, the authenticity of the domain controller cannot be verified. Domain controllers must have a server certificate to establish authenticity as part of PKI authentications in the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000130 + Windows Server 2019 Exploit Protection mitigations must be configured for iexplore.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000185 - Obtain a server certificate for the domain controller. - - - - This applies to domain controllers. It is NA for other systems. + SV-103423 + V-93335 + CCI-000366 + Ensure the following mitigations are turned "ON" for iexplore.exe: -Run "MMC". +DEP: +Enable: ON -Select "Add/Remove Snap-in" from the "File" menu. +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Select "Certificates" in the left pane and click the "Add >" button. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select "Computer Account" and click "Next". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Click "OK". +This is applicable to unclassified systems, for other systems this is NA. -Select and expand the Certificates (Local Computer) entry in the left pane. +Run "Windows PowerShell" with elevated privileges (run as administrator). -Select and expand the Personal entry in the left pane. +Enter "Get-ProcessMitigation -Name iexplore.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Select the Certificates entry in the left pane. +If the following mitigations do not have a status of "ON", this is a finding: -If no certificate for the domain controller exists in the right pane, this is a finding. +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000066-GPOS-00034 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000290 - Windows Server 2019 domain Controller PKI certificates must be issued by the DoD PKI or an approved External Certificate Authority (ECA). - <VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000140 + Windows Server 2019 Exploit Protection mitigations must be configured for INFOPATH.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000185 - Obtain a server certificate for the domain controller issued by the DoD PKI or an approved ECA. - - - - This applies to domain controllers. It is NA for other systems. - -Run "MMC". - -Select "Add/Remove Snap-in" from the "File" menu. - -Select "Certificates" in the left pane and click the "Add >" button. + SV-103425 + V-93337 + CCI-000366 + Ensure the following mitigations are turned "ON" for INFOPATH.EXE: -Select "Computer Account" and click "Next". +DEP: +Enable: ON -Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". +ASLR: +ForceRelocateImages: ON -Click "OK". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select and expand the Certificates (Local Computer) entry in the left pane. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Select and expand the Personal entry in the left pane. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Select the Certificates entry in the left pane. +This is applicable to unclassified systems, for other systems this is NA. -In the right pane, examine the "Issued By" field for the certificate to determine the issuing CA. +Run "Windows PowerShell" with elevated privileges (run as administrator). -If the "Issued By" field of the PKI certificate being used by the domain controller does not indicate the issuing CA is part of the DoD PKI or an approved ECA, this is a finding. +Enter "Get-ProcessMitigation -Name INFOPATH.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -If the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding. +If the following mitigations do not have a status of "ON", this is a finding: -There are multiple sources from which lists of valid DoD CAs and approved ECAs can be obtained: +DEP: +Enable: ON -The Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil. +ASLR: +ForceRelocateImages: ON -DoD Public Key Enablement (PKE) Engineering Support maintains the InstallRoot utility to manage DoD supported root certificates on Windows computers, which includes a list of authorized CAs. The utility package can be downloaded from the PKI and PKE Tools page on IASE: +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -http://iase.disa.mil/pki-pke/function_pages/tools.html +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000066-GPOS-00034 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000300 - Windows Server 2019 PKI certificates associated with user accounts must be issued by a DoD PKI or an approved External Certificate Authority (ECA). - <VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000150 + Windows Server 2019 Exploit Protection mitigations must be configured for java.exe, javaw.exe, and javaws.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000185 - Map user accounts to PKI certificates using the appropriate User Principal Name (UPN) for the network. See PKE documentation for details. - - - - This applies to domain controllers. It is NA for other systems. + SV-103427 + V-93339 + CCI-000366 + Ensure the following mitigations are turned "ON" for java.exe, javaw.exe, and javaws.exe: -Review user account mappings to PKI certificates. +DEP: +Enable: ON -Open "Windows PowerShell". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Enter "Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Exclude disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -If the User Principal Name (UPN) is not in the format of an individual's identifier for the certificate type and for the appropriate domain suffix, this is a finding. +This is applicable to unclassified systems, for other systems this is NA. -For standard NIPRNet certificates, the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI). +Run "Windows PowerShell" with elevated privileges (run as administrator). -Alt Tokens and other certificates may use a different UPN format than the EDI-PI which vary by organization. Verified these with the organization. +Enter "Get-ProcessMitigation -Name [application name]" with each of the following substituted for [application name]: +java.exe, javaw.exe, and javaws.exe +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -NIPRNet Example: +If the following mitigations do not have a status of "ON" for each, this is a finding: -Name - User Principal Name -User1 - 1234567890@mil +DEP: +Enable: ON -See PKE documentation for other network domain suffixes. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -If the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding. +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000066-GPOS-00034 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-PK-000010 - Windows Server 2019 must have the DoD Root Certificate Authority (CA) certificates 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 CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000160 + Windows Server 2019 Exploit Protection mitigations must be configured for lync.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000185 - CCI-002470 - Install the DoD Root CA certificates: + SV-103429 + V-93341 + CCI-000366 + Ensure the following mitigations are turned "ON" for lync.exe: -DoD Root CA 2 -DoD Root CA 3 -DoD Root CA 4 -DoD Root CA 5 - -The InstallRoot tool is available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx. - - - - The certificates and thumbprints referenced below apply to unclassified systems; see PKE documentation for other networks. - -Open "Windows PowerShell" as an administrator. - -Execute the following command: +DEP: +Enable: ON -Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint, NotAfter +ASLR: +ForceRelocateImages: ON -If the following certificate "Subject" and "Thumbprint" information is not displayed, this is a finding. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -If an expired certificate ("NotAfter" date) is not listed in the results, this is not a finding. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 -NotAfter: 12/5/2029 +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB -NotAfter: 12/30/2029 +This is applicable to unclassified systems, for other systems this is NA. -Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 -NotAfter: 7/25/2032 +Run "Windows PowerShell" with elevated privileges (run as administrator). -Subject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B -NotAfter: 6/14/2041 +Enter "Get-ProcessMitigation -Name lync.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Alternately, use the Certificates MMC snap-in: +If the following mitigations do not have a status of "ON", this is a finding: -Run "MMC". +DEP: +Enable: ON -Select "File", "Add/Remove Snap-in". +ASLR: +ForceRelocateImages: ON -Select "Certificates" and click "Add". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select "Computer account" and click "Next". +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-EP-000170 + Windows Server 2019 Exploit Protection mitigations must be configured for MSACCESS.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103431 + V-93343 + CCI-000366 + Ensure the following mitigations are turned "ON" for MSACCESS.EXE: -Select "Local computer: (the computer this console is running on)" and click "Finish". +DEP: +Enable: ON -Click "OK". +ASLR: +ForceRelocateImages: ON -Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -For each of the DoD Root CA certificates noted below: +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Right-click on the certificate and select "Open". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Select the "Details" Tab. +This is applicable to unclassified systems, for other systems this is NA. -Scroll to the bottom and select "Thumbprint". +Run "Windows PowerShell" with elevated privileges (run as administrator). -If the DoD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. +Enter "Get-ProcessMitigation -Name MSACCESS.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -If an expired certificate ("Valid to" date) is not listed in the results, this is not a finding. +If the following mitigations do not have a status of "ON", this is a finding: -DoD Root CA 2 -Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 -Valid to: Wednesday, December 5, 2029 +DEP: +Enable: ON -DoD Root CA 3 -Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB -Valid to: Sunday, December 30, 2029 +ASLR: +ForceRelocateImages: ON -DoD Root CA 4 -Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 -Valid to: Sunday, July 25, 2032 +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -DoD Root CA 5 -Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B -Valid to: Friday, June 14, 2041 +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000066-GPOS-00034 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-PK-000020 - Windows Server 2019 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates 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. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000180 + Windows Server 2019 Exploit Protection mitigations must be configured for MSPUB.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000185 - CCI-002470 - Install 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 + SV-103433 + V-93345 + CCI-000366 + Ensure the following mitigations are turned "ON" for MSPUB.EXE: -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 are available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx. - - - - This is applicable to unclassified systems. It is NA for others. - -Open "PowerShell" as an administrator. +DEP: +Enable: ON -Execute the following command: +ASLR: +ForceRelocateImages: ON -Get-ChildItem -Path Cert:Localmachine\disallowed | Where {$_.Issuer -Like "*DoD Interoperability*" -and $_.Subject -Like "*DoD*"} | FL Subject, Issuer, Thumbprint, NotAfter +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -If an expired certificate ("NotAfter" date) is not listed in the results, this is not a finding. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -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 -NotAfter: 9/6/2019 +This is applicable to unclassified systems, for other systems this is NA. -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 -NotAfter: 2/17/2019 +Run "Windows PowerShell" with elevated privileges (run as administrator). -Alternately, use the Certificates MMC snap-in: +Enter "Get-ProcessMitigation -Name MSPUB.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Run "MMC". +If the following mitigations do not have a status of "ON", this is a finding: -Select "File", "Add/Remove Snap-in". +DEP: +Enable: ON -Select "Certificates" and click "Add". +ASLR: +ForceRelocateImages: ON -Select "Computer account" and click "Next". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select "Local computer: (the computer this console is running on)" and click "Finish". +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-EP-000190 + Windows Server 2019 Exploit Protection mitigations must be configured for OIS.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93347 + SV-103435 + CCI-000366 + Ensure the following mitigations are turned "ON" for OIS.EXE: -Click "OK". +DEP: +Enable: ON -Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -For each certificate with "DoD Root CA..." under "Issued To" and "DoD Interoperability Root CA..." under "Issued By": +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Right-click on the certificate and select "Open". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Select the "Details" Tab. +This is applicable to unclassified systems, for other systems this is NA. -Scroll to the bottom and select "Thumbprint". +Run "Windows PowerShell" with elevated privileges (run as administrator). -If the certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. +Enter "Get-ProcessMitigation -Name OIS.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -If an expired certificate ("Valid to" date) is not listed in the results, this is not a finding. +If the following mitigations do not have a status of "ON", this is a finding: -Issued To: DoD Root CA 2 -Issued By: DoD Interoperability Root CA 1 -Thumbprint: 22BBE981F0694D246CC1472ED2B021DC8540A22F -Valid to: Friday, September 6, 2019 +DEP: +Enable: ON -Issued To: DoD Root CA 3 -Issued By: DoD Interoperability Root CA 2 -Thumbprint: FFAD03329B9E527A43EEC66A56F9CBB5393E6E13 -Valid to: Sunday, September 23, 2018 +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Issued To: DoD Root CA 3 -Issued By: DoD Interoperability Root CA 2 -Thumbprint: FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4 -Valid to: Sunday, February 17, 2019 +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000066-GPOS-00034 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-PK-000030 - Windows Server 2019 must have the US DoD CCEB Interoperability Root CA cross-certificates 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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000200 + Windows Server 2019 Exploit Protection mitigations must be configured for OneDrive.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000185 - CCI-002470 - Install the US DoD CCEB Interoperability Root CA cross-certificate on unclassified systems. + V-93349 + SV-103437 + CCI-000366 + Ensure the following mitigations are turned "ON" for OneDrive.exe: -Issued To - Issued By - Thumbprint -DoD Root CA 2 - US DoD CCEB Interoperability Root CA 1 - DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3 +DEP: +Enable: ON -DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - 929BF3196896994C0A201DF4A5B71F603FEFBF2E +ASLR: +ForceRelocateImages: ON -Administrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. +ImageLoad: +BlockRemoteImageLoads: ON -The FBCA Cross-Certificate Remover Tool and User Guide are available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx. - - - - This is applicable to unclassified systems. It is NA for others. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Open "PowerShell" as an administrator. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Execute the following command: +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter +This is applicable to unclassified systems, for other systems this is NA. -If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. +Run "Windows PowerShell" with elevated privileges (run as administrator). -If an expired certificate ("NotAfter" date) is not listed in the results, this is not a finding. +Enter "Get-ProcessMitigation -Name OneDrive.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -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 -NotAfter: 3/9/2019 +If the following mitigations do not have a status of "ON", this is a finding: -Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US -Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E -NotAfter: 9/27/2019 +DEP: +Enable: ON -Alternately, use the Certificates MMC snap-in: +ASLR: +ForceRelocateImages: ON -Run "MMC". +ImageLoad: +BlockRemoteImageLoads: ON -Select "File", "Add/Remove Snap-in". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select "Certificates" and click "Add". +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-EP-000210 + Windows Server 2019 Exploit Protection mitigations must be configured for OUTLOOK.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93351 + SV-103439 + CCI-000366 + Ensure the following mitigations are turned "ON" for OUTLOOK.EXE: -Select "Computer account" and click "Next". +DEP: +Enable: ON -Select "Local computer: (the computer this console is running on)" and click "Finish". +ASLR: +ForceRelocateImages: ON -Click "OK". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -For each certificate with "US DoD CCEB Interoperability Root CA ..." under "Issued By": +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Right-click on the certificate and select "Open". +This is applicable to unclassified systems, for other systems this is NA. -Select the "Details" Tab. +Run "Windows PowerShell" with elevated privileges (run as administrator). -Scroll to the bottom and select "Thumbprint". +Enter "Get-ProcessMitigation -Name OUTLOOK.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -If the certificate below is not listed or the value for the "Thumbprint" field is not as noted, this is a finding. +If the following mitigations do not have a status of "ON", this is a finding: -If an expired certificate ("Valid to" date) is not listed in the results, this is not a finding. +DEP: +Enable: ON -Issued To: DoD Root CA 2 -Issued By: US DoD CCEB Interoperability Root CA 1 -Thumbprint: DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3 -Valid to: Saturday, March 9, 2019 +ASLR: +ForceRelocateImages: ON -Issued To: DoD Root CA 3 -Issuer by: US DoD CCEB Interoperability Root CA 2 -Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E -Valid: Friday, September 27, 2019 +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000067-GPOS-00035 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000350 - Windows Server 2019 users must be required to enter a password to access private keys stored on the computer. - <VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. - -The cornerstone of the PKI is the private key used to encrypt or digitally sign information. - -If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. - -Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000220 + Windows Server 2019 Exploit Protection mitigations must be configured for plugin-container.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000186 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "System cryptography: Force strong key protection for user keys stored on the computer" to "User must enter a password each time they use a key". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93353 + SV-103441 + CCI-000366 + Ensure the following mitigations are turned "ON" for plugin-container.exe: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Cryptography\ +DEP: +Enable: ON -Value Name: ForceKeyProtection +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Type: REG_DWORD -Value: 0x00000002 (2) - - - - - SRG-OS-000120-GPOS-00061 - <GroupDescription></GroupDescription> - - WN19-SO-000290 - Windows Server 2019 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites. - <VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000803 - Configure 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: +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -AES128_HMAC_SHA1 -AES256_HMAC_SHA1 -Future encryption types +This is applicable to unclassified systems, for other systems this is NA. -Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship. - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Run "Windows PowerShell" with elevated privileges (run as administrator). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\ +Enter "Get-ProcessMitigation -Name plugin-container.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Value Name: SupportedEncryptionTypes +If the following mitigations do not have a status of "ON", this is a finding: -Value Type: REG_DWORD -Value: 0x7ffffff8 (2147483640) +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000393-GPOS-00173 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000480 - Windows Server 2019 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. - -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000230 + Windows Server 2019 Exploit Protection mitigations must be configured for POWERPNT.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002890 - CCI-003123 - Configure 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: + V-93355 + SV-103443 + CCI-000366 + Ensure the following mitigations are turned "ON" for POWERPNT.EXE: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ +DEP: +Enable: ON -Value Name: AllowUnencryptedTraffic +ASLR: +ForceRelocateImages: ON -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000393-GPOS-00173 - <GroupDescription></GroupDescription> - - WN19-CC-000510 - Windows Server 2019 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. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-002890 - CCI-003123 - Configure 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: +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Value Name: AllowUnencryptedTraffic +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name POWERPNT.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Type: REG_DWORD -Value: 0x00000000 (0) +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000125-GPOS-00065 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000470 - Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000240 + Windows Server 2019 Exploit Protection mitigations must be configured for PPTVIEW.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000877 - Configure 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: + V-93357 + SV-103445 + CCI-000366 + Ensure the following mitigations are turned "ON" for PPTVIEW.EXE: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ +DEP: +Enable: ON -Value Name: AllowBasic +ASLR: +ForceRelocateImages: ON -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000125-GPOS-00065 - <GroupDescription></GroupDescription> - - WN19-CC-000490 - Windows Server 2019 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. Disallowing Digest authentication will reduce this potential.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000877 - Configure 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: +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Value Name: AllowDigest +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000125-GPOS-00065 - <GroupDescription></GroupDescription> - - WN19-CC-000500 - Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000877 - Configure 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: +This is applicable to unclassified systems, for other systems this is NA. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ +Run "Windows PowerShell" with elevated privileges (run as administrator). -Value Name: AllowBasic +Enter "Get-ProcessMitigation -Name PPTVIEW.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Type: REG_DWORD -Value: 0x00000000 (0) +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000163-GPOS-00072 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000160 - Windows Server 2019 directory service must be configured to terminate LDAP-based network connections to the directory server after five minutes of inactivity. - <VulnDiscussion>The failure to terminate inactive network connections increases the risk of a successful attack on the directory server. The longer an established session is in progress, the more time an attacker has to hijack the session, implement a means to passively intercept data, or compromise any protections on client access. For example, if an attacker gains control of a client computer, an existing (already authenticated) session with the directory server could allow access to the directory. The lack of confidentiality protection in LDAP-based sessions increases exposure to this vulnerability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000250 + Windows Server 2019 Exploit Protection mitigations must be configured for VISIO.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001133 - Configure the directory service to terminate LDAP-based network connections to the directory server after 5 minutes of inactivity. + SV-103447 + V-93359 + CCI-000366 + Ensure the following mitigations are turned "ON" for VISIO.EXE: -Open an elevated "Command prompt" (run as administrator). +DEP: +Enable: ON -Enter "ntdsutil". +ASLR: +ForceRelocateImages: ON -At the "ntdsutil:" prompt, enter "LDAP policies". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -At the "ldap policy:" prompt, enter "connections". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -At the "server connections:" prompt, enter "connect to server [host-name]" (where [host-name] is the computer name of the domain controller). +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -At the "server connections:" prompt, enter "q". +This is applicable to unclassified systems, for other systems this is NA. -At the "ldap policy:" prompt, enter "Set MaxConnIdleTime to 300". +Run "Windows PowerShell" with elevated privileges (run as administrator). -Enter "Commit Changes" to save. +Enter "Get-ProcessMitigation -Name VISIO.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Enter "Show values" to verify changes. +If the following mitigations do not have a status of "ON", this is a finding: -Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit. - - - - This applies to domain controllers. It is NA for other systems. +DEP: +Enable: ON -Open an elevated "Command Prompt" (run as administrator). +ASLR: +ForceRelocateImages: ON -Enter "ntdsutil". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -At the "ntdsutil:" prompt, enter "LDAP policies". +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-EP-000260 + Windows Server 2019 Exploit Protection mitigations must be configured for VPREVIEW.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103449 + V-93361 + CCI-000366 + Ensure the following mitigations are turned "ON" for VPREVIEW.EXE: -At the "ldap policy:" prompt, enter "connections". +DEP: +Enable: ON -At the "server connections:" prompt, enter "connect to server [host-name]" -(where [host-name] is the computer name of the domain controller). +ASLR: +ForceRelocateImages: ON -At the "server connections:" prompt, enter "q". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -At the "ldap policy:" prompt, enter "show values". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -If the value for MaxConnIdleTime is greater than "300" (5 minutes) or is not specified, this is a finding. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit. +This is applicable to unclassified systems, for other systems this is NA. -Alternately, Dsquery can be used to display MaxConnIdleTime: +Run "Windows PowerShell" with elevated privileges (run as administrator). -Open "Command Prompt (Admin)". -Enter the following command (on a single line). +Enter "Get-ProcessMitigation -Name VPREVIEW.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -dsquery * "cn=Default Query Policy,cn=Query-Policies,cn=Directory Service, cn=Windows NT,cn=Services,cn=Configuration,dc=[forest-name]" -attr LDAPAdminLimits +If the following mitigations do not have a status of "ON", this is a finding: -The quotes are required and dc=[forest-name] is the fully qualified LDAP name of the domain being reviewed (e.g., dc=disaost,dc=mil). +DEP: +Enable: ON -If the results do not specify a "MaxConnIdleTime" or it has a value greater than "300" (5 minutes), this is a finding. +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000478-GPOS-00223 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000360 - Windows Server 2019 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing. - <VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000270 + Windows Server 2019 Exploit Protection mitigations must be configured for WINWORD.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002450 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93363 + SV-103451 + CCI-000366 + Ensure the following mitigations are turned "ON" for WINWORD.EXE: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ +DEP: +Enable: ON -Value Name: Enabled +ASLR: +ForceRelocateImages: ON -Value Type: REG_DWORD -Value: 0x00000001 (1) +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -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; otherwise. the browser will not be able to connect to a secure site. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name WINWORD.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000396-GPOS-00176 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000140 - Windows Server 2019 must use separate, NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level when replication data traverses a network cleared to a lower level than the data. - <VulnDiscussion>Directory data that is not appropriately encrypted is subject to compromise. Commercial-grade encryption does not provide adequate protection when the classification level of directory data in transit is higher than the level of the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000280 + Windows Server 2019 Exploit Protection mitigations must be configured for wmplayer.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002450 - Configure NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level that transfer replication data through a network cleared to a lower level than the data. - - - - This applies to domain controllers. It is NA for other systems. + V-93365 + SV-103453 + CCI-000366 + Ensure the following mitigations are turned "ON" for wmplayer.exe: -Review the organization network diagram(s) or documentation to determine the level of classification for the network(s) over which replication data is transmitted. +DEP: +Enable: ON -Determine the classification level of the Windows domain controller. +Payload: +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -If the classification level of the Windows domain controller is higher than the level of the networks, review the organization network diagram(s) and directory implementation documentation to determine if NSA-approved encryption is used to protect the replication network traffic. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -If the classification level of the Windows domain controller is higher than the level of the network traversed and NSA-approved encryption is not used, this is a finding. - - - - - SRG-OS-000185-GPOS-00079 - <GroupDescription></GroupDescription> - - WN19-00-000250 - Windows Server 2019 systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. - <VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). +This is applicable to unclassified systems, for other systems this is NA. -Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001199 - CCI-002475 - CCI-002476 - Configure systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data to employ encryption to protect the confidentiality and integrity of all information at rest. - - - - Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. +Run "Windows PowerShell" with elevated privileges (run as administrator). -If they do not, this is a finding. - - - - - SRG-OS-000134-GPOS-00068 - <GroupDescription></GroupDescription> - - WN19-CC-000240 - Windows Server 2019 administrator accounts must not be enumerated during elevation. - <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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001084 - Configure 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: +Enter "Get-ProcessMitigation -Name wmplayer.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ +If the following mitigations do not have a status of "ON", this is a finding: -Value Name: EnumerateAdministrators +DEP: +Enable: ON -Type: REG_DWORD -Value: 0x00000000 (0) +Payload: +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000134-GPOS-00068 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000390 - Windows Server 2019 UIAccess applications must not be allowed to prompt for elevation without using 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 prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000290 + Windows Server 2019 Exploit Protection mitigations must be configured for wordpad.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001084 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" to "Disabled". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + SV-103455 + V-93367 + CCI-000366 + Ensure the following mitigations are turned "ON" for wordpad.exe: -If the following registry value does not exist or is not configured as specified, this is a finding: +DEP: +Enable: ON -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Value Name: EnableUIADesktopToggle +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Value Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000134-GPOS-00068 - <GroupDescription></GroupDescription> - - WN19-SO-000400 - Windows Server 2019 User Account Control must, at a 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001084 - Configure 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". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -The more secure option for this setting, "Prompt for credentials on the secure desktop", would also be acceptable. - - - - UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). +This is applicable to unclassified systems, for other systems this is NA. -If the following registry value does not exist or is not configured as specified, this is a finding: +Run "Windows PowerShell" with elevated privileges (run as administrator). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Enter "Get-ProcessMitigation -Name wordpad.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Value Name: ConsentPromptBehaviorAdmin +If the following mitigations do not have a status of "ON", this is a finding: -Value Type: REG_DWORD -Value: 0x00000002 (2) (Prompt for consent on the secure desktop) -0x00000001 (1) (Prompt for credentials on the secure desktop) +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000134-GPOS-00068 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000420 - Windows Server 2019 User 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></IAControls> + + WN19-SO-000020 + Windows Server 2019 must prevent local accounts with blank passwords from being used 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 does 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001084 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + V-93279 + SV-103367 + CCI-000366 + Configure 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". + + + + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: EnableInstallerDetection +Value Name: LimitBlankPasswordUse Value Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000134-GPOS-00068 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000430 - Windows Server 2019 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations. - <VulnDiscussion>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> + + WN19-SO-000100 + Windows Server 2019 maximum age for machine account passwords must be configured to 30 days or less. + <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 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001084 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + SV-103373 + V-93285 + CCI-000366 + This is the default configuration for this setting (30 days). + +Configure 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). + + + + This is the default configuration for this setting (30 days). 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: EnableSecureUIAPaths +Value Name: MaximumPasswordAge Value Type: REG_DWORD -Value: 0x00000001 (1) +Value: 0x0000001e (30) (or less, but not 0) - - SRG-OS-000134-GPOS-00068 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000450 - Windows Server 2019 User Account Control (UAC) must virtualize file and registry write failures to per-user locations. - <VulnDiscussion>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></IAControls> + + WN19-SO-000150 + Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001084 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + V-93287 + SV-103375 + CCI-000366 + Configure 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". + + + + 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\ +Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ -Value Name: EnableVirtualization +Value Name: scremoveoption -Value Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_SZ +Value: 1 (Lock Workstation) or 2 (Force Logoff) + +If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO. - - SRG-OS-000138-GPOS-00069 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000230 - Windows Server 2019 non-system-created file shares must limit access to groups that require it. - <VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000210 + Windows Server 2019 must not allow anonymous SID/Name translation. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001090 - If a non-system-created 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. - - - - If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) - -Run "Computer Management". - -Navigate to System Tools >> Shared Folders >> Shares. - -Right-click any non-system-created shares. - -Select "Properties". - -Select the "Share Permissions" tab. + SV-103377 + V-93289 + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Allow anonymous SID/Name translation" to "Disabled". + + + + Verify the effective setting in Local Group Policy Editor. -If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. +Run "gpedit.msc". -Select the "Security" tab. +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. -If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. +If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding. - - SRG-OS-000138-GPOS-00069 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000350 - Windows Server 2019 Remote Desktop Services must prevent drive redirection. - <VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls> + + WN19-SO-000220 + Windows Server 2019 must not allow anonymous enumeration of Security Account Manager (SAM) accounts. + <VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001090 - Configure 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". - - - + V-93291 + SV-103379 + CCI-000366 + Configure 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". + + + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: fDisableCdm +Value Name: RestrictAnonymousSAM -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000138-GPOS-00069 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000120 - Windows Server 2019 data files owned by users must be on a different logical partition from the directory server data files. - <VulnDiscussion>When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. - -The directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000240 + Windows Server 2019 must be configured to prevent anonymous users from having the same permissions as the Everyone group. + <VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001090 - Move shares used to store files owned by users to a different logical partition than the directory server data files. - - - - This applies to domain controllers. It is NA for other systems. - -Run "Regedit". - -Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". - -Note the directory locations in the values for "DSA Database file". - -Open "Command Prompt". - -Enter "net share". + V-93293 + SV-103381 + CCI-000366 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Note the logical drive(s) or file system partition for any organization-created data shares. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Ignore system shares (e.g., NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) should not be ignored. +Value Name: EveryoneIncludesAnonymous -If user shares are located on the same logical partition as the directory server data files, this is a finding. +Value Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000138-GPOS-00069 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000230 - Windows Server 2019 must not allow anonymous enumeration of shares. - <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></IAControls> + + WN19-SO-000260 + Windows Server 2019 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously. + <VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001090 - Configure 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". - - - + SV-103383 + V-93295 + CCI-000366 + Configure 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". + + + 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\Lsa\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\ -Value Name: RestrictAnonymous +Value Name: UseMachineId -Value Type: REG_DWORD +Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000138-GPOS-00069 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000250 - Windows Server 2019 must restrict anonymous access to Named Pipes and Shares. - <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></IAControls> + + WN19-SO-000270 + Windows Server 2019 must prevent NTLM 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001090 - Configure 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". - - - + V-93297 + SV-103385 + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network security: Allow LocalSystem NULL session fallback" 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: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ -Value Name: RestrictNullSessAccess +Value Name: allownullsessionfallback -Value Type: REG_DWORD -Value: 0x00000001 (1) +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000420-GPOS-00186 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000060 - Windows Server 2019 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 server's 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> + + WN19-SO-000280 + Windows Server 2019 must prevent PKU2U authentication using online identities. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002385 - Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" to "Enabled". - -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. - - - + SV-103387 + V-93299 + CCI-000366 + Configure 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". + + + 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\Services\Netbt\Parameters\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\pku2u\ -Value Name: NoNameReleaseOnDemand +Value Name: AllowOnlineID -Value Type: REG_DWORD -Value: 0x00000001 (1) +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000425-GPOS-00189 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000260 - Windows Server 2019 must implement protection methods such as TLS, encrypted VPNs, or IPsec if the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. - <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. - -Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. - -Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. - -Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000310 + Windows Server 2019 LAN Manager authentication level must be configured 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 standalone 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002420 - CCI-002422 - Configure protection methods such as TLS, encrypted VPNs, or IPsec when the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. - - - - If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. + SV-103389 + V-93301 + CCI-000366 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If protection methods have not been implemented, this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ + +Value Name: LmCompatibilityLevel + +Value Type: REG_DWORD +Value: 0x00000005 (5) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-DC-000320 - Windows Server 2019 domain controllers must require LDAP access signing. - <VulnDiscussion>Unsigned network traffic is susceptible to man-in-the-middle attacks, where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. The risk of an attacker pulling this off can be decreased by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPsec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man-in-the-middle attacks extremely difficult. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000320 + Windows Server 2019 must be configured to at least negotiate signing for LDAP client signing. + <VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain controller: LDAP server signing requirements" to "Require signing". - - - - This applies to domain controllers. It is NA for other systems. - -If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103391 + V-93303 + CCI-000366 + Configure 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. + + + + 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\Services\NTDS\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LDAP\ -Value Name: LDAPServerIntegrity +Value Name: LDAPClientIntegrity Value Type: REG_DWORD -Value: 0x00000002 (2) +Value: 0x00000001 (1) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000060 - Windows Server 2019 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000330 + Windows Server 2019 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption. + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - + SV-103393 + V-93305 + CCI-000366 + Configure 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). + + + 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ -Value Name: RequireSignOrSeal +Value Name: NTLMMinClientSec Value Type: REG_DWORD -Value: 0x00000001 (1) +Value: 0x20080000 (537395200) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000070 - Windows Server 2019 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000340 + Windows Server 2019 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption. + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - + SV-103395 + V-93307 + CCI-000366 + Configure 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). + + + 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ -Value Name: SealSecureChannel +Value Name: NTLMMinServerSec Value Type: REG_DWORD -Value: 0x00000001 (1) +Value: 0x20080000 (537395200) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000080 - Windows Server 2019 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000370 + Windows Server 2019 default permissions of global system objects must be strengthened. + <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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - + V-93309 + SV-103397 + CCI-000366 + Configure 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". + + + 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\ -Value Name: SignSecureChannel +Value Name: ProtectionMode Value Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000110 - Windows Server 2019 must be configured to require a strong session key. - <VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-UC-000010 + Windows Server 2019 must preserve zone information when saving attachments. + <VulnDiscussion>Attachments from outside sources may contain malicious code. 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103399 + V-93311 + CCI-000366 + The default behavior is for Windows to mark file attachments with their zone information. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ +If this needs to be corrected, configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager >> "Do not preserve zone information in file attachments" to "Not Configured" or "Disabled". + + + + The default behavior is for Windows to mark file attachments with their zone information. -Value Name: RequireStrongKey +If the registry Value Name below does not exist, this is not a finding. -Value Type: REG_DWORD -Value: 0x00000001 (1) +If it exists and is configured with a value of "2", this is not a finding. -This setting may prevent a system from being joined to a domain if not configured consistently between systems. +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ + +Value Name: SaveZoneInformation + +Value Type: REG_DWORD +Value: 0x00000002 (2) (or if the Value Name does not exist) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00229 <GroupDescription></GroupDescription> - - WN19-SO-000160 - Windows Server 2019 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000450 + Windows Server 2019 must disable automatically signing in the last interactive user after a system-initiated restart. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network client: Digitally sign communications (always)" to "Enabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103357 + V-93269 + CCI-000366 + Configure 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: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: RequireSecuritySignature +Value Name: DisableAutomaticRestartSignOn Value Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000170 - Windows Server 2019 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled. - <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. + + WN19-00-000280 + Windows Server 2019 must have a host-based firewall installed and enabled. + <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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93571 + SV-103657 + CCI-002080 + CCI-000366 + Install and enable a host-based firewall on the system. + + + + Determine if a host-based firewall is installed and enabled on the system. -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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. + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN19-CC-000451 + The Windows Explorer Preview pane must be disabled for Windows Server 2019. + <VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. + +Organizations must disable the Windows Preview pane and Windows Detail pane.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-102625 + SV-111575 + CCI-000366 + Ensure the following settings are configured for Windows Server 2019 locally or applied through group policy. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ +Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn off Preview Pane" to "Enabled". -Value Name: EnableSecuritySignature +Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn on or off details pane" to "Enabled" and "Configure details pane" to "Always hide". + + + + If the following registry values do not exist or are not configured as specified, this is a finding: + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + +Value Name: NoPreviewPane Value Type: REG_DWORD -Value: 0x00000001 (1) + +Value: 1 + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + +Value Name: NoReadingPane + +Value Type: REG_DWORD + +Value: 1 - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000021-GPOS-00005 <GroupDescription></GroupDescription> - - WN19-SO-000190 - Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AC-000020 + Windows Server 2019 must have the number of allowed bad logon attempts configured to three or less. + <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 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network server: Digitally sign communications (always)" to "Enabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93141 + SV-103229 + CCI-000044 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout threshold" to "3" or fewer invalid logon attempts (excluding "0", which is unacceptable). + + + + Verify the effective setting in Local Group Policy Editor. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ +Run "gpedit.msc". -Value Name: RequireSecuritySignature +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. -Value Type: REG_DWORD -Value: 0x00000001 (1) +If the "Account lockout threshold" is "0" or more than "3" attempts, this is a finding. + + - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000021-GPOS-00005 <GroupDescription></GroupDescription> - - WN19-SO-000200 - Windows Server 2019 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled. - <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. + + WN19-AC-000030 + Windows Server 2019 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater. + <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. -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103231 + V-93143 + CCI-000044 + CCI-002238 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Reset account lockout counter after" to at least "15" minutes. + + + + Verify the effective setting in Local Group Policy Editor. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ +Run "gpedit.msc". -Value Name: EnableSecuritySignature +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. -Value Type: REG_DWORD -Value: 0x00000001 (1) +If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding. + + - - SRG-OS-000433-GPOS-00192 + + SRG-OS-000057-GPOS-00027 <GroupDescription></GroupDescription> - - WN19-CC-000310 - Windows Server 2019 Explorer Data Execution Prevention must be enabled. - <VulnDiscussion>Data Execution Prevention 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></IAControls> + + WN19-UR-000170 + Windows Server 2019 Manage auditing and security log user right must only be assigned to the Administrators group. + <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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002824 - The default behavior is for data execution prevention to be turned on for File Explorer. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off Data Execution Prevention for Explorer" to "Not Configured" or "Disabled". - - - - The default behavior is for Data Execution Prevention to be turned on for File Explorer. + V-93197 + SV-103285 + CCI-000171 + CCI-000164 + CCI-000162 + CCI-000163 + CCI-001914 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Manage auditing and security log" to include only the following accounts or groups: -If the registry value name below does not exist, this is not a finding. +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. -If it exists and is configured with a value of "0", this is not a finding. +Run "gpedit.msc". -If it exists and is configured with a value of "1", this is a finding. +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ +If any accounts or groups other than the following are granted the "Manage auditing and security log" user right, this is a finding. -Value Name: NoDataExecutionPrevention +- Administrators -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) + - - SRG-OS-000433-GPOS-00193 + + SRG-OS-000069-GPOS-00037 <GroupDescription></GroupDescription> - - WN19-EP-000020 - Windows Server 2019 Exploit Protection system-level mitigation, Randomize memory allocations (Bottom-Up ASLR), must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AC-000080 + Windows Server 2019 must have the built-in Windows password complexity policy 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 three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. + +Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002824 - Ensure Exploit Protection system-level mitigation, "Randomize memory allocations (Bottom-Up ASLR)" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Randomize memory allocations (Bottom-Up ASLR)" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Bottom-Up ASLR on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <ASLR BottomUp="true" HighEntropy="true"></ASLR> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. - -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". - -Run "Windows PowerShell" with elevated privileges (run as administrator). + V-93459 + SV-103545 + CCI-000192 + CCI-000193 + CCI-000194 + CCI-001619 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Password must meet complexity requirements" to "Enabled". + + + + Verify the effective setting in Local Group Policy Editor. -Enter "Get-ProcessMitigation -System". +Run "gpedit.msc". -If the status of "ASLR: BottomUp" is "OFF", this is a finding. +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. -Values that would not be a finding include: +If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding. -ON -NOTSET (Default configuration) + - - SRG-OS-000191-GPOS-00080 + + SRG-OS-000073-GPOS-00041 <GroupDescription></GroupDescription> - - WN19-00-000290 - Windows Server 2019 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Host Based Security System (HBSS) is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). - <VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AC-000090 + Windows Server 2019 reversible password encryption must be disabled. + <VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001233 - Install a DoD approved HBSS software and ensure it is operating continuously. - - - - Verify DoD approved HBSS software is installed, configured, and properly operating. Ask the operator to document the HBSS software installation and configuration. + SV-103551 + V-93465 + CCI-000196 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Store passwords using reversible encryption" to "Disabled". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for "Store passwords using reversible encryption" is not set to "Disabled", this is a finding. -If the operator is not able to provide a documented configuration for an installed HBSS or if the HBSS software is not properly configured, maintained, or used, this is a finding. + - - SRG-OS-000480-GPOS-00231 + + SRG-OS-000075-GPOS-00043 <GroupDescription></GroupDescription> - - WN19-00-000280 - Windows Server 2019 must have a host-based firewall installed and enabled. - <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></IAControls> + + WN19-AC-000060 + Windows Server 2019 minimum password age must be configured to at least one day. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - CCI-002080 - Install and enable a host-based firewall on the system. - - - - Determine if a host-based firewall is installed and enabled on the system. + SV-103557 + V-93471 + CCI-000198 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password age" to at least "1" day. + + + + Verify the effective setting in Local Group Policy Editor. -If a host-based firewall is not installed and enabled on the system, this is a finding. +Run "gpedit.msc". -The configuration requirements will be determined by the applicable firewall STIG. +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for the "Minimum password age" is set to "0" days ("Password can be changed immediately"), this is a finding. + + - - WN19-CC-000451 + + SRG-OS-000076-GPOS-00044 <GroupDescription></GroupDescription> - - WN19-CC-000451 - The Windows Explorer Preview pane must be disabled for Windows Server 2019. - <VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. - -Organizations must disable the Windows Preview pane and Windows Detail pane.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AC-000050 + Windows Server 2019 maximum password age must be configured to 60 days or less. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following settings are configured for Windows Server 2019 locally or applied through group policy. - -Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn off Preview Pane" to "Enabled". + V-93477 + SV-103563 + CCI-000199 + Configure 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). + + + + Verify the effective setting in Local Group Policy Editor. -Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn on or off details pane" to "Enabled" and "Configure details pane" to "Always hide". - - - - - If the following registry values do not exist or are not configured as specified, this is a finding: +Run "gpedit.msc". -Registry Hive: HKEY_CURRENT_USER -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. -Value Name: NoPreviewPane +If the value for the "Maximum password age" is greater than "60" days, this is a finding. -Value Type: REG_DWORD +If the value is set to "0" (never expires), this is a finding. -Value: 1 + + + + + + SRG-OS-000077-GPOS-00045 + <GroupDescription></GroupDescription> + + WN19-AC-000040 + Windows Server 2019 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 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93479 + SV-103565 + CCI-000200 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Enforce password history" to "24" passwords remembered. + + + + Verify the effective setting in Local Group Policy Editor. -Registry Hive: HKEY_CURRENT_USER -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer +Run "gpedit.msc". -Value Name: NoReadingPane +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. -Value Type: REG_DWORD +If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding. -Value: 1 - - SRG-OS-000297-GPOS-00115 + + SRG-OS-000078-GPOS-00046 <GroupDescription></GroupDescription> - - WN19-DC-000410 - Windows Server 2019 Deny log on through Remote Desktop Services user right on domain controllers must be configured to prevent unauthenticated access. - <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. - -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> + + WN19-AC-000070 + Windows Server 2019 minimum password length must be configured to 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002314 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on through Remote Desktop Services" to include the following: - -- Guests Group - - - - This applies to domain controllers. A separate version applies to other systems. - -Verify the effective setting in Local Group Policy Editor. + V-93463 + SV-103549 + CCI-000205 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password length" to "14" characters. + + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. -- Guests Group +If the value for the "Minimum password length," is less than "14" characters, this is a finding. - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-DC-000340 Windows Server 2019 Access this computer from the network user right must only be assigned to the Administrators, Authenticated Users, and Enterprise Domain Controllers groups on domain controllers. @@ -13815,21 +14575,23 @@ Enterprise Domain Controllers groups on domain controllers. Accounts with the "Access this computer from the network" right may access resources on the system, and this right must be limited to those requiring it.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Access this computer from the network" to include only the following accounts or groups: + SV-103083 + V-92995 + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Access this computer from the network" to include only the following accounts or groups: - Administrators - Authenticated Users - Enterprise Domain Controllers - - - + + + This applies to domain controllers. It is NA for other systems. Verify the effective setting in Local Group Policy Editor. @@ -13848,29 +14610,31 @@ If any accounts or groups other than the following are granted the "Access this - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-DC-000360 Windows Server 2019 Allow log on through Remote Desktop Services user right must only be assigned to the Administrators group on domain controllers. <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on through Remote Desktop Services" to include only the following accounts or groups: + V-92997 + SV-103085 + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on through Remote Desktop Services" to include only the following accounts or groups: - Administrators - - - + + + This applies to domain controllers, it is NA for other systems. Verify the effective setting in Local Group Policy Editor. @@ -13886,10 +14650,10 @@ If any accounts or groups other than the following are granted the "Allow log on - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-DC-000370 Windows Server 2019 Deny access to this computer from the network user right on domain controllers must be configured to prevent unauthenticated access. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -13898,19 +14662,21 @@ The "Deny access to this computer from the network" user right defines the accou 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure 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: + SV-103087 + V-92999 + CCI-000213 + Configure 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: - Guests Group - - - + + + This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. @@ -13927,10 +14693,10 @@ If the following accounts or groups are not defined for the "Deny access to this - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-DC-000380 Windows Server 2019 Deny log on as a batch job user right on domain controllers must be configured to prevent unauthenticated access. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -13939,19 +14705,21 @@ The "Deny log on as a batch job" user right defines accounts that are prevented 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure 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: + SV-103089 + V-93001 + CCI-000213 + Configure 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: - Guests Group - - - + + + This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. @@ -13968,10 +14736,10 @@ If the following accounts or groups are not defined for the "Deny log on as a ba - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-DC-000390 Windows Server 2019 Deny log on as a service user right must be configured to include no accounts or groups (blank) on domain controllers. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -13980,17 +14748,19 @@ The "Deny log on as a service" user right defines accounts that are denied logon Incorrect configurations could prevent services from starting and result in a denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on as a service" to include no entries (blank). - - - + V-93003 + SV-103091 + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on as a service" to include no entries (blank). + + + This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. @@ -14005,10 +14775,10 @@ If any accounts or groups are defined for the "Deny log on as a service" user ri - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-DC-000400 Windows Server 2019 Deny log on locally user right on domain controllers must be configured to prevent unauthenticated access. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -14017,95 +14787,177 @@ The "Deny log on locally" user right defines accounts that are prevented from lo 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 2019 + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103093 + V-93005 + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on locally" to include the following: + +- Guests Group + + + + This applies to domain controllers. A separate version applies to other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: + +- Guests Group + + + + + + + SRG-OS-000080-GPOS-00048 + <GroupDescription></GroupDescription> + + WN19-UR-000030 + Windows Server 2019 Allow log on locally user right must only be assigned to the Administrators group. + <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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93017 + SV-103105 + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on locally" to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 + + + + + + + SRG-OS-000121-GPOS-00062 + <GroupDescription></GroupDescription> + + WN19-SO-000010 + Windows Server 2019 must have the built-in guest account disabled. + <VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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 MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on locally" to include the following: - -- Guests Group - - - - This applies to domain controllers. A separate version applies to other systems. - -Verify the effective setting in Local Group Policy Editor. + V-93497 + SV-103583 + CCI-000804 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Guest account status" to "Disabled". + + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. -- Guests Group +If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. - - SRG-OS-000080-GPOS-00048 + + SRG-OS-000297-GPOS-00115 <GroupDescription></GroupDescription> - - WN19-UR-000030 - Windows Server 2019 Allow log on locally user right must only be assigned to the Administrators group. + + WN19-DC-000410 + Windows Server 2019 Deny log on through Remote Desktop Services user right on domain controllers must be configured to prevent unauthenticated access. <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></IAControls> +The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. + +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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on locally" to include only the following accounts or groups: + SV-103051 + V-92963 + CCI-002314 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on through Remote Desktop Services" to include the following: -- Administrators - - - - Verify the effective setting in Local Group Policy Editor. +- Guests Group + + + + This applies to domain controllers. A separate version applies to other systems. + +Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: +If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: -- Administrators +- Guests Group - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-DC-000350 Windows Server 2019 Add workstations to domain user right must only be assigned to the Administrators group on domain controllers. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. Accounts with the "Add workstations to domain" right may add computers to a domain. This could result in unapproved or incorrectly configured systems being added to a 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Add workstations to domain" to include only the following accounts or groups: + V-93039 + SV-103127 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Add workstations to domain" to include only the following accounts or groups: - Administrators - - - + + + This applies to domain controllers. It is NA for other systems. Verify the effective setting in Local Group Policy Editor. @@ -14122,29 +14974,31 @@ If any accounts or groups other than the following are granted the "Add workstat - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-DC-000420 Windows Server 2019 Enable computer and user accounts to be trusted for delegation user right must only be assigned to the Administrators group on domain controllers. <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 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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 include only the following accounts or groups: + SV-103129 + V-93041 + CCI-002235 + Configure 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 include only the following accounts or groups: - Administrators - - - + + + This applies to domain controllers. A separate version applies to other systems. Verify the effective setting in Local Group Policy Editor. @@ -14161,27 +15015,29 @@ If any accounts or groups other than the following are granted the "Enable compu - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000010 Windows Server 2019 Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + V-93049 + SV-103137 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14194,27 +15050,29 @@ If any accounts or groups are granted the "Access Credential Manager as a truste - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000020 Windows Server 2019 Act as part of the operating system user right must not be assigned to any groups or accounts. <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 the 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + SV-103139 + V-93051 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14227,29 +15085,31 @@ If any accounts or groups (to include administrators), are granted the "Act as p - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000040 Windows Server 2019 Back up files and directories user right must only be assigned to the Administrators group. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Back up files and directories" to include only the following accounts or groups: + V-93053 + SV-103141 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Back up files and directories" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14264,29 +15124,31 @@ If any accounts or groups other than the following are granted the "Back up file - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000050 Windows Server 2019 Create a pagefile user right must only be assigned to the Administrators group. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create a pagefile" to include only the following accounts or groups: + SV-103143 + V-93055 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create a pagefile" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14301,27 +15163,29 @@ If any accounts or groups other than the following are granted the "Create a pag - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000060 Windows Server 2019 Create a token object user right must not be assigned to any groups or accounts. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + V-93057 + SV-103145 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14334,32 +15198,34 @@ If any accounts or groups are granted the "Create a token object" user right, th - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000070 Windows Server 2019 Create global objects user right must only be assigned to Administrators, Service, Local Service, and Network Service. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create global objects" to include only the following accounts or groups: + V-93059 + SV-103147 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create global objects" to include only the following accounts or groups: - Administrators - Service - Local Service - Network Service - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14377,27 +15243,29 @@ If any accounts or groups other than the following are granted the "Create globa - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000080 Windows Server 2019 Create permanent shared objects user right must not be assigned to any groups or accounts. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + SV-103149 + V-93061 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14410,31 +15278,33 @@ If any accounts or groups are granted the "Create permanent shared objects" user - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000090 Windows Server 2019 Create symbolic links user right must only be assigned to the Administrators group. <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 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create symbolic links" to include only the following accounts or groups: + SV-103151 + V-93063 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create symbolic links" to include only the following accounts or groups: - Administrators Systems that have the Hyper-V role will also have "Virtual Machines" given this user right. If this needs to be added manually, enter it as "NT Virtual Machine\Virtual Machines". - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14449,29 +15319,31 @@ If any accounts or groups other than the following are granted the "Create symbo - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000100 Windows Server 2019 Debug programs: user right must only be assigned to the Administrators group. <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Debug programs" to include only the following accounts or groups: + V-93065 + SV-103153 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Debug programs" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14486,29 +15358,31 @@ If any accounts or groups other than the following are granted the "Debug progra - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000110 Windows Server 2019 Force shutdown from a remote system user right must only be assigned to the Administrators group. <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 denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Force shutdown from a remote system" to include only the following accounts or groups: + V-93067 + SV-103155 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Force shutdown from a remote system" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14523,30 +15397,32 @@ If any accounts or groups other than the following are granted the "Force shutdo - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000120 Windows Server 2019 Generate security audits user right must only be assigned to Local Service and Network Service. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Generate security audits" to include only the following accounts or groups: + V-93069 + SV-103157 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Generate security audits" to include only the following accounts or groups: - Local Service - Network Service - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14562,32 +15438,34 @@ If any accounts or groups other than the following are granted the "Generate sec - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000130 Windows Server 2019 Impersonate a client after authentication user right must only be assigned to Administrators, Service, Local Service, and Network Service. <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 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Impersonate a client after authentication" to include only the following accounts or groups: + SV-103159 + V-93071 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Impersonate a client after authentication" to include only the following accounts or groups: - Administrators - Service - Local Service - Network Service - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14605,29 +15483,31 @@ If any accounts or groups other than the following are granted the "Impersonate - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000140 Windows Server 2019 Increase scheduling priority: user right must only be assigned to the Administrators group. <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 denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Increase scheduling priority" to include only the following accounts or groups: + SV-103161 + V-93073 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Increase scheduling priority" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14642,29 +15522,31 @@ If any accounts or groups other than the following are granted the "Increase sch - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000150 Windows Server 2019 Load and unload device drivers user right must only be assigned to the Administrators group. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Load and unload device drivers" user right allows a user to load device drivers dynamically on a system. This could be used by an attacker to install malicious code.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Load and unload device drivers" to include only the following accounts or groups: + SV-103163 + V-93075 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Load and unload device drivers" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14679,27 +15561,29 @@ If any accounts or groups other than the following are granted the "Load and unl - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000160 Windows Server 2019 Lock pages in memory user right must not be assigned to any groups or accounts. <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 denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + V-93077 + SV-103165 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14712,29 +15596,31 @@ If any accounts or groups are granted the "Lock pages in memory" user right, thi - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000180 Windows Server 2019 Modify firmware environment values user right must only be assigned to the Administrators group. <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 denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Modify firmware environment values" to include only the following accounts or groups: + V-93079 + SV-103167 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Modify firmware environment values" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14749,29 +15635,31 @@ If any accounts or groups other than the following are granted the "Modify firmw - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000190 Windows Server 2019 Perform volume maintenance tasks user right must only be assigned to the Administrators group. <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. This could be used to delete volumes, resulting in data loss or a denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Perform volume maintenance tasks" to include only the following accounts or groups: + V-93081 + SV-103169 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Perform volume maintenance tasks" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14786,29 +15674,31 @@ If any accounts or groups other than the following are granted the "Perform volu - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000200 Windows Server 2019 Profile single process user right must only be assigned to the Administrators group. <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 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Profile single process" to include only the following accounts or groups: + V-93083 + SV-103171 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Profile single process" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14823,29 +15713,31 @@ If any accounts or groups other than the following are granted the "Profile sing - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000210 Windows Server 2019 Restore files and directories user right must only be assigned to the Administrators group. <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 overwrite more current 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Restore files and directories" to include only the following accounts or groups: + V-93085 + SV-103173 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Restore files and directories" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14860,29 +15752,31 @@ If any accounts or groups other than the following are granted the "Restore file - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000220 Windows Server 2019 Take ownership of files or other objects user right must only be assigned to the Administrators group. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Take ownership of files or other objects" to include only the following accounts or groups: + V-93087 + SV-103175 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Take ownership of files or other objects" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14897,92 +15791,29 @@ If any accounts or groups other than the following are granted the "Take ownersh - - SRG-OS-000021-GPOS-00005 - <GroupDescription></GroupDescription> - - WN19-AC-000020 - Windows Server 2019 must have the number of allowed bad logon attempts configured to three or less. - <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 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000044 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout threshold" to "3" or fewer invalid logon attempts (excluding "0", which is unacceptable). - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. - -If the "Account lockout threshold" is "0" or more than "3" attempts, this is a finding. - - - - - - - SRG-OS-000021-GPOS-00005 - <GroupDescription></GroupDescription> - - WN19-AC-000030 - Windows Server 2019 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater. - <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. - -Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000044 - CCI-002238 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Reset account lockout counter after" to at least "15" minutes. - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. - -If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding. - - - - - - + SRG-OS-000329-GPOS-00128 <GroupDescription></GroupDescription> - + WN19-AC-000010 Windows Server 2019 account lockout duration must be configured to 15 minutes or greater. <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002238 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout duration" to "15" minutes or greater. + V-93145 + SV-103233 + CCI-002238 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout duration" to "15" minutes or greater. A value of "0" is also acceptable, requiring an administrator to unlock the account. - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -14995,68 +15826,27 @@ If the "Account lockout duration" is less than "15" minutes (excluding "0"), thi - - SRG-OS-000057-GPOS-00027 - <GroupDescription></GroupDescription> - - WN19-UR-000170 - Windows Server 2019 Manage auditing and security log user right must only be assigned to the Administrators group. - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000162 - CCI-000163 - CCI-000164 - CCI-000171 - CCI-001914 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Manage auditing and security log" to include only the following accounts or groups: - -- Administrators - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -- Administrators - - - - - - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - + WN19-00-000450 Windows Server 2019 must have orphaned security identifiers (SIDs) removed from user rights. <VulnDiscussion>Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be established for some reason.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Remove any unresolved SIDs found in User Rights assignments and determined to not be for currently valid accounts or groups by removing the accounts or groups from the appropriate group policy. - - - + V-93227 + SV-103315 + CCI-000366 + Remove any unresolved SIDs found in User Rights assignments and determined to not be for currently valid accounts or groups by removing the accounts or groups from the appropriate group policy. + + + Review the effective User Rights setting in Local Group Policy Editor. Run "gpedit.msc". @@ -15070,25 +15860,27 @@ If any unresolved SIDs exist and are not for currently valid accounts or groups, - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - + WN19-SO-000030 Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Rename administrator account" to a name other than "Administrator". - - - + V-93281 + SV-103369 + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Rename administrator account" to a name other than "Administrator". + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -15101,25 +15893,27 @@ If the value for "Accounts: Rename administrator account" is not set to a value - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - + WN19-SO-000040 Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Rename guest account" to a name other than "Guest". - - - + SV-103371 + V-93283 + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Rename guest account" to a name other than "Guest". + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -15128,230 +15922,6 @@ Navigate to Local Computer Policy >> Computer Configuration >> Windo If the value for "Accounts: Rename guest account" is not set to a value other than "Guest", this is a finding. - - - - - - SRG-OS-000069-GPOS-00037 - <GroupDescription></GroupDescription> - - WN19-AC-000080 - Windows Server 2019 must have the built-in Windows password complexity policy 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 three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. - -Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000192 - CCI-000193 - CCI-000194 - CCI-001619 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Password must meet complexity requirements" to "Enabled". - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding. - - - - - - - SRG-OS-000078-GPOS-00046 - <GroupDescription></GroupDescription> - - WN19-AC-000070 - Windows Server 2019 minimum password length must be configured to 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000205 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password length" to "14" characters. - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for the "Minimum password length," is less than "14" characters, this is a finding. - - - - - - - SRG-OS-000073-GPOS-00041 - <GroupDescription></GroupDescription> - - WN19-AC-000090 - Windows Server 2019 reversible password encryption must be disabled. - <VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000196 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Store passwords using reversible encryption" to "Disabled". - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for "Store passwords using reversible encryption" is not set to "Disabled", this is a finding. - - - - - - - SRG-OS-000075-GPOS-00043 - <GroupDescription></GroupDescription> - - WN19-AC-000060 - Windows Server 2019 minimum password age must be configured to at least one day. - <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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000198 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password age" to at least "1" day. - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for the "Minimum password age" is set to "0" days ("Password can be changed immediately"), this is a finding. - - - - - - - SRG-OS-000076-GPOS-00044 - <GroupDescription></GroupDescription> - - WN19-AC-000050 - Windows Server 2019 maximum password age must be configured to 60 days or less. - <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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000199 - Configure 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). - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - - - - - - - SRG-OS-000077-GPOS-00045 - <GroupDescription></GroupDescription> - - WN19-AC-000040 - Windows Server 2019 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 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000200 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Enforce password history" to "24" passwords remembered. - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding. - - - - - - - SRG-OS-000121-GPOS-00062 - <GroupDescription></GroupDescription> - - WN19-SO-000010 - Windows Server 2019 must have the built-in guest account disabled. - <VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000804 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Guest account status" to "Disabled". - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. - -If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. - diff --git a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V1R5_Manual-xccdf.log b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V1R5_Manual-xccdf.log deleted file mode 100644 index 8d467137d..000000000 --- a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V1R5_Manual-xccdf.log +++ /dev/null @@ -1,16 +0,0 @@ -V-92993::*::'' -V-93063::- Administrators::- Administrators`r`nSystems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines", SID S-1-5-83-0). This is not a finding. -V-93175::\SOFTWARE\ Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\::\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ -V-93217::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct AntiVirus service information'} -V-93257::0x00000000 (0) (Security), 0x00000001 (1) (Basic)::0 or 1 -V-93259::0x00000000 (0) - No peering (HTTP Only)::0, 1, 2, 99 or 100 -V-93261::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93263::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93267::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93311::0x00000002 (2) (or if the Value Name does not exist)::2 -V-93413::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93463::*::HardCodedRule(AccountPolicyRule)@{DscResource = 'AccountPolicy'; PolicyName = 'Minimum password length'; PolicyValue = $null; OrganizationValueTestString = "'{0}' -ge '14'"} -V-93523::0x00000002 (2) (Prompt for consent on the secure desktop)::1 or 2 -V-93563::0x00000000 (0) (or if the Value Name does not exist)::0 -V-93571::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct Firewall service information'} -V-93149::*::HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System'; ValueName = 'LegalNoticeCaption'; ValueType = 'String'; ValueData = $null; OrganizationValueTestString = "'{0}' -match '^(DoD Notice and Consent Banner|US Department of Defense Warning Statement)$'"} diff --git a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V2R2_Manual-xccdf.log b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V2R2_Manual-xccdf.log new file mode 100644 index 000000000..d9b329073 --- /dev/null +++ b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V2R2_Manual-xccdf.log @@ -0,0 +1,16 @@ +V-205664::*::'' +V-205756::- Administrators::- Administrators`r`nSystems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines", SID S-1-5-83-0). This is not a finding. +V-205639::\SOFTWARE\ Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\::\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ +V-205850::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct AntiVirus service information'} +V-205869::0x00000000 (0) (Security), 0x00000001 (1) (Basic)::0 or 1 +V-205870::0x00000000 (0) - No peering (HTTP Only)::0, 1, 2, 99 or 100 +V-205871::0x00000000 (0) (or if the Value Name does not exist)::0 +V-205872::0x00000000 (0) (or if the Value Name does not exist)::0 +V-205874::0x00000000 (0) (or if the Value Name does not exist)::0 +V-205924::0x00000002 (2) (or if the Value Name does not exist)::2 +V-205693::0x00000000 (0) (or if the Value Name does not exist)::0 +V-205662::*::HardCodedRule(AccountPolicyRule)@{DscResource = 'AccountPolicy'; PolicyName = 'Minimum password length'; PolicyValue = $null; OrganizationValueTestString = "'{0}' -ge '14'"} +V-205717::0x00000002 (2) (Prompt for consent on the secure desktop)::1 or 2 +V-205830::0x00000000 (0) (or if the Value Name does not exist)::0 +V-214936::*::HardCodedRule(ServiceRule)@{DscResource = 'Service'; Ensure = 'Present'; ServiceName = $null; ServiceState = 'Running'; StartupType = $null; OrganizationValueTestString = 'ServiceName/StartupType is populated with correct Firewall service information'} +V-205632::*::HardCodedRule(RegistryRule)@{DscResource = 'Registry'; Ensure = 'Present'; Key = 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System'; ValueName = 'LegalNoticeCaption'; ValueType = 'String'; ValueData = $null; OrganizationValueTestString = "'{0}' -match '^(DoD Notice and Consent Banner|US Department of Defense Warning Statement)$'"} diff --git a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V1R5_Manual-xccdf.xml b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V2R2_Manual-xccdf.xml similarity index 60% rename from source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V1R5_Manual-xccdf.xml rename to source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V2R2_Manual-xccdf.xml index 2c2a06478..2b48395cf 100644 --- a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V1R5_Manual-xccdf.xml +++ b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_MS_STIG_V2R2_Manual-xccdf.xml @@ -1,2848 +1,2880 @@  - - accepted - Windows Server 2019 Security Technical Implementation Guide + + accepted + Microsoft Windows Server 2019 Security Technical Implementation Guide This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil. + + + + DISA STIG.DOD.MIL - Release: 5 Benchmark Date: 17 Jun 2020 - 1 + Release: 2 Benchmark Date: 04 May 2021 + 3.2.2.36079 + 1.10.0 + 2 I - 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> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - SRG-OS-000028-GPOS-00009 + + SRG-OS-000002-GPOS-00002 <GroupDescription></GroupDescription> - - WN19-SO-000120 - Windows Server 2019 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver. - <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. + + WN19-00-000300 + Windows Server 2019 must automatically remove or disable temporary user accounts after 72 hours. + <VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. -Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. + +If temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. + +To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000056 - CCI-000057 - CCI-000060 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Interactive logon: Machine inactivity limit" to "900" seconds or less, excluding "0" which is effectively disabled. - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103063 + V-92975 + CCI-000016 + Configure temporary user accounts to automatically expire within 72 hours. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Domain accounts can be configured with an account expiration date, under "Account" properties. -Value Name: InactivityTimeoutSecs +Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. -Value Type: REG_DWORD -Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled) +Delete any temporary user accounts that are no longer necessary. + + + + Review temporary user accounts for expiration dates. + +Determine if temporary user accounts are used and identify any that exist. If none exist, this is NA. + +Domain Controllers: + +Open "PowerShell". + +Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". + +If "AccountExpirationDate" has not been defined within 72 hours for any temporary user account, this is a finding. + +Member servers and standalone systems: + +Open "Command Prompt". + +Run "Net user [username]", where [username] is the name of the temporary user account. + +If "Account expires" has not been defined within 72 hours for any temporary user account, this is a finding. - - SRG-OS-000032-GPOS-00013 + + SRG-OS-000004-GPOS-00004 <GroupDescription></GroupDescription> - - WN19-AU-000190 - Windows Server 2019 must be configured to audit logon successes. + + WN19-AU-000100 + Windows Server 2019 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. -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. +Security Group Management records events such as creating, deleting, or changing security groups, including changes in group members. -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000067 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Logon" with "Success" selected. - - - + SV-103067 + V-92979 + CCI-000018 + CCI-001403 + CCI-001405 + CCI-001404 + CCI-002130 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -2855,34 +2887,40 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Logon - Success +Account Management >> Security Group Management - Success - - SRG-OS-000032-GPOS-00013 + + SRG-OS-000004-GPOS-00004 <GroupDescription></GroupDescription> - - WN19-AU-000200 - Windows Server 2019 must be configured to audit logon failures. + + WN19-AU-000110 + Windows Server 2019 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. -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. +User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000067 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Logon" with "Failure" selected. - - - + SV-103069 + V-92981 + CCI-002130 + CCI-001405 + CCI-001404 + CCI-001403 + CCI-000018 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -2895,254 +2933,236 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Logon - Failure +Account Management >> User Account Management - Success - - SRG-OS-000033-GPOS-00014 + + SRG-OS-000004-GPOS-00004 <GroupDescription></GroupDescription> - - WN19-CC-000370 - Windows Server 2019 Remote Desktop Services must require secure Remote Procedure Call (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. + + WN19-AU-000120 + Windows Server 2019 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. -Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000068 - CCI-001453 - Configure 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: + SV-103071 + V-92983 + CCI-000172 + CCI-000018 + CCI-001403 + CCI-001404 + CCI-001405 + CCI-002130 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: fEncryptRPCTraffic +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Type: REG_DWORD -Value: 0x00000001 (1) +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 - Failure - - SRG-OS-000033-GPOS-00014 + + SRG-OS-000023-GPOS-00006 <GroupDescription></GroupDescription> - - WN19-CC-000380 - Windows Server 2019 Remote Desktop Services must be configured with the client connection encryption set to High 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. + + WN19-SO-000130 + Windows Server 2019 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. -Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000068 - CCI-001453 - Configure 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" with "High Level" 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 NT\Terminal Services\ + SV-103235 + V-93147 + CCI-000048 + CCI-000050 + CCI-001384 + CCI-001385 + CCI-001386 + CCI-001387 + CCI-001388 + Configure 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: -Value Name: MinEncryptionLevel +You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. -Type: REG_DWORD -Value: 0x00000003 (3) - - - - - SRG-OS-000002-GPOS-00002 - <GroupDescription></GroupDescription> - - WN19-00-000300 - Windows Server 2019 must automatically remove or disable temporary user accounts after 72 hours. - <VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. +By using this IS (which includes any device attached to this IS), you consent to the following conditions: -Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. +-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. -If temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. +-At any time, the USG may inspect and seize data stored on this IS. -To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000016 - Configure temporary user accounts to automatically expire within 72 hours. +-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. -Domain accounts can be configured with an account expiration date, under "Account" properties. +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. +-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. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Delete any temporary user accounts that are no longer necessary. - - - - Review temporary user accounts for expiration dates. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Determine if temporary user accounts are used and identify any that exist. If none exist, this is NA. +Value Name: LegalNoticeText -Domain Controllers: +Value Type: REG_SZ +Value: See message text below -Open "PowerShell". +You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. -Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". +By using this IS (which includes any device attached to this IS), you consent to the following conditions: -If "AccountExpirationDate" has not been defined within 72 hours for any temporary user account, this is a finding. +-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. -Member servers and standalone systems: +-At any time, the USG may inspect and seize data stored on this IS. -Open "Command Prompt". +-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. -Run "Net user [username]", where [username] is the name of the temporary user account. +-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -If "Account expires" has not been defined within 72 hours for any temporary user account, this is a finding. +-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. - - SRG-OS-000123-GPOS-00064 + + SRG-OS-000023-GPOS-00006 <GroupDescription></GroupDescription> - - WN19-00-000310 - Windows Server 2019 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours. - <VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. - -Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. + + WN19-SO-000140 + Windows Server 2019 title for legal banner dialog box must be configured with the appropriate text. + <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. -To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001682 - Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours. - -Domain accounts can be configured with an account expiration date, under "Account" properties. - -Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. - - - - Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. + SV-103237 + V-93149 + CCI-001388 + CCI-001386 + CCI-001387 + CCI-001384 + CCI-001385 + CCI-000048 + Configure 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 an organization-defined equivalent. -If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. - -If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. - -Domain Controllers: - -Open "PowerShell". +If an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN19-SO-000150. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. +Value Name: LegalNoticeCaption -Member servers and standalone systems: +Value Type: REG_SZ +Value: See message title options below -Open "Command Prompt". +"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. -Run "Net user [username]", where [username] is the name of the emergency account. +If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. -If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. +Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required. - - SRG-OS-000004-GPOS-00004 + + SRG-OS-000028-GPOS-00009 <GroupDescription></GroupDescription> - - WN19-AU-000100 - Windows Server 2019 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 security groups, including changes in group members. + + WN19-SO-000120 + Windows Server 2019 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver. + <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. -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000018 - CCI-000172 - CCI-001403 - CCI-001404 - CCI-001405 - CCI-002130 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + V-92961 + SV-103049 + CCI-000056 + CCI-000057 + CCI-000060 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Interactive logon: Machine inactivity limit" to "900" seconds or less, excluding "0" which is effectively disabled. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -If the system does not audit the following, this is a finding. +Value Name: InactivityTimeoutSecs -Account Management >> Security Group Management - Success +Value Type: REG_DWORD +Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled) - - SRG-OS-000004-GPOS-00004 + + SRG-OS-000032-GPOS-00013 <GroupDescription></GroupDescription> - - WN19-AU-000110 - Windows Server 2019 must be configured to audit Account Management - User Account Management successes. + + WN19-AU-000190 + Windows Server 2019 must be configured to audit 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. -User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. +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. -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000018 - CCI-000172 - CCI-001403 - CCI-001404 - CCI-001405 - CCI-002130 - Configure 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. - - - + V-92967 + SV-103055 + CCI-000067 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -3155,38 +3175,36 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Account Management >> User Account Management - Success +Logon/Logoff >> Logon - Success - - SRG-OS-000004-GPOS-00004 + + SRG-OS-000032-GPOS-00013 <GroupDescription></GroupDescription> - - WN19-AU-000120 - Windows Server 2019 must be configured to audit Account Management - User Account Management failures. + + WN19-AU-000200 + Windows Server 2019 must be configured to audit 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. -User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. +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. -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000018 - CCI-000172 - CCI-001403 - CCI-001404 - CCI-001405 - CCI-002130 - Configure 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. - - - + V-92969 + SV-103057 + CCI-000172 + CCI-000067 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -3199,8840 +3217,9552 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Account Management >> User Account Management - Failure +Logon/Logoff >> Logon - Failure - - SRG-OS-000240-GPOS-00090 + + SRG-OS-000033-GPOS-00014 <GroupDescription></GroupDescription> - - WN19-AU-000150 - Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. - -Account Lockout events can be used to identify potentially malicious logon attempts. + + WN19-CC-000370 + Windows Server 2019 Remote Desktop Services must require secure Remote Procedure Call (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. -Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-001404 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-92971 + SV-103059 + CCI-000068 + CCI-001453 + Configure 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: -Use the "AuditPol" tool to review the current Audit Policy configuration: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Value Name: fEncryptRPCTraffic -Enter "AuditPol /get /category:*" +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000033-GPOS-00014 + <GroupDescription></GroupDescription> + + WN19-CC-000380 + Windows Server 2019 Remote Desktop Services must be configured with the client connection encryption set to High 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. -Compare the "AuditPol" settings with the following: +Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-92973 + SV-103061 + CCI-001453 + CCI-000068 + Configure 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" with "High Level" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If the system does not audit the following, this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Logon/Logoff >> Account Lockout - Success +Value Name: MinEncryptionLevel + +Type: REG_DWORD +Value: 0x00000003 (3) - - SRG-OS-000240-GPOS-00090 + + SRG-OS-000042-GPOS-00020 <GroupDescription></GroupDescription> - - WN19-AU-000160 - Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout failures. + + WN19-CC-000090 + Windows Server 2019 command 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. -Account Lockout events can be used to identify potentially malicious logon attempts. - -Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-001404 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + V-93173 + SV-103261 + CCI-000135 + Configure 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: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ -If the system does not audit the following, this is a finding. +Value Name: ProcessCreationIncludeCmdLine_Enabled -Logon/Logoff >> Account Lockout - Failure +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000080-GPOS-00048 + + SRG-OS-000042-GPOS-00020 <GroupDescription></GroupDescription> - - WN19-00-000130 - Windows Server 2019 local volumes must use a format that supports NTFS attributes. - <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 a file system that supports NTFS attributes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000460 + Windows Server 2019 PowerShell script block logging 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. + +Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Format volumes to use NTFS or ReFS. - - - - Open "Computer Management". - -Select "Disk Management" under "Storage". + SV-103263 + V-93175 + CCI-000135 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> "Turn on PowerShell Script Block Logging" to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -For each local volume, if the file system does not indicate "NTFS", this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ -"ReFS" (resilient file system) is also acceptable and would not be a finding. +Value Name: EnableScriptBlockLogging -This does not apply to system partitions such the Recovery and EFI System Partition. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000080-GPOS-00048 + + SRG-OS-000057-GPOS-00027 <GroupDescription></GroupDescription> - - WN19-00-000180 - Windows Server 2019 non-administrative accounts or groups must only have print permissions on printer shares. - <VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000030 + Windows Server 2019 permissions 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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure the permissions on shared printers to restrict standard users to only have Print permissions. - - - - Open "Printers & scanners" in "Settings". - -If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) - -For each printer: - -Select the printer and "Manage". + V-93189 + SV-103277 + CCI-000162 + CCI-000163 + CCI-000164 + Configure the permissions on the Application event log file (Application.evtx) to prevent access by non-privileged accounts. The default permissions listed below satisfy this requirement: -Select "Printer Properties". +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control -Select the "Sharing" tab. +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. -If "Share this printer" is checked, select the "Security" tab. +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". + + + + Navigate to the Application event log file. -If any standard user accounts or groups have permissions other than "Print", this is a finding. +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. -The default is for the "Everyone" group to be given "Print" permission. +If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: -"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts. +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control - - SRG-OS-000312-GPOS-00122 + + SRG-OS-000057-GPOS-00027 <GroupDescription></GroupDescription> - - WN19-00-000140 - Windows Server 2019 permissions for the system drive root directory (usually C:\) 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. - -The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + + WN19-AU-000040 + Windows Server 2019 permissions 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. -Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002165 - Maintain the default permissions for the system drive's root directory and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). - -Default Permissions -C:\ -Type - "Allow" for all -Inherited from - "None" for all + V-93191 + SV-103279 + CCI-000164 + CCI-000163 + CCI-000162 + Configure the permissions on the Security event log file (Security.evtx) to prevent access by non-privileged accounts. The default permissions listed below satisfy this requirement: -Principal - Access - Applies to +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control -SYSTEM - Full control - This folder, subfolders, and files -Administrators - Full control - This folder, subfolders, and files -Users - Read & execute - This folder, subfolders, and files -Users - Create folders/append data - This folder and subfolders -Users - Create files/write data - Subfolders only -CREATOR OWNER - Full Control - Subfolders and files only - - - - The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. -Review the permissions for the system drive's root directory (usually C:\). 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. +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". + + + + Navigate to the Security event log file. -If permissions are not as restrictive as the default permissions listed below, this is a finding. +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. -Viewing in File Explorer: +If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: -View the Properties of the system drive's root directory. +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + SRG-OS-000057-GPOS-00027 + <GroupDescription></GroupDescription> + + WN19-AU-000050 + Windows Server 2019 permissions 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. -Select the "Security" tab, and the "Advanced" button. +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93193 + SV-103281 + CCI-000162 + CCI-000164 + CCI-000163 + Configure the permissions on the System event log file (System.evtx) to prevent access by non-privileged accounts. The default permissions listed below satisfy this requirement: -Default permissions: -C:\ -Type - "Allow" for all -Inherited from - "None" for all +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control -Principal - Access - Applies to +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. -SYSTEM - Full control - This folder, subfolders, and files -Administrators - Full control - This folder, subfolders, and files -Users - Read & execute - This folder, subfolders, and files -Users - Create folders/append data - This folder and subfolders -Users - Create files/write data - Subfolders only -CREATOR OWNER - Full Control - Subfolders and files only +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". + + + + Navigate to the System event log file. -Alternately, use icacls: +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. -Open "Command Prompt (Admin)". +If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: -Enter "icacls" followed by the directory: +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + SRG-OS-000062-GPOS-00031 + <GroupDescription></GroupDescription> + + WN19-SO-000050 + Windows Server 2019 must force audit policy subcategory settings to override audit policy category settings. + <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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93151 + SV-103239 + CCI-000169 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -"icacls c:\" +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -The following results should be displayed: +Value Name: SCENoApplyLegacyAuditPolicy -c:\ -NT AUTHORITY\SYSTEM:(OI)(CI)(F) -BUILTIN\Administrators:(OI)(CI)(F) -BUILTIN\Users:(OI)(CI)(RX) -BUILTIN\Users:(CI)(AD) -BUILTIN\Users:(CI)(IO)(WD) -CREATOR OWNER:(OI)(CI)(IO)(F) -Successfully processed 1 files; Failed processing 0 files +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000312-GPOS-00122 + + SRG-OS-000066-GPOS-00034 <GroupDescription></GroupDescription> - - WN19-00-000150 - Windows Server 2019 permissions for program file 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. - -The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + + WN19-PK-000010 + Windows Server 2019 must have the DoD Root Certificate Authority (CA) certificates 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 CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. -Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002165 - Maintain the default permissions for the program file directories and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). + SV-103573 + V-93487 + CCI-000185 + CCI-002470 + Install the DoD Root CA certificates: -Default permissions: -\Program Files and \Program Files (x86) -Type - "Allow" for all -Inherited from - "None" for all +DoD Root CA 2 +DoD Root CA 3 +DoD Root CA 4 +DoD Root CA 5 -Principal - Access - Applies to +The InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. + + + + The certificates and thumbprints referenced below apply to unclassified systems; see PKE documentation for other networks. -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files - - - - The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). +Open "Windows PowerShell" as an administrator. -Review the permissions for the program file directories (Program Files and Program Files [x86]). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. +Execute the following command: -If permissions are not as restrictive as the default permissions listed below, this is a finding. +Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint, NotAfter -Viewing in File Explorer: +If the following certificate "Subject" and "Thumbprint" information is not displayed, this is a finding. -For each folder, view the Properties. +Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 +NotAfter: 12/5/2029 -Select the "Security" tab, and the "Advanced" button. +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB +NotAfter: 12/30/2029 -Default permissions: -\Program Files and \Program Files (x86) -Type - "Allow" for all -Inherited from - "None" for all +Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 +NotAfter: 7/25/2032 -Principal - Access - Applies to +Subject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B +NotAfter: 6/14/2041 -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files +Alternately, use the Certificates MMC snap-in: -Alternately, use icacls: +Run "MMC". -Open a Command prompt (admin). +Select "File", "Add/Remove Snap-in". -Enter "icacls" followed by the directory: +Select "Certificates" and click "Add". -'icacls "c:\program files"' -'icacls "c:\program files (x86)"' +Select "Computer account" and click "Next". -The following results should be displayed for each when entered: +Select "Local computer: (the computer this console is running on)" and click "Finish". -c:\program files (c:\program files (x86)) -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) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) -Successfully processed 1 files; Failed processing 0 files +Click "OK". + +Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates". + +For each of the DoD Root CA certificates noted below: + +Right-click on the certificate and select "Open". + +Select the "Details" Tab. + +Scroll to the bottom and select "Thumbprint". + +If the DoD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. + +DoD Root CA 2 +Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 +Valid to: Wednesday, December 5, 2029 + +DoD Root CA 3 +Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB +Valid to: Sunday, December 30, 2029 + +DoD Root CA 4 +Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 +Valid to: Sunday, July 25, 2032 + +DoD Root CA 5 +Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B +Valid to: Friday, June 14, 2041 - - SRG-OS-000312-GPOS-00122 + + SRG-OS-000066-GPOS-00034 <GroupDescription></GroupDescription> - - WN19-00-000160 - Windows Server 2019 permissions for the Windows installation directory 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. - -The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + + WN19-PK-000020 + Windows Server 2019 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates 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. -Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002165 - Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). + V-93489 + SV-103575 + CCI-000185 + CCI-002470 + Install the DoD Interoperability Root CA cross-certificates on unclassified systems. -Default permissions: -Type - "Allow" for all -Inherited from - "None" for all +Issued To - Issued By - Thumbprint -Principal - Access - Applies to +DoD Root CA 2 - DoD Interoperability Root CA 1 - A8C27332CCB4CA49554CE55D34062A7DD2850C02 -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files - - - - The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). +DoD Root CA 3 - DoD Interoperability Root CA 2 - AC06108CA348CC03B53795C64BF84403C1DBD341 -Review the permissions for the Windows installation directory (usually C:\Windows). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. +Administrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. -If permissions are not as restrictive as the default permissions listed below, this is a finding: +The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. + + + + This is applicable to unclassified systems. It is NA for others. -Viewing in File Explorer: +Open "PowerShell" as an administrator. -For each folder, view the Properties. +Execute the following command: -Select the "Security" tab and the "Advanced" button. +Get-ChildItem -Path Cert:Localmachine\disallowed | Where {$_.Issuer -Like "*DoD Interoperability*" -and $_.Subject -Like "*DoD*"} | FL Subject, Issuer, Thumbprint, NotAfter -Default permissions: -\Windows -Type - "Allow" for all -Inherited from - "None" for all +If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. -Principal - Access - Applies to +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: AC06108CA348CC03B53795C64BF84403C1DBD341 +NotAfter: 1/22/2022 10:22:56 AM -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files +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: A8C27332CCB4CA49554CE55D34062A7DD2850C02 +NotAfter: 8/26/2022 9:25:51 AM -Alternately, use icacls: +Alternately, use the Certificates MMC snap-in: -Open a Command prompt (admin). +Run "MMC". -Enter "icacls" followed by the directory: +Select "File", "Add/Remove Snap-in". -"icacls c:\windows" +Select "Certificates" and click "Add". -The following results should be displayed for each when entered: +Select "Computer account" and click "Next". -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) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) -Successfully processed 1 files; Failed processing 0 files +Select "Local computer: (the computer this console is running on)" and 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: DoD Root CA 2 +Issued By: DoD Interoperability Root CA 1 +Thumbprint: A8C27332CCB4CA49554CE55D34062A7DD2850C02 +Valid to: Friday, August 26, 2022 + +Issued To: DoD Root CA 3 +Issued By: DoD Interoperability Root CA 2 +Thumbprint: AC06108CA348CC03B53795C64BF84403C1DBD341 +Valid to: Saturday, January 22, 2022 - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000066-GPOS-00034 <GroupDescription></GroupDescription> - - WN19-00-000170 - Windows Server 2019 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained. - <VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-PK-000030 + Windows Server 2019 must have the US DoD CCEB Interoperability Root CA cross-certificates 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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. + +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive. + V-93491 + SV-103577 + CCI-000185 + CCI-002470 + Install the US DoD CCEB Interoperability Root CA cross-certificate on unclassified systems. -The default permissions of the higher-level keys are noted below. +Issued To - Issued By - Thumbprint -HKEY_LOCAL_MACHINE\SECURITY +DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -SYSTEM - Full Control - This key and subkeys -Administrators - Special - This key and subkeys +DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - 929BF3196896994C0A201DF4A5B71F603FEFBF2E -HKEY_LOCAL_MACHINE\SOFTWARE +Administrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - This key and subkeys -ALL APPLICATION PACKAGES - Read - This key and subkeys +The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. + + + + This is applicable to unclassified systems. It is NA for others. -HKEY_LOCAL_MACHINE\SYSTEM +Open "PowerShell" as an administrator. -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - Subkeys only -ALL APPLICATION PACKAGES - Read - This key and subkeys +Execute the following command: -Microsoft has also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID. -S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 - - - - Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. +Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter -If any non-privileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. +If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. -If permissions are not as restrictive as the default permissions listed below, this is a finding: +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 +NotAfter: 8/26/2022 9:07:50 AM -Run "Regedit". +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E +NotAfter: 9/27/2019 -Right-click on the registry areas noted below. +Alternately, use the Certificates MMC snap-in: -Select "Permissions" and the "Advanced" button. +Run "MMC". -HKEY_LOCAL_MACHINE\SECURITY +Select "File", "Add/Remove Snap-in". -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -SYSTEM - Full Control - This key and subkeys -Administrators - Special - This key and subkeys +Select "Certificates" and click "Add". -HKEY_LOCAL_MACHINE\SOFTWARE +Select "Computer account" and click "Next". -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - This key and subkeys -ALL APPLICATION PACKAGES - Read - This key and subkeys +Select "Local computer: (the computer this console is running on)" and click "Finish". -HKEY_LOCAL_MACHINE\SYSTEM +Click "OK". -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - Subkeys only -ALL APPLICATION PACKAGES - Read - This key and subkeys +Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates". -Other examples under the noted keys may also be sampled. There may be some instances where non-privileged groups have greater than Read permission. +For each certificate with "US DoD CCEB Interoperability Root CA ..." under "Issued By": -Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID, this is currently not a finding. -S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 +Right-click on the certificate and select "Open". -If the defaults have not been changed, these are not a finding. +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: DoD Root CA 3 +Issued By: US DoD CCEB Interoperability Root CA 2 +Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 +Valid to: Friday, August 26, 2022 + +Issued To: DoD Root CA 3 +Issued By: US DoD CCEB Interoperability Root CA 2 +Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E +Valid: Friday, September 27, 2019 - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000067-GPOS-00035 <GroupDescription></GroupDescription> - - WN19-MS-000010 - Windows Server 2019 must only allow administrators responsible for the member server or standalone system to 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. + + WN19-SO-000350 + Windows Server 2019 users must be required to enter a password to access private keys stored on the computer. + <VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. -System administrators must log on to systems using only accounts with the minimum level of authority necessary. +The cornerstone of the PKI is the private key used to encrypt or digitally sign information. -For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group (see V-36433 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. +If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. -Standard user accounts must not be members of the built-in Administrators group.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the local "Administrators" group to include only administrator groups or accounts responsible for administration of the system. - -For domain-joined member servers, replace the Domain Admins group with a domain member server administrator group. - -Remove any standard user accounts. - - - - This applies to member servers and standalone systems. A separate version applies to domain controllers. - -Open "Computer Management". - -Navigate to "Groups" under "Local Users and Groups". - -Review the local "Administrators" group. - -Only administrator groups or accounts responsible for administration of the system may be members of the group. - -For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group. + V-93493 + SV-103579 + CCI-000186 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "System cryptography: Force strong key protection for user keys stored on the computer" to "User must enter a password each time they use a key". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Standard user accounts must not be members of the local Administrator group. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Cryptography\ -If accounts that do not have responsibility for administration of the system are members of the local Administrators group, this is a finding. +Value Name: ForceKeyProtection -If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding. +Type: REG_DWORD +Value: 0x00000002 (2) - - SRG-OS-000324-GPOS-00125 + + SRG-OS-000073-GPOS-00041 <GroupDescription></GroupDescription> - - WN19-MS-000060 - Windows Server 2019 must restrict remote calls to the Security Account Manager (SAM) to Administrators on domain-joined member servers and standalone systems. - <VulnDiscussion>The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000300 + Windows Server 2019 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 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Navigate to the policy Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Restrict clients allowed to make remote calls to SAM". -Select "Edit Security" to configure the "Security descriptor:". - -Add "Administrators" in "Group or user names:" if it is not already listed (this is the default). - -Select "Administrators" in "Group or user names:". - -Select "Allow" for "Remote Access" in "Permissions for "Administrators". - -Click "OK". - -The "Security descriptor:" must be populated with "O:BAG:BAD:(A;;RC;;;BA) for the policy to be enforced. - - - - This applies to member servers and standalone systems; it is NA for domain controllers. - -If the following registry value does not exist or is not configured as specified, this is a finding: + V-93467 + SV-103553 + CCI-000196 + Configure 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". + + + + 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\Lsa\ -Value Name: RestrictRemoteSAM +Value Name: NoLMHash -Value Type: REG_SZ -Value: O:BAG:BAD:(A;;RC;;;BA) +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000074-GPOS-00042 <GroupDescription></GroupDescription> - - WN19-AU-000090 - Windows Server 2019 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 Events records events such as the access of a password hash or the Password Policy Checking API being called. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000180 + Windows Server 2019 unencrypted passwords must not be sent to third-party Server Message Block (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 determine 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + V-93469 + SV-103555 + CCI-000197 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -If the system does not audit the following, this is a finding: +Value Name: EnablePlainTextPassword -Account Management >> Other Account Management Events - Success +Value Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000076-GPOS-00044 <GroupDescription></GroupDescription> - - WN19-AU-000140 - Windows Server 2019 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. + + WN19-00-000020 + Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days. + <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93473 + SV-103559 + CCI-000199 + Change the built-in Administrator account password at least every "60" days. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this. + + + + Review the password last set date for the built-in Administrator account. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Domain controllers: -Enter "AuditPol /get /category:*" +Open "PowerShell". -Compare the "AuditPol" settings with the following: +Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". -If the system does not audit the following, this is a finding. +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. -Detailed Tracking >> Process Creation - Success +Member servers and standalone systems: + +Open "Command Prompt". + +Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. + +(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) + +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000076-GPOS-00044 <GroupDescription></GroupDescription> - - WN19-AU-000260 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000210 + Windows Server 2019 passwords must be configured to expire. + <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93475 + SV-103561 + CCI-000199 + Configure all enabled user account passwords to expire. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Uncheck "Password never expires" for all enabled user accounts in Active Directory Users and Computers for domain accounts and Users in Computer Management for member servers and standalone systems. Document any exceptions with the ISSO. + + + + Review the password never expires status for enabled user accounts. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Open "PowerShell". -Enter "AuditPol /get /category:*" +Domain Controllers: -Compare the "AuditPol" settings with the following: +Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". -If the system does not audit the following, this is a finding. +Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. -Policy Change >> Audit Policy Change - Success +If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. + +Member servers and standalone systems: + +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. + +Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). + +If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000078-GPOS-00046 <GroupDescription></GroupDescription> - - WN19-AU-000270 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000050 + Windows Server 2019 manually managed application 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" - -Compare the "AuditPol" settings with the following: + SV-103547 + V-93461 + CCI-000205 + Establish a policy that requires application/service account passwords that are manually managed to be at least 15 characters in length. Ensure the policy is enforced. + + + + Determine if manually managed application/service accounts exist. If none exist, this is NA. -If the system does not audit the following, this is a finding. +Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. -Policy Change >> Audit Policy Change - Failure +If such a policy does not exist or has not been implemented, this is a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - - WN19-AU-000280 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000130 + Windows Server 2019 local volumes must use a format that supports NTFS attributes. + <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 a file system that supports NTFS attributes.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-92991 + SV-103079 + CCI-000213 + Format volumes to use NTFS or ReFS. + + + + Open "Computer Management". -Use the "AuditPol" tool to review the current Audit Policy configuration: +Select "Disk Management" under "Storage". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +For each local volume, if the file system does not indicate "NTFS", this is a finding. -Enter "AuditPol /get /category:*" - -Compare the "AuditPol" settings with the following: - -If the system does not audit the following, this is a finding. +"ReFS" (resilient file system) is also acceptable and would not be a finding. -Policy Change >> Authentication Policy Change - Success +This does not apply to system partitions such the Recovery and EFI System Partition. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - - WN19-AU-000290 - Windows Server 2019 must be configured to audit Policy Change - Authorization 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. - -Authorization Policy Change records events related to changes in user rights, such as "Create a token object". - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000180 + Windows Server 2019 non-administrative accounts or groups must only have print permissions on printer shares. + <VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> "Audit Authorization 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103081 + V-92993 + CCI-000213 + Configure the permissions on shared printers to restrict standard users to only have Print permissions. + + + + Open "Printers & scanners" in "Settings". -Use the "AuditPol" tool to review the current Audit Policy configuration: +If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +For each printer: -Enter "AuditPol /get /category:*" +Select the printer and "Manage". -Compare the "AuditPol" settings with the following: +Select "Printer Properties". -If the system does not audit the following, this is a finding. +Select the "Sharing" tab. -Policy Change >> Authorization Policy Change - Success +If "Share this printer" is checked, select the "Security" tab. + +If any standard user accounts or groups have permissions other than "Print", this is a finding. + +The default is for the "Everyone" group to be given "Print" permission. + +"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000300 - Windows Server 2019 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". - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000270 + Windows Server 2019 must have the roles and features required by the system documented. + <VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + SV-103467 + V-93381 + CCI-000381 + Document the roles and features required for the system to operate. Uninstall any that are not required. + + + + Required roles and features will vary based on the function of the individual system. -Compare the "AuditPol" settings with the following: +Roles and features specifically required to be disabled per the STIG are identified in separate requirements. -If the system does not audit the following, this is a finding. +If the organization has not documented the roles and features required for the system(s), this is a finding. -Privilege Use >> Sensitive Privilege Use - Success +The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State". - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000310 - Windows Server 2019 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". - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000320 + Windows Server 2019 must not have the Fax Server role installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93383 + SV-103469 + CCI-000381 + Uninstall the "Fax Server" role. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the role. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -Privilege Use >> Sensitive Privilege Use - Failure +Deselect "Fax Server" on the "Roles" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Fax". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000320 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000340 + Windows Server 2019 must not have the Peer Name Resolution Protocol installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103471 + V-93385 + CCI-000381 + Uninstall the "Peer Name Resolution Protocol" feature. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the feature. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -System >> IPsec Driver - Success +Deselect "Peer Name Resolution Protocol" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq PNRP". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000330 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000350 + Windows Server 2019 must not have Simple TCP/IP Services installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93387 + SV-103473 + CCI-000381 + Uninstall the "Simple TCP/IP Services" feature. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the feature. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -System >> IPsec Driver - Failure +Deselect "Simple TCP/IP Services" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Simple-TCPIP". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000340 - Windows Server 2019 must be configured to audit System - Other System 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. - -Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000370 + Windows Server 2019 must not have the TFTP Client installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103475 + V-93389 + CCI-000381 + Uninstall the "TFTP Client" feature. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the feature. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -System >> Other System Events - Success +Deselect "TFTP Client" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq TFTP-Client". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000350 - Windows Server 2019 must be configured to audit System - Other System 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. - -Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000380 + Windows Server 2019 must not the Server Message Block (SMB) v1 protocol installed. + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93391 + SV-103477 + CCI-000381 + Uninstall the SMBv1 protocol. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Open "Windows PowerShell" with elevated privileges (run as administrator). -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Enter "Uninstall-WindowsFeature -Name FS-SMB1 -Restart". +(Omit the Restart parameter if an immediate restart of the system cannot be done.) -Enter "AuditPol /get /category:*" +Alternately: -Compare the "AuditPol" settings with the following: +Start "Server Manager". -If the system does not audit the following, this is a finding. +Select the server with the feature. -System >> Other System Events - Failure - - - - - SRG-OS-000327-GPOS-00127 - <GroupDescription></GroupDescription> - - WN19-AU-000360 - Windows Server 2019 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. +Scroll down to "ROLES AND FEATURES" in the right pane. -Security State Change records events related to changes in the security state, such as startup and shutdown of the system. +Select "Remove Roles and Features" from the drop-down "TASKS" list. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. +Select the appropriate server on the "Server Selection" page and click "Next". -Use the "AuditPol" tool to review the current Audit Policy configuration: +Deselect "SMB 1.0/CIFS File Sharing Support" on the "Features" page. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Click "Next" and "Remove" as prompted. + + + + Different methods are available to disable SMBv1 on Windows Server 2019. This is the preferred method, however if WN19-00-000390 and WN19-00-000400 are configured, this is NA. -Enter "AuditPol /get /category:*" +Open "Windows PowerShell" with elevated privileges (run as administrator). -Compare the "AuditPol" settings with the following: +Enter "Get-WindowsFeature -Name FS-SMB1". -If the system does not audit the following, this is a finding. +If "Installed State" is "Installed", this is a finding. -System >> Security State Change - Success +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000370 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000390 + Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server. + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + SV-103479 + V-93393 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 Server" to "Disabled". -Use the "AuditPol" tool to review the current Audit Policy configuration: +The system must be restarted for the change to take effect. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +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. + + + + Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. -Enter "AuditPol /get /category:*" +If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ -If the system does not audit the following, this is a finding. +Value Name: SMB1 -System >> Security System Extension - Success +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000380 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000400 + Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client. + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93395 + SV-103481 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 client driver" to "Enabled" with "Disable driver (recommended)" selected for "Configure MrxSmb10 driver". -Use the "AuditPol" tool to review the current Audit Policy configuration: +The system must be restarted for the changes to take effect. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +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. + + + + Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. -Enter "AuditPol /get /category:*" +If the following registry value is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ -If the system does not audit the following, this is a finding. +Value Name: Start -System >> System Integrity - Success +Type: REG_DWORD +Value: 0x00000004 (4) - - SRG-OS-000327-GPOS-00127 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000390 - Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000410 + Windows Server 2019 must not have Windows PowerShell 2.0 installed. + <VulnDiscussion>Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-002234 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93397 + SV-103483 + CCI-000381 + Uninstall the "Windows PowerShell 2.0 Engine". -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the feature. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -System >> System Integrity - Failure +Deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell" on the "Features" page. + +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq PowerShell-v2". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000023-GPOS-00006 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-SO-000130 - Windows Server 2019 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. - -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000010 + Windows Server 2019 must prevent the display of slide shows on the lock screen. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000048 - CCI-000050 - CCI-001384 - CCI-001385 - CCI-001386 - CCI-001387 - CCI-001388 - Configure 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. + V-93399 + SV-103485 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> Control Panel >> Personalization >> "Prevent enabling lock screen slide show" to "Enabled". + + + + Verify the registry value below. --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. - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +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: LegalNoticeText - -Value Type: REG_SZ -Value: See message text below - -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. +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\ --This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. +Value Name: NoLockScreenSlideshow --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. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000023-GPOS-00006 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-SO-000140 - Windows Server 2019 title for legal banner dialog box must be configured with the appropriate text. - <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. - -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000020 + Windows Server 2019 must have WDigest Authentication 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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000048 - CCI-001384 - CCI-001385 - CCI-001386 - CCI-001387 - CCI-001388 - Configure 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 an organization-defined equivalent. + SV-103487 + V-93401 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "WDigest Authentication (disabling may require KB2871997)" to "Disabled". -If an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN19-SO-000150. - - - +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: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ - -Value Name: LegalNoticeCaption - -Value Type: REG_SZ -Value: See message title options below - -"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\ -If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. +Value Name: UseLogonCredential -Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required. +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000062-GPOS-00031 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-SO-000050 - Windows Server 2019 must force audit policy subcategory settings to override audit policy category settings. - <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></IAControls> + + WN19-CC-000150 + Windows Server 2019 downloading print driver packages over HTTP 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 will prevent 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000169 - Configure 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". - - - + SV-103489 + V-93403 + CCI-000381 + Configure 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 -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ -Value Name: SCENoApplyLegacyAuditPolicy +Value Name: DisableWebPnPDownload -Value Type: REG_DWORD +Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000070 - Windows Server 2019 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. + + WN19-CC-000160 + Windows Server 2019 printing over HTTP 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 will prevent uncontrolled updates to the system. -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></IAControls> +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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + SV-103491 + V-93405 + CCI-000381 + Configure 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: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ -If the system does not audit the following, this is a finding. +Value Name: DisableHTTPPrinting -Account Logon >> Credential Validation - Success +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000080 - Windows Server 2019 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></IAControls> + + WN19-CC-000170 + Windows Server 2019 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 in to 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + SV-103493 + V-93407 + CCI-000381 + Configure 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. -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ -If the system does not audit the following, this is a finding. +Value Name: DontDisplayNetworkSelectionUI -Account Logon >> Credential Validation - Failure +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000474-GPOS-00219 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000130 - Windows Server 2019 must be configured to audit Detailed Tracking - Plug and Play 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. + + WN19-CC-000200 + Windows Server 2019 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 will prevent uncontrolled updates to the system. -Plug and Play activity records events related to the successful connection of external devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> "Audit PNP Activity" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: + V-93409 + SV-103495 + CCI-000381 + Configure 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: -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\ -Enter "AuditPol /get /category:*" +Value Name: DisableInventory -Compare the "AuditPol" settings with the following: - -If the system does not audit the following, this is a finding. - -Detailed Tracking >> Plug and Play Events - Success +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000170 - Windows Server 2019 must be configured to audit Logon/Logoff - Group Membership 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 Group Membership records information related to the group membership of a user's logon token.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000300 + Windows Server 2019 Windows Defender SmartScreen must be enabled. + <VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Group Membership" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: + V-93411 + SV-103497 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Configure Windows Defender SmartScreen" to "Enabled" with either option "Warn" or "Warn and prevent bypass" selected. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Windows 2019 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer. + + + + This is applicable to unclassified systems; for other systems, this is NA. -Enter "AuditPol /get /category:*" +If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ -If the system does not audit the following, this is a finding. +Value Name: EnableSmartScreen -Logon/Logoff >> Group Membership - Success +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000210 - Windows Server 2019 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 that have administrative privileges and can be used to elevate processes. - -Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000400 + Windows Server 2019 must disable Basic authentication for RSS feeds over HTTP. + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93413 + SV-103499 + CCI-000381 + The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. -Use the "AuditPol" tool to review the current Audit Policy configuration: +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> "Turn on Basic feed authentication over HTTP" to "Not Configured" or "Disabled". + + + + The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +If the registry value name below does not exist, this is not a finding. -Enter "AuditPol /get /category:*" +If it exists and is configured with a value of "0", this is not a finding. -Compare the "AuditPol" settings with the following: +If it exists and is configured with a value of "1", this is a finding. -If the system does not audit the following, this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ -Logon/Logoff >> Special Logon - Success +Value Name: AllowBasicAuthInClear + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000220 - Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. - -Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000410 + Windows Server 2019 must prevent Indexing of encrypted files. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" + V-93415 + SV-103501 + CCI-000381 + Configure 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: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\ -If the system does not audit the following, this is a finding. +Value Name: AllowIndexingEncryptedStoresOrItems -Object Access >> Other Object Access Events - Success +Value Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000470-GPOS-00214 + + SRG-OS-000095-GPOS-00049 <GroupDescription></GroupDescription> - - WN19-AU-000230 - Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. - -Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-MS-000030 + Windows Server 2019 local users on domain-joined member servers 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). + SV-103505 + V-93419 + CCI-000381 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> "Enumerate local users on domain-joined computers" to "Disabled". + + + + This applies to member servers. For domain controllers and standalone systems, this is NA. -Enter "AuditPol /get /category:*" +If the following registry value does not exist or is not configured as specified, this is a finding: -Compare the "AuditPol" settings with the following: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ -If the system does not audit the following, this is a finding. +Value Name: EnumerateLocalUsers -Object Access >> Other Object Access Events - Failure +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000474-GPOS-00219 + + SRG-OS-000096-GPOS-00050 <GroupDescription></GroupDescription> - - WN19-AU-000240 - Windows Server 2019 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. - -Removable Storage auditing under Object Access 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></IAControls> + + WN19-00-000330 + Windows Server 2019 must not have the Microsoft FTP service installed unless required by the organization. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: + SV-103507 + V-93421 + CCI-000382 + Uninstall the "FTP Server" role. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). - -Enter "AuditPol /get /category:*" - -Compare the "AuditPol" settings with the following: +Start "Server Manager". -If the system does not audit the following, this is a finding. +Select the server with the role. -Object Access >> Removable Storage - Success +Scroll down to "ROLES AND FEATURES" in the right pane. -Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. - - - - - SRG-OS-000474-GPOS-00219 - <GroupDescription></GroupDescription> - - WN19-AU-000250 - Windows Server 2019 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. +Select "Remove Roles and Features" from the drop-down "TASKS" list. -Removable Storage auditing under Object Access 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000172 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. +Select the appropriate server on the "Server Selection" page and click "Next". -Use the "AuditPol" tool to review the current Audit Policy configuration: +Deselect "FTP Server" under "Web Server (IIS)" on the "Roles" page. -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Click "Next" and "Remove" as prompted. + + + + If the server has the role of an FTP server, this is NA. -Enter "AuditPol /get /category:*" +Open "PowerShell". -Compare the "AuditPol" settings with the following: +Enter "Get-WindowsFeature | Where Name -eq Web-Ftp-Service". -If the system does not audit the following, this is a finding. +If "Installed State" is "Installed", this is a finding. -Object Access >> Removable Storage - Failure +An Installed State of "Available" or "Removed" is not a finding. -Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. +If the system has the role of an FTP server, this must be documented with the ISSO. - - SRG-OS-000472-GPOS-00217 + + SRG-OS-000096-GPOS-00050 <GroupDescription></GroupDescription> - - WN19-AU-000180 - Windows Server 2019 must be configured to audit 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. - -Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000360 + Windows Server 2019 must not have the Telnet Client installed. + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000172 - CCI-000366 - Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + V-93423 + SV-103509 + CCI-000382 + Uninstall the "Telnet Client" feature. -Use the "AuditPol" tool to review the current Audit Policy configuration: +Start "Server Manager". -Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). +Select the server with the feature. -Enter "AuditPol /get /category:*" +Scroll down to "ROLES AND FEATURES" in the right pane. -Compare the "AuditPol" settings with the following: +Select "Remove Roles and Features" from the drop-down "TASKS" list. -If the system does not audit the following, this is a finding. +Select the appropriate server on the "Server Selection" page and click "Next". -Logon/Logoff >> Logoff - Success - - - - - SRG-OS-000042-GPOS-00020 - <GroupDescription></GroupDescription> - - WN19-CC-000090 - Windows Server 2019 command 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. +Deselect "Telnet Client" on the "Features" page. -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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000135 - Configure 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: +Click "Next" and "Remove" as prompted. + + + + Open "PowerShell". -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ +Enter "Get-WindowsFeature | Where Name -eq Telnet-Client". -Value Name: ProcessCreationIncludeCmdLine_Enabled +If "Installed State" is "Installed", this is a finding. -Value Type: REG_DWORD -Value: 0x00000001 (1) +An Installed State of "Available" or "Removed" is not a finding. - - SRG-OS-000042-GPOS-00020 + + SRG-OS-000104-GPOS-00051 <GroupDescription></GroupDescription> - - WN19-CC-000460 - Windows Server 2019 PowerShell script block logging 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. - -Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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> + + WN19-00-000070 + Windows Server 2019 shared user accounts must not be permitted. + <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 nonrepudiation or individual accountability for system access and resource usage.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000135 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> "Turn on PowerShell Script Block Logging" to "Enabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103523 + V-93437 + CCI-000764 + Remove unapproved shared accounts from the system. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ +Document required shared accounts with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. + + + + Determine whether any shared accounts exist. If no shared accounts exist, this is NA. -Value Name: EnableScriptBlockLogging +Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. -Value Type: REG_DWORD -Value: 0x00000001 (1) +If unapproved shared accounts exist, this is a finding. - - SRG-OS-000341-GPOS-00132 + + SRG-OS-000104-GPOS-00051 <GroupDescription></GroupDescription> - - WN19-CC-000270 - Windows Server 2019 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> + + WN19-00-000200 + Windows Server 2019 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. 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001849 - Configure 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 write events directly to an audit server, this is NA. + SV-103525 + V-93439 + CCI-000764 + Configure all enabled accounts to require passwords. -If the following registry value does not exist or is not configured as specified, this is a finding: +The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account. + + + + Review the password required status for enabled user accounts. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Application\ +Open "PowerShell". -Value Name: MaxSize +Domain Controllers: -Type: REG_DWORD -Value: 0x00008000 (32768) (or greater) +Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". + +Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). + +If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. + +Member servers and standalone systems: + +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. + +Exclude disabled accounts (e.g., DefaultAccount, Guest). + +If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. - - SRG-OS-000341-GPOS-00132 + + SRG-OS-000118-GPOS-00060 <GroupDescription></GroupDescription> - - WN19-CC-000280 - Windows Server 2019 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> + + WN19-00-000190 + Windows Server 2019 outdated or unused accounts must be removed or disabled. + <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, disabled 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001849 - Configure 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 write events directly to an audit server, this is NA. + V-93457 + SV-103543 + CCI-000795 + Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days. + + + + Open "Windows PowerShell". -If the following registry value does not exist or is not configured as specified, this is a finding: +Domain Controllers: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\ +Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" -Value Name: MaxSize +This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. -Type: REG_DWORD -Value: 0x00030000 (196608) (or greater) +Member servers and standalone systems: + +Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) + +"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { + $user = ([ADSI]$_.Path) + $lastLogin = $user.Properties.LastLogin.Value + $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 + if ($lastLogin -eq $null) { + $lastLogin = 'Never' + } + Write-Host $user.Name $lastLogin $enabled +}" + +This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). +For example: User1 10/31/2015 5:49:56 AM True + +Review the list of accounts returned by the above queries to determine the finding validity for each account reported. + +Exclude the following accounts: + +- Built-in administrator account (Renamed, SID ending in 500) +- Built-in guest account (Renamed, Disabled, SID ending in 501) +- Application accounts + +If any enabled accounts have not been logged on to within the past 35 days, this is a finding. + +Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO. - - SRG-OS-000341-GPOS-00132 + + SRG-OS-000120-GPOS-00061 <GroupDescription></GroupDescription> - - WN19-CC-000290 - Windows Server 2019 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> + + WN19-SO-000290 + Windows Server 2019 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites. + <VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. + +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001849 - Configure 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 write events directly to an audit server, this is NA. + V-93495 + SV-103581 + CCI-000803 + Configure 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: -If the following registry value does not exist or is not configured as specified, this is a finding: +AES128_HMAC_SHA1 +AES256_HMAC_SHA1 +Future encryption types + +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship. + + + + 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\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\ -Value Name: MaxSize +Value Name: SupportedEncryptionTypes -Type: REG_DWORD -Value: 0x00008000 (32768) (or greater) +Value Type: REG_DWORD +Value: 0x7ffffff8 (2147483640) - - SRG-OS-000342-GPOS-00133 + + SRG-OS-000123-GPOS-00064 <GroupDescription></GroupDescription> - - WN19-AU-000010 - Windows Server 2019 audit records must be backed up to a different system or media than the system being audited. - <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001851 - Establish and implement a process for backing up log data to another system or media other than the system being audited. - - - - Determine if a process to back up log data to a different system or media than the system being audited has been implemented. + + WN19-00-000310 + Windows Server 2019 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours. + <VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. -If it has not, this is a finding. - - - - - SRG-OS-000479-GPOS-00224 - <GroupDescription></GroupDescription> - - WN19-AU-000020 - Windows Server 2019 must, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly. - <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001851 - Configure the system to, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly. - - - - Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. +Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. -If they are not, this is a finding. - - - - - SRG-OS-000355-GPOS-00143 - <GroupDescription></GroupDescription> - - WN19-00-000440 - The Windows Server 2019 time service must synchronize with an appropriate DoD time source. - <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> +To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001891 - Configure the system to synchronize time with an appropriate DoD time source. + V-92977 + SV-103065 + CCI-001682 + Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours. -Domain-joined systems use NT5DS to synchronize time from other systems in the domain by default. +Domain accounts can be configured with an account expiration date, under "Account" properties. -If 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 appropriate DoD time server. +Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. + + + + Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. -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. - - - - Review the Windows time service configuration. +If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. -Open an elevated "Command Prompt" (run as administrator). +If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. -Enter "W32tm /query /configuration". +Domain Controllers: -Domain-joined systems (excluding the domain controller with the PDC emulator role): +Open "PowerShell". -If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. +Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". -Other systems: +If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. -If systems are configured with a "Type" of "NTP", including standalone systems and the domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. +Member servers and standalone systems: -To determine the domain controller with the PDC Emulator role: +Open "Command Prompt". -Open "PowerShell". +Run "Net user [username]", where [username] is the name of the emergency account. -Enter "Get-ADDomain | FT PDCEmulator". +If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. - - SRG-OS-000057-GPOS-00027 + + SRG-OS-000125-GPOS-00065 <GroupDescription></GroupDescription> - - WN19-AU-000030 - Windows Server 2019 permissions 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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000470 + Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000162 - CCI-000163 - CCI-000164 - Configure the permissions on the Application event log file (Application.evtx) to prevent access by non-privileged accounts. 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" folder. - -If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". - - - - Navigate to the Application event log file. + V-93503 + SV-103589 + CCI-000877 + Configure 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: -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: +Value Name: AllowBasic -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000057-GPOS-00027 + + SRG-OS-000125-GPOS-00065 <GroupDescription></GroupDescription> - - WN19-AU-000040 - Windows Server 2019 permissions 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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000490 + Windows Server 2019 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. Disallowing Digest authentication will reduce this potential.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000162 - CCI-000163 - CCI-000164 - Configure the permissions on the Security event log file (Security.evtx) to prevent access by non-privileged accounts. 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" folder. - -If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". - - - - Navigate to the Security event log file. + SV-103591 + V-93505 + CCI-000877 + Configure 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: -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: +Value Name: AllowDigest -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000057-GPOS-00027 + + SRG-OS-000125-GPOS-00065 <GroupDescription></GroupDescription> - - WN19-AU-000050 - Windows Server 2019 permissions 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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000500 + Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000162 - CCI-000163 - CCI-000164 - Configure the permissions on the System event log file (System.evtx) to prevent access by non-privileged accounts. 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" folder. - -If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog". - - - - Navigate to the System event log file. + V-93507 + SV-103593 + CCI-000877 + Configure 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: -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: +Value Name: AllowBasic -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000257-GPOS-00098 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-AU-000060 - Windows Server 2019 Event Viewer must be protected from unauthorized modification and deletion. - <VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. - -Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. - -Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000240 + Windows Server 2019 administrator accounts must not be enumerated during elevation. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001494 - CCI-001495 - Configure the permissions on the "Eventvwr.exe" file to prevent modification by any groups or accounts other than TrustedInstaller. The default permissions listed below satisfy this requirement: + V-93517 + SV-103603 + CCI-001084 + Configure 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: -TrustedInstaller - Full Control -Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute - -The default location is the "%SystemRoot%\System32" folder. - - - - Navigate to "%SystemRoot%\System32". - -View the permissions on "Eventvwr.exe". - -If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ -The default permissions below satisfy this requirement: +Value Name: EnumerateAdministrators -TrustedInstaller - Full Control -Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000362-GPOS-00149 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-CC-000420 - Windows Server 2019 must prevent users 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> + + WN19-MS-000020 + Windows Server 2019 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers. + <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 local 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001812 - Configure 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: + V-93519 + SV-103605 + CCI-001084 + Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Apply UAC restrictions to local accounts on network logons" to "Enabled". -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ +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. + + + + This applies to member servers. For domain controllers and standalone systems, this is NA. -Value Name: EnableUserControl +If the following registry value does not exist or is not configured as specified, this is a finding: -Type: REG_DWORD -Value: 0x00000000 (0) +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + +Value Name: LocalAccountTokenFilterPolicy + +Type: REG_DWORD +Value: 0x00000000 (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. - - SRG-OS-000362-GPOS-00149 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-CC-000430 - Windows Server 2019 must disable the Windows Installer Always install with elevated privileges option. - <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></IAControls> + + WN19-SO-000390 + Windows Server 2019 UIAccess applications must not be allowed to prompt for elevation without using 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 prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001812 - Configure 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: + V-93521 + SV-103607 + CCI-001084 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" to "Disabled". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\Installer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: AlwaysInstallElevated +Value Name: EnableUIADesktopToggle -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000000 (0) - - SRG-OS-000363-GPOS-00150 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-00-000220 - Windows Server 2019 system files must be monitored for unauthorized changes. - <VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code 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> + + WN19-SO-000400 + Windows Server 2019 User Account Control must, at a 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001744 - Monitor the system for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools. - - - - Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. + SV-103609 + V-93523 + CCI-001084 + Configure 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". -If system files are not monitored for unauthorized changes, this is a finding. +The more secure option for this setting, "Prompt for credentials on the secure desktop", would also be acceptable. + + + + UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: ConsentPromptBehaviorAdmin -A properly configured HBSS Policy Auditor 5.2 or later File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. The Asset module within HBSS does not meet this requirement. +Value Type: REG_DWORD +Value: 0x00000002 (2) (Prompt for consent on the secure desktop) +0x00000001 (1) (Prompt for credentials on the secure desktop) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-00-000030 - Windows Server 2019 administrative accounts must 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 account. - -Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to 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. - -Whitelisting can be used to enforce the policy to ensure compliance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000420 + Windows Server 2019 User 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. Ensure the policy is enforced. + SV-103611 + V-93525 + CCI-001084 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. - - - - Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. +If the following registry value does not exist or is not configured as specified, this is a finding: -If it does not, this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. +Value Name: EnableInstallerDetection + +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-00-000040 - Windows Server 2019 members 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> + + WN19-SO-000430 + Windows Server 2019 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations. + <VulnDiscussion>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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions. - - - - If no accounts are members of the Backup Operators group, this is NA. + V-93527 + SV-103613 + CCI-001084 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. +If the following registry value does not exist or is not configured as specified, this is a finding: -If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: EnableSecureUIAPaths + +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000134-GPOS-00068 <GroupDescription></GroupDescription> - - WN19-00-000060 - Windows Server 2019 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization. - <VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account passwords.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000450 + Windows Server 2019 User Account Control (UAC) must virtualize file and registry write failures to per-user locations. + <VulnDiscussion>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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization. - -It is recommended that system-managed service accounts be used whenever possible. - - - - Determine if manually managed application/service accounts exist. If none exist, this is NA. - -If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. - -Identify manually managed application/service accounts. - -To determine the date a password was last changed: - -Domain controllers: - -Open "PowerShell". - -Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. - -If the "PasswordLastSet" date is more than one year old, this is a finding. - + V-93529 + SV-103615 + CCI-001084 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -Member servers and standalone systems: +If the following registry value does not exist or is not configured as specified, this is a finding: -Open "Command Prompt". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. +Value Name: EnableVirtualization -If the "Password Last Set" date is more than one year old, this is a finding. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000138-GPOS-00069 <GroupDescription></GroupDescription> - - WN19-00-000090 - Windows Server 2019 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use. - <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000230 + Windows Server 2019 non-system-created file shares must limit access to groups that require it. + <VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.) + SV-103617 + V-93531 + CCI-001090 + If a non-system-created share is required on a system, configure the share and NTFS permissions to limit access to the specific groups or accounts that require it. -The TPM must be enabled in the firmware. +Remove any unnecessary non-system-created shares. + + + + If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) -Run "tpm.msc" for configuration options in Windows. - - - - For standalone systems, this is NA. +Run "Computer Management". -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. +Navigate to System Tools >> Shared Folders >> Shares. -Verify the system has a TPM and it is ready for use. +Right-click any non-system-created shares. -Run "tpm.msc". +Select "Properties". -Review the sections in the center pane. +Select the "Share Permissions" tab. -"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". +If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. -TPM Manufacturer Information - Specific Version = 2.0 or 1.2 +Select the "Security" tab. -If a TPM is not found or is not ready for use, this is a finding. +If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000138-GPOS-00069 <GroupDescription></GroupDescription> - - WN19-00-000100 - Windows Server 2019 must be maintained at a supported servicing level. - <VulnDiscussion>Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level 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> + + WN19-CC-000350 + Windows Server 2019 Remote Desktop Services must prevent drive redirection. + <VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Update the system to a Version 1809 (Build 17763.xxx) or greater. - - - - Open "Command Prompt". + SV-103619 + V-93533 + CCI-001090 + Configure 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: -Enter "winver.exe". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -If the "About Windows" dialog box does not display "Microsoft Windows Server Version 1809 (Build 17763.xxx)" or greater, this is a finding. +Value Name: fDisableCdm -Preview versions must not be used in a production environment. +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000138-GPOS-00069 <GroupDescription></GroupDescription> - - WN19-00-000110 - Windows Server 2019 must use an anti-virus program. - <VulnDiscussion>Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000230 + Windows Server 2019 must not allow anonymous enumeration of shares. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Install an anti-virus solution on the system. - - - - Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution. + V-93537 + SV-103623 + CCI-001090 + Configure 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". + + + + 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\Lsa\ + +Value Name: RestrictAnonymous -If there is no anti-virus solution installed on the system, this is a finding. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000138-GPOS-00069 <GroupDescription></GroupDescription> - - WN19-00-000120 - Windows Server 2019 must have a host-based intrusion detection or prevention system. - <VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000250 + Windows Server 2019 must restrict anonymous access to Named Pipes and Shares. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Install a HIDS or HIPS on each server. - - - - Determine whether there is a HIDS or HIPS on each server. + V-93539 + SV-103625 + CCI-001090 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. +Value Name: RestrictNullSessAccess -If a HIDS is not installed on the system, this is a finding. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000185-GPOS-00079 <GroupDescription></GroupDescription> - - WN19-00-000240 - Windows Server 2019 must have software certificate installation files removed. - <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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Remove any certificate installation files (*.p12 and *.pfx) found on a system. + + WN19-00-000250 + Windows Server 2019 systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. + <VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. -Note: This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. - - - - Search all drives for *.p12 and *.pfx files. +Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). -If any files with these extensions exist, this is a finding. +Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93515 + SV-103601 + CCI-001199 + CCI-002475 + CCI-002476 + Configure systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data to employ encryption to protect the confidentiality and integrity of all information at rest. + + + + Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. -This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. 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. +If they do not, this is a finding. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000191-GPOS-00080 <GroupDescription></GroupDescription> - - WN19-00-000420 - Windows Server 2019 FTP servers must be configured to prevent anonymous logons. - <VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. - -Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000290 + Windows Server 2019 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Host Based Security System (HBSS) is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). + <VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the FTP service to prevent anonymous logons. - -Open "Internet Information Services (IIS) Manager". - -Select the server. - -Double-click "FTP Authentication". + SV-103653 + V-93567 + CCI-001233 + Install a DoD-approved ESS software and ensure it is operating continuously. + + + + Verify DoD-approved ESS software is installed and properly operating. Ask the site ISSM for documentation of the ESS software installation and configuration. -Select "Anonymous Authentication". - -Select "Disabled" under "Actions". - - - - If FTP is not installed on the system, this is NA. - -Open "Internet Information Services (IIS) Manager". - -Select the server. +If the ISSM is not able to provide a documented configuration for an installed ESS or if the ESS software is not properly maintained or used, this is a finding. -Double-click "FTP Authentication". - -If the "Anonymous Authentication" status is "Enabled", this is a finding. +Note: Example of documentation can be a copy of the site's CCB approved Software Baseline with version of software noted or a memo from the ISSM stating current ESS software and version. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000240-GPOS-00090 <GroupDescription></GroupDescription> - - WN19-00-000430 - Windows Server 2019 FTP servers must be configured to prevent access to the system drive. - <VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000150 + Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. + +Account Lockout events can be used to identify potentially malicious logon attempts. + +Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system. - - - - If FTP is not installed on the system, this is NA. + SV-103075 + V-92987 + CCI-001404 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Open "Internet Information Services (IIS) Manager". +Use the "AuditPol" tool to review the current Audit Policy configuration: -Select "Sites" under the server name. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -For any sites with a Binding that lists FTP, right-click the site and select "Explore". +Enter "AuditPol /get /category:*" -If the site is not defined to a specific folder for shared FTP resources, this is a finding. +Compare the "AuditPol" settings with the following: -If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding. +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Account Lockout - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000240-GPOS-00090 <GroupDescription></GroupDescription> - - WN19-00-000460 - Windows Server 2019 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS. - <VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000160 + Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. + +Account Lockout events can be used to identify potentially malicious logon attempts. + +Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode. - - - - Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must run in "UEFI" mode. + V-92989 + SV-103077 + CCI-000172 + CCI-001404 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". +Use the "AuditPol" tool to review the current Audit Policy configuration: -Run "System Information". +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding. +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 >> Account Lockout - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000257-GPOS-00098 <GroupDescription></GroupDescription> - - WN19-00-000470 - Windows Server 2019 must have Secure Boot enabled. - <VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000060 + Windows Server 2019 Event Viewer must be protected from unauthorized modification and deletion. + <VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. + +Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. + +Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Enable Secure Boot in the system firmware. - - - - Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must have Secure Boot enabled. + SV-103283 + V-93195 + CCI-001494 + CCI-001495 + Configure the permissions on the "Eventvwr.exe" file to prevent modification by any groups or accounts other than TrustedInstaller. The default permissions listed below satisfy this requirement: -Run "System Information". +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute -Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. +The default location is the "%SystemRoot%\System32" folder. + + + + Navigate to "%SystemRoot%\System32". -On server core installations, run the following PowerShell command: +View the permissions on "Eventvwr.exe". -Confirm-SecureBootUEFI +If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. -If a value of "True" is not returned, this is a finding. +The default permissions below satisfy this requirement: + +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000312-GPOS-00122 <GroupDescription></GroupDescription> - - WN19-CC-000030 - Windows Server 2019 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing. - <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></IAControls> + + WN19-00-000140 + Windows Server 2019 permissions for the system drive root directory (usually C:\) 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. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. + V-93019 + SV-103107 + CCI-002165 + Maintain the default permissions for the system drive's root directory and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: +Default Permissions +C:\ +Type - "Allow" for all +Inherited from - "None" for all -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ +Principal - Access - Applies to -Value Name: DisableIPSourceRouting +SYSTEM - Full control - This folder, subfolders, and files +Administrators - Full control - This folder, subfolders, and files +Users - Read & execute - This folder, subfolders, and files +Users - Create folders/append data - This folder and subfolders +Users - Create files/write data - Subfolders only +CREATOR OWNER - Full Control - Subfolders and files only + + + + The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). -Type: REG_DWORD -Value: 0x00000002 (2) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000040 - Windows Server 2019 source routing must be configured to the highest protection level to prevent Internet Protocol (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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. +Review the permissions for the system drive's root directory (usually C:\). 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. -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: +If permissions are not as restrictive as the default permissions listed below, this is a finding. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ +Viewing in File Explorer: -Value Name: DisableIPSourceRouting +View the Properties of the system drive's root directory. -Value Type: REG_DWORD -Value: 0x00000002 (2) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000050 - Windows Server 2019 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 the 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" to "Disabled". +Select the "Security" tab, and the "Advanced" button. -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: +Default permissions: +C:\ +Type - "Allow" for all +Inherited from - "None" for all -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ +Principal - Access - Applies to -Value Name: EnableICMPRedirect +SYSTEM - Full control - This folder, subfolders, and files +Administrators - Full control - This folder, subfolders, and files +Users - Read & execute - This folder, subfolders, and files +Users - Create folders/append data - This folder and subfolders +Users - Create files/write data - Subfolders only +CREATOR OWNER - Full Control - Subfolders and files only -Value Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000070 - Windows Server 2019 insecure logons to an SMB server must be disabled. - <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Lanman Workstation >> "Enable insecure guest logons" to "Disabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Alternately, use icacls: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation\ +Open "Command Prompt (Admin)". -Value Name: AllowInsecureGuestAuth +Enter "icacls" followed by the directory: -Type: REG_DWORD -Value: 0x00000000 (0) +"icacls c:\" + +The following results should be displayed: + +c:\ +NT AUTHORITY\SYSTEM:(OI)(CI)(F) +BUILTIN\Administrators:(OI)(CI)(F) +BUILTIN\Users:(OI)(CI)(RX) +BUILTIN\Users:(CI)(AD) +BUILTIN\Users:(CI)(IO)(WD) +CREATOR OWNER:(OI)(CI)(IO)(F) +Successfully processed 1 files; Failed processing 0 files - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000312-GPOS-00122 <GroupDescription></GroupDescription> - - WN19-CC-000080 - Windows Server 2019 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares. - <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000150 + Windows Server 2019 permissions for program file 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. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Network Provider >> "Hardened UNC Paths" to "Enabled" with at least the following configured in "Hardened UNC Paths" (click the "Show" button to display): - -Value Name: \\*\SYSVOL -Value: RequireMutualAuthentication=1, RequireIntegrity=1 + V-93021 + SV-103109 + CCI-002165 + Maintain the default permissions for the program file directories and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). -Value Name: \\*\NETLOGON -Value: RequireMutualAuthentication=1, RequireIntegrity=1 - - - - This requirement is applicable to domain-joined systems. For standalone systems, this is NA. +Default permissions: +\Program Files and \Program Files (x86) +Type - "Allow" for all +Inherited from - "None" for all -If the following registry values do not exist or are not configured as specified, this is a finding: +Principal - Access - Applies to -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + + + + The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). -Value Name: \\*\NETLOGON -Value Type: REG_SZ -Value: RequireMutualAuthentication=1, RequireIntegrity=1 +Review the permissions for the program file directories (Program Files and Program Files [x86]). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. -Value Name: \\*\SYSVOL -Value Type: REG_SZ -Value: RequireMutualAuthentication=1, RequireIntegrity=1 +If permissions are not as restrictive as the default permissions listed below, this is a finding. -Additional entries would not be a finding. - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000100 - Windows Server 2019 must be configured to enable Remote host allows delegation of non-exportable credentials. - <VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Remote host allows delegation of non-exportable credentials" to "Enabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Viewing in File Explorer: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ +For each folder, view the Properties. -Value Name: AllowProtectedCreds +Select the "Security" tab, and the "Advanced" button. -Type: REG_DWORD -Value: 0x00000001 (1) +Default permissions: +\Program Files and \Program Files (x86) +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + +Alternately, use icacls: + +Open a Command prompt (admin). + +Enter "icacls" followed by the directory: + +'icacls "c:\program files"' +'icacls "c:\program files (x86)"' + +The following results should be displayed for each when entered: + +c:\program files (c:\program files (x86)) +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) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +Successfully processed 1 files; Failed processing 0 files - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000312-GPOS-00122 <GroupDescription></GroupDescription> - - WN19-CC-000110 - Windows Server 2019 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection. - <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000160 + Windows Server 2019 permissions for the Windows installation directory 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. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Secure Boot" or "Secure Boot and DMA Protection" selected. - -A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: - -https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard - - - - For standalone systems, this is NA. - -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. - -Open "PowerShell" with elevated privileges (run as administrator). + SV-103111 + V-93023 + CCI-002165 + Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). -Enter the following: +Default permissions: +Type - "Allow" for all +Inherited from - "None" for all -"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" +Principal - Access - Applies to -If "RequiredSecurityProperties" does not include a value of "2" indicating "Secure Boot" (e.g., "{1, 2}"), this is a finding. +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + + + + The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). -If "Secure Boot and DMA Protection" is configured, "3" will also be displayed in the results (e.g., "{1, 2, 3}"). +Review the permissions for the Windows installation directory (usually C:\Windows). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. -If "VirtualizationBasedSecurityStatus" is not a value of "2" indicating "Running", this is a finding. +If permissions are not as restrictive as the default permissions listed below, this is a finding: -Alternately: +Viewing in File Explorer: -Run "System Information". +For each folder, view the Properties. -Under "System Summary", verify the following: +Select the "Security" tab and the "Advanced" button. -If "Device Guard Virtualization based security" does not display "Running", this is a finding. +Default permissions: +\Windows +Type - "Allow" for all +Inherited from - "None" for all -If "Device Guard Required Security Properties" does not display "Base Virtualization Support, Secure Boot", this is a finding. +Principal - Access - Applies to -If "Secure Boot and DMA Protection" is configured, "DMA Protection" will also be displayed (e.g., "Base Virtualization Support, Secure Boot, DMA Protection"). +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files -The policy settings referenced in the Fix section will configure the following registry values. However, due to hardware requirements, the registry values alone do not ensure proper function. +Alternately, use icacls: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ +Open a Command prompt (admin). -Value Name: EnableVirtualizationBasedSecurity -Value Type: REG_DWORD -Value: 0x00000001 (1) +Enter "icacls" followed by the directory: -Value Name: RequirePlatformSecurityFeatures -Value Type: REG_DWORD -Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) +"icacls c:\windows" -A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: +The following results should be displayed for each when entered: -https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard +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) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +Successfully processed 1 files; Failed processing 0 files - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-CC-000130 - Windows Server 2019 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad. - <VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls> + + WN19-00-000170 + Windows Server 2019 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained. + <VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). + SV-103113 + V-93025 + CCI-002235 + Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive. -If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> "Boot-Start Driver Initialization Policy" to "Not Configured" or "Enabled" with any option other than "All" selected. - - - - The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). +The default permissions of the higher-level keys are noted below. -If the registry value name below does not exist, this is not a finding. +HKEY_LOCAL_MACHINE\SECURITY -If it exists and is configured with a value of "0x00000007 (7)", this is a finding. +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +SYSTEM - Full Control - This key and subkeys +Administrators - Special - This key and subkeys -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ +HKEY_LOCAL_MACHINE\SOFTWARE -Value Name: DriverLoadPolicy +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - This key and subkeys +ALL APPLICATION PACKAGES - Read - This key and subkeys -Value Type: REG_DWORD -Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) +HKEY_LOCAL_MACHINE\SYSTEM -Possible values for this setting are: -8 - Good only -1 - Good and unknown -3 - Good, unknown and bad but critical -7 - All (which includes "bad" and would be a finding) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000140 - Windows Server 2019 group policy objects must be reprocessed even if they have not changed. - <VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Group Policy >> "Configure registry policy processing" to "Enabled" with the option "Process even if the Group Policy objects have not changed" selected. - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - Subkeys only +ALL APPLICATION PACKAGES - Read - This key and subkeys -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ +Microsoft has also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID. +S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 + + + + Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. -Value Name: NoGPOListChanges +If any non-privileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000180 - Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (on battery). - <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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: +If permissions are not as restrictive as the default permissions listed below, this is a finding: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ +Run "Regedit". -Value Name: DCSettingIndex +Right-click on the registry areas noted below. -Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000480-GPOS-00227 - <GroupDescription></GroupDescription> - - WN19-CC-000190 - Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (plugged in). - <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000366 - Configure 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: +Select "Permissions" and the "Advanced" button. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ +HKEY_LOCAL_MACHINE\SECURITY -Value Name: ACSettingIndex +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +SYSTEM - Full Control - This key and subkeys +Administrators - Special - This key and subkeys + +HKEY_LOCAL_MACHINE\SOFTWARE + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - This key and subkeys +ALL APPLICATION PACKAGES - Read - This key and subkeys + +HKEY_LOCAL_MACHINE\SYSTEM + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - Subkeys only +ALL APPLICATION PACKAGES - Read - This key and subkeys + +Other examples under the noted keys may also be sampled. There may be some instances where non-privileged groups have greater than Read permission. + +Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID, this is currently not a finding. +S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 -Type: REG_DWORD -Value: 0x00000001 (1) +If the defaults have not been changed, these are not a finding. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-CC-000250 - Windows Server 2019 Telemetry must be configured to Security or Basic. - <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-MS-000010 + Windows Server 2019 must only allow administrators responsible for the member server or standalone system to 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 using only accounts with the minimum level of authority necessary. + +For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group (see V-36433 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. + +Standard user accounts must not be members of the built-in 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Data Collection and Preview Builds>> "Allow Telemetry" to "Enabled" with "0 - Security [Enterprise Only]" or "1 - Basic" selected in "Options". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93043 + SV-103131 + CCI-002235 + Configure the local "Administrators" group to include only administrator groups or accounts responsible for administration of the system. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DataCollection\ +For domain-joined member servers, replace the Domain Admins group with a domain member server administrator group. -Value Name: AllowTelemetry +Remove any standard user accounts. + + + + This applies to member servers and standalone systems. A separate version applies to domain controllers. -Type: REG_DWORD -Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic) +Open "Computer Management". + +Navigate to "Groups" under "Local Users and Groups". + +Review the local "Administrators" group. + +Only administrator groups or accounts responsible for administration of the system may be members of the group. + +For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group. + +Standard user accounts must not be members of the local Administrator group. + +If accounts that do not have responsibility for administration of the system are members of the local Administrators group, this is a finding. + +If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - - WN19-CC-000260 - Windows Server 2019 Windows Update must not obtain updates from other PCs on the Internet. - <VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-MS-000060 + Windows Server 2019 must restrict remote calls to the Security Account Manager (SAM) to Administrators on domain-joined member servers and standalone systems. + <VulnDiscussion>The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Delivery Optimization >> "Download Mode" to "Enabled" with any option except "Internet" selected. + SV-103133 + V-93045 + CCI-002235 + Navigate to the policy Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Restrict clients allowed to make remote calls to SAM". +Select "Edit Security" to configure the "Security descriptor:". -Acceptable selections include: +Add "Administrators" in "Group or user names:" if it is not already listed (this is the default). -Bypass (100) -Group (2) -HTTP only (0) -LAN (1) -Simple (99) - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Select "Administrators" in "Group or user names:". -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\ +Select "Allow" for "Remote Access" in "Permissions for "Administrators". -Value Name: DODownloadMode +Click "OK". -Value Type: REG_DWORD -Value: 0x00000000 (0) - No peering (HTTP Only) -0x00000001 (1) - Peers on same NAT only (LAN) -0x00000002 (2) - Local Network / Private group peering (Group) -0x00000063 (99) - Simple download mode, no peering (Simple) -0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) +The "Security descriptor:" must be populated with "O:BAG:BAD:(A;;RC;;;BA) for the policy to be enforced. + + + + This applies to member servers and standalone systems; it is NA for domain controllers. -A value of 0x00000003 (3), Internet, is a finding. +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\Lsa\ + +Value Name: RestrictRemoteSAM + +Value Type: REG_SZ +Value: O:BAG:BAD:(A;;RC;;;BA) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000320 - Windows Server 2019 Turning 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></IAControls> + + WN19-AU-000090 + Windows Server 2019 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 Events records events such as the access of a password hash or the Password Policy Checking API being called. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - The default behavior is for File Explorer heap termination on corruption to be disabled. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off heap termination on corruption" to "Not Configured" or "Disabled". - - - - The default behavior is for File Explorer heap termination on corruption to be enabled. + V-93089 + SV-103177 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If the registry Value Name below does not exist, this is not a finding. +Use the "AuditPol" tool to review the current Audit Policy configuration: -If it exists and is configured with a value of "0", this is not a finding. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -If it exists and is configured with a value of "1", this is a finding. +Enter "AuditPol /get /category:*" -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ +Compare the "AuditPol" settings with the following: -Value Name: NoHeapTerminationOnCorruption +If the system does not audit the following, this is a finding: -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) +Account Management >> Other Account Management Events - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000330 - Windows Server 2019 File Explorer shell protocol must run in protected mode. - <VulnDiscussion>The shell protocol will limit the set of folders that 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> + + WN19-AU-000140 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - The default behavior is for shell protected mode to be turned on for File Explorer. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off shell protocol protected mode" to "Not Configured" or "Disabled". - - - - The default behavior is for shell protected mode to be turned on for File Explorer. + V-93091 + SV-103179 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If the registry value name below does not exist, this is not a finding. +Use the "AuditPol" tool to review the current Audit Policy configuration: -If it exists and is configured with a value of "0", this is not a finding. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -If it exists and is configured with a value of "1", this is a finding. +Enter "AuditPol /get /category:*" -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ +Compare the "AuditPol" settings with the following: -Value Name: PreXPSP2ShellProtocolBehavior +If the system does not audit the following, this is a finding. -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) +Detailed Tracking >> Process Creation - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000390 - Windows Server 2019 must prevent attachments 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> + + WN19-AU-000260 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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: + SV-103181 + V-93093 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: DisableEnclosureDownload +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Type: REG_DWORD -Value: 0x00000001 (1) +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 - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000440 - Windows Server 2019 users must be notified if a web-based program attempts to install software. - <VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000270 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> "Prevent Internet Explorer security prompt for Windows Installer scripts" to "Not Configured" or "Disabled". - - - - The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. + SV-103183 + V-93095 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If the registry value name below does not exist, this is not a finding. +Use the "AuditPol" tool to review the current Audit Policy configuration: -If it exists and is configured with a value of "0", this is not a finding. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -If it exists and is configured with a value of "1", this is a finding. +Enter "AuditPol /get /category:*" -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ +Compare the "AuditPol" settings with the following: -Value Name: SafeForScripting +If the system does not audit the following, this is a finding. -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) +Policy Change >> Audit Policy Change - Failure - - SRG-OS-000480-GPOS-00229 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-CC-000450 - Windows Server 2019 must disable automatically signing in the last interactive user after a system-initiated restart. - <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> + + WN19-AU-000280 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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. + V-93097 + SV-103185 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: DisableAutomaticRestartSignOn +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Type: REG_DWORD -Value: 0x00000001 (1) +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 - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-MS-000050 - Windows Server 2019 must limit the caching of logon credentials to four or less on domain-joined member servers. - <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> + + WN19-AU-000290 + Windows Server 2019 must be configured to audit Policy Change - Authorization 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. + +Authorization Policy Change records events related to changes in user rights, such as "Create a token object". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - 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. - - - - This applies to member servers. For domain controllers and standalone systems, this is NA. + V-93099 + SV-103187 + CCI-002234 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> "Audit Authorization 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If the following registry value does not exist or is not configured as specified, this is a finding: +Use the "AuditPol" tool to review the current Audit Policy configuration: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Name: CachedLogonsCount +Enter "AuditPol /get /category:*" -Value Type: REG_SZ -Value: 4 (or less) +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Policy Change >> Authorization Policy Change - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-MS-000140 - Windows Server 2019 must be running Credential Guard on domain-joined member servers. - <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. This authentication information, which was stored in the Local Security Authority (LSA) in previous versions of Windows, is isolated from the rest of operating system and can only be accessed by privileged system software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000300 + Windows Server 2019 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". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Enabled with UEFI lock" selected for "Credential Guard Configuration". - -A Microsoft article on Credential Guard system requirement can be found at the following link: - -https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements - - - - For domain controllers and standalone systems, this is NA. + V-93101 + SV-103189 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. +Use the "AuditPol" tool to review the current Audit Policy configuration: -Open "PowerShell" with elevated privileges (run as administrator). +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Enter the following: +Enter "AuditPol /get /category:*" -"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" +Compare the "AuditPol" settings with the following: -If "SecurityServicesRunning" does not include a value of "1" (e.g., "{1, 2}"), this is a finding. +If the system does not audit the following, this is a finding. -Alternately: +Privilege Use >> Sensitive Privilege Use - Success + + + + + SRG-OS-000327-GPOS-00127 + <GroupDescription></GroupDescription> + + WN19-AU-000310 + Windows Server 2019 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. -Run "System Information". +Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs". -Under "System Summary", verify the following: +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93103 + SV-103191 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If "Device Guard Security Services Running" does not list "Credential Guard", this is a finding. +Use the "AuditPol" tool to review the current Audit Policy configuration: -The policy settings referenced in the Fix section will configure the following registry value. However, due to hardware requirements, the registry value alone does not ensure proper function. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ +Enter "AuditPol /get /category:*" -Value Name: LsaCfgFlags -Value Type: REG_DWORD -Value: 0x00000001 (1) (Enabled with UEFI lock) +Compare the "AuditPol" settings with the following: -A Microsoft article on Credential Guard system requirement can be found at the following link: +If the system does not audit the following, this is a finding. -https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements +Privilege Use >> Sensitive Privilege Use - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-SO-000020 - Windows Server 2019 must prevent local accounts with blank passwords from being used 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 does 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> + + WN19-AU-000320 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93105 + SV-103193 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: LimitBlankPasswordUse +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Type: REG_DWORD -Value: 0x00000001 (1) +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 - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-SO-000100 - Windows Server 2019 maximum age for machine account passwords must be configured to 30 days or less. - <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 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> + + WN19-AU-000330 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - This is the default configuration for this setting (30 days). + V-93107 + SV-103195 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Configure 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). - - - - This is the default configuration for this setting (30 days). +Use the "AuditPol" tool to review the current Audit Policy configuration: -If the following registry value does not exist or is not configured as specified, this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ +Enter "AuditPol /get /category:*" -Value Name: MaximumPasswordAge +Compare the "AuditPol" settings with the following: -Value Type: REG_DWORD -Value: 0x0000001e (30) (or less, but not 0) +If the system does not audit the following, this is a finding. + +System >> IPsec Driver - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-SO-000150 - Windows Server 2019 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> + + WN19-AU-000340 + Windows Server 2019 must be configured to audit System - Other System 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. + +Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103197 + V-93109 + CCI-000172 + CCI-002234 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: scremoveoption +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Type: REG_SZ -Value: 1 (Lock Workstation) or 2 (Force Logoff) +Enter "AuditPol /get /category:*" -If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO. +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> Other System Events - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-SO-000210 - Windows Server 2019 must not allow anonymous SID/Name translation. - <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> + + WN19-AU-000350 + Windows Server 2019 must be configured to audit System - Other System 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. + +Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Allow anonymous SID/Name translation" to "Disabled". - - - - Verify the effective setting in Local Group Policy Editor. + V-93111 + SV-103199 + CCI-002234 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Run "gpedit.msc". +Use the "AuditPol" tool to review the current Audit Policy configuration: -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding. +Enter "AuditPol /get /category:*" + +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +System >> Other System Events - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-SO-000220 - Windows Server 2019 must not allow anonymous enumeration of Security Account Manager (SAM) accounts. - <VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls> + + WN19-AU-000360 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103201 + V-93113 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: RestrictAnonymousSAM +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Type: REG_DWORD -Value: 0x00000001 (1) +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 - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-SO-000240 - Windows Server 2019 must be configured to prevent anonymous users from having the same permissions as the Everyone group. - <VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls> + + WN19-AU-000370 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93115 + SV-103203 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: EveryoneIncludesAnonymous +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Value Type: REG_DWORD -Value: 0x00000000 (0) +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 - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-SO-000260 - Windows Server 2019 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously. - <VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls> + + WN19-AU-000380 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93117 + SV-103205 + CCI-000172 + CCI-002234 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: UseMachineId +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Type: REG_DWORD -Value: 0x00000001 (1) +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 - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000327-GPOS-00127 <GroupDescription></GroupDescription> - - WN19-SO-000270 - Windows Server 2019 must prevent NTLM 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></IAControls> + + WN19-AU-000390 + Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network security: Allow LocalSystem NULL session fallback" to "Disabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93119 + SV-103207 + CCI-002234 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ +Use the "AuditPol" tool to review the current Audit Policy configuration: -Value Name: allownullsessionfallback +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Type: REG_DWORD -Value: 0x00000000 (0) +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 - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000341-GPOS-00132 <GroupDescription></GroupDescription> - - WN19-SO-000280 - Windows Server 2019 must prevent PKU2U authentication using online identities. - <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></IAControls> + + WN19-CC-000270 + Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103265 + V-93177 + CCI-001849 + Configure 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 write events directly to an audit server, 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: \SYSTEM\CurrentControlSet\Control\LSA\pku2u\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Application\ -Value Name: AllowOnlineID +Value Name: MaxSize Type: REG_DWORD -Value: 0x00000000 (0) +Value: 0x00008000 (32768) (or greater) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000341-GPOS-00132 <GroupDescription></GroupDescription> - - WN19-SO-000310 - Windows Server 2019 LAN Manager authentication level must be configured 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 standalone 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></IAControls> + + WN19-CC-000280 + Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103267 + V-93179 + CCI-001849 + Configure 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 write events directly to an audit server, 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: \SYSTEM\CurrentControlSet\Control\Lsa\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\ -Value Name: LmCompatibilityLevel +Value Name: MaxSize -Value Type: REG_DWORD -Value: 0x00000005 (5) +Type: REG_DWORD +Value: 0x00030000 (196608) (or greater) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000341-GPOS-00132 <GroupDescription></GroupDescription> - - WN19-SO-000320 - Windows Server 2019 must be configured to at least negotiate signing for LDAP client signing. - <VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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> + + WN19-CC-000290 + Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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. - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103269 + V-93181 + CCI-001849 + Configure 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 write events directly to an audit server, 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: \SYSTEM\CurrentControlSet\Services\LDAP\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\ -Value Name: LDAPClientIntegrity +Value Name: MaxSize -Value Type: REG_DWORD -Value: 0x00000001 (1) +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000342-GPOS-00133 <GroupDescription></GroupDescription> - - WN19-SO-000330 - Windows Server 2019 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption. - <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> + + WN19-AU-000010 + Windows Server 2019 audit records must be backed up to a different system or media than the system being audited. + <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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). - - - - 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\Lsa\MSV1_0\ - -Value Name: NTLMMinClientSec + V-93183 + SV-103271 + CCI-001851 + Establish and implement a process for backing up log data to another system or media other than the system being audited. + + + + Determine if a process to back up log data to a different system or media than the system being audited has been implemented. -Value Type: REG_DWORD -Value: 0x20080000 (537395200) +If it has not, this is a finding. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000355-GPOS-00143 <GroupDescription></GroupDescription> - - WN19-SO-000340 - Windows Server 2019 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption. - <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> + + WN19-00-000440 + The Windows Server 2019 time service must synchronize with an appropriate DoD time source. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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). - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93187 + SV-103275 + CCI-001891 + Configure the system to synchronize time with an appropriate DoD time source. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ +Domain-joined systems use NT5DS to synchronize time from other systems in the domain by default. -Value Name: NTLMMinServerSec +If 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 appropriate DoD time server. -Value Type: REG_DWORD -Value: 0x20080000 (537395200) +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. + + + + Review the Windows time service configuration. + +Open an elevated "Command Prompt" (run as administrator). + +Enter "W32tm /query /configuration". + +Domain-joined systems (excluding the domain controller with the PDC emulator role): + +If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. + +Other systems: + +If systems are configured with a "Type" of "NTP", including standalone systems and the domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. + +To determine the domain controller with the PDC Emulator role: + +Open "PowerShell". + +Enter "Get-ADDomain | FT PDCEmulator". - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000362-GPOS-00149 <GroupDescription></GroupDescription> - - WN19-SO-000370 - Windows Server 2019 default permissions of global system objects must be strengthened. - <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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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> + + WN19-CC-000420 + Windows Server 2019 must prevent users 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure 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". - - - + V-93199 + SV-103287 + CCI-001812 + Configure 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 -Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: ProtectionMode +Value Name: EnableUserControl -Value Type: REG_DWORD -Value: 0x00000001 (1) +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000362-GPOS-00149 <GroupDescription></GroupDescription> - - WN19-UC-000010 - Windows Server 2019 must preserve zone information when saving attachments. - <VulnDiscussion>Attachments from outside sources may contain malicious code. 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> + + WN19-CC-000430 + Windows Server 2019 must disable the Windows Installer Always install with elevated privileges option. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - The default behavior is for Windows to mark file attachments with their zone information. - -If this needs to be corrected, configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager >> "Do not preserve zone information in file attachments" to "Not Configured" or "Disabled". - - - - The default behavior is for Windows to mark file attachments with their zone information. - -If the registry Value Name below does not exist, this is not a finding. - -If it exists and is configured with a value of "2", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. + V-93201 + SV-103289 + CCI-001812 + Configure 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_CURRENT_USER -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: SaveZoneInformation +Value Name: AlwaysInstallElevated -Value Type: REG_DWORD -Value: 0x00000002 (2) (or if the Value Name does not exist) +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000363-GPOS-00150 <GroupDescription></GroupDescription> - - WN19-EP-000010 - Windows Server 2019 Exploit Protection system-level mitigation, Data Execution Prevention (DEP), must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Data Execution Prevention (DEP)", are enabled by default at the system level. DEP prevents code from being run from data-only memory pages. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000220 + Windows Server 2019 system files must be monitored for unauthorized changes. + <VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure Exploit Protection system-level mitigation, "Data Execution Prevention (DEP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Data Execution Prevention (DEP)" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn DEP on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <DEP Enable="true"></DEP> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. - -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -System". - -If the status of "DEP: Enable" is "OFF", this is a finding. + V-93203 + SV-103291 + CCI-001744 + Monitor the system for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools. + + + + Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. -Values that would not be a finding include: +If system files are not monitored for unauthorized changes, this is a finding. -ON -NOTSET (Default configuration) +A properly configured and approved DoD HBSS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000368-GPOS-00154 <GroupDescription></GroupDescription> - - WN19-EP-000030 - Windows Server 2019 Exploit Protection system-level mitigation, Control flow guard (CFG), must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Control flow guard (CFG)", are enabled by default at the system level. CFG ensures flow integrity for indirect calls. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000210 + Windows Server 2019 Autoplay 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 media is inserted into 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure Exploit Protection system-level mitigation, "Control flow guard (CFG)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Control flow guard (CFG)" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn CFG on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <ControlFlowGuard Enable="true"></ControlFlowGuard> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. - -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -System". + V-93373 + SV-103459 + CCI-001764 + Configure 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: -If the status of "CFG: Enable" is "OFF", this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -Values that would not be a finding include: +Value Name: NoAutoplayfornonVolume -ON -NOTSET (Default configuration) +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000368-GPOS-00154 <GroupDescription></GroupDescription> - - WN19-EP-000040 - Windows Server 2019 Exploit Protection system-level mitigation, Validate exception chains (SEHOP), must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate exception chains (SEHOP)", are enabled by default at the system level. SEHOP (structured exception handling overwrite protection) ensures the integrity of an exception chain during exception dispatch. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000220 + Windows Server 2019 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure Exploit Protection system-level mitigation, "Validate exception chains (SEHOP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Validate exception chains (SEHOP)" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn SEHOP on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <SEHOP Enable="true"></SEHOP> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. + V-93375 + SV-103461 + CCI-001764 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Set the default behavior for AutoRun" to "Enabled" with "Do not execute any autorun commands" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ -Run "Windows PowerShell" with elevated privileges (run as administrator). +Value Name: NoAutorun -Enter "Get-ProcessMitigation -System". +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000368-GPOS-00154 + <GroupDescription></GroupDescription> + + WN19-CC-000230 + Windows Server 2019 AutoPlay 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 media is inserted into 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. Enabling this policy disables 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93377 + SV-103463 + CCI-001764 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Turn off AutoPlay" to "Enabled" with "All Drives" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If the status of "SEHOP: Enable" is "OFF", this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\ -Values that would not be a finding include: +Value Name: NoDriveTypeAutoRun -ON -NOTSET (Default configuration) +Type: REG_DWORD +Value: 0x000000ff (255) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000370-GPOS-00155 <GroupDescription></GroupDescription> - - WN19-EP-000050 - Windows Server 2019 Exploit Protection system-level mitigation, Validate heap integrity, must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate heap integrity", are enabled by default at the system level. "Validate heap integrity" terminates a process when heap corruption is detected. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000080 + Windows Server 2019 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. + <VulnDiscussion>Using a whitelist provides a configuration management method to allow 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure Exploit Protection system-level mitigation, "Validate heap integrity" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. + V-93379 + SV-103465 + CCI-001774 + Configure an application whitelisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. -Open "Windows Defender Security Center". +Configuration of whitelisting applications will vary by the program. AppLocker is a whitelisting application built into Windows Server. -Select "App & browser control". +If AppLocker is used, it is configured through group policy in Computer Configuration >> Windows Settings >> Security Settings >> Application Control Policies >> AppLocker. -Select "Exploit protection settings". +Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: -Under "System settings", configure "Validate heap integrity" to "On by default" or "Use default (<On>)". +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm + + + + This is applicable to unclassified systems. For other systems, this is NA. -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Validate heap integrity on (other system level EP requirements can be combined under <SystemConfig>): +Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. -<SystemConfig> - <Heap TerminateOnError="true"></Heap> -</SystemConfig> +If an application whitelisting program is not in use on the system, this is a finding. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. +Configuration of whitelisting applications will vary by the program. -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". +AppLocker is a whitelisting application built into Windows Server. A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules. -Run "Windows PowerShell" with elevated privileges (run as administrator). +If AppLocker is used, perform the following to view the configuration of AppLocker: -Enter "Get-ProcessMitigation -System". +Open "PowerShell". -If the status of "Heap: TerminateOnError" is "OFF", this is a finding. +If the AppLocker PowerShell module has not been imported previously, execute the following first: -Values that would not be a finding include: +Import-Module AppLocker -ON -NOTSET (Default configuration) +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" at the following link: + +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000373-GPOS-00157 <GroupDescription></GroupDescription> - - WN19-EP-000060 - Windows Server 2019 Exploit Protection mitigations must be configured for Acrobat.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000340 + Windows Server 2019 must not save passwords 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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for Acrobat.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name Acrobat.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON + V-93425 + SV-103511 + CCI-002038 + Configure 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: -ASLR: -BottomUp: ON -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: DisablePasswordSaving -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000373-GPOS-00157 <GroupDescription></GroupDescription> - - WN19-EP-000070 - Windows Server 2019 Exploit Protection mitigations must be configured for AcroRd32.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000360 + Windows Server 2019 Remote 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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for AcroRd32.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON + V-93427 + SV-103513 + CCI-002038 + Configure 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: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Name: fPromptForPassword -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000373-GPOS-00157 + <GroupDescription></GroupDescription> + + WN19-CC-000520 + Windows Server 2019 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. -This is applicable to unclassified systems, for other systems this is NA. +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103515 + V-93429 + CCI-002038 + Configure 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: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -Enter "Get-ProcessMitigation -Name AcroRd32.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Value Name: DisableRunAs -If the following mitigations do not have a status of "ON", this is a finding: +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000373-GPOS-00157 + <GroupDescription></GroupDescription> + + WN19-SO-000380 + Windows Server 2019 User 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. -DEP: -Enable: ON +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103517 + V-93431 + CCI-002038 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -ASLR: -BottomUp: ON -ForceRelocateImages: ON +If the following registry value does not exist or is not configured as specified, this is a finding: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Name: FilterAdministratorToken + +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000373-GPOS-00157 <GroupDescription></GroupDescription> - - WN19-EP-000080 - Windows Server 2019 Exploit Protection mitigations must be configured for chrome.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000410 + Windows Server 2019 User Account Control must automatically deny standard user requests for elevation. + <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for chrome.exe: + V-93433 + SV-103519 + CCI-002038 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -DEP: -Enable: ON +If the following registry value does not exist or is not configured as specified, this is a finding: -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Value Name: ConsentPromptBehaviorUser -This is applicable to unclassified systems, for other systems this is NA. +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000373-GPOS-00157 + <GroupDescription></GroupDescription> + + WN19-SO-000440 + Windows Server 2019 User 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93435 + SV-103521 + CCI-002038 + Configure 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". + + + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -Enter "Get-ProcessMitigation -Name chrome.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +If the following registry value does not exist or is not configured as specified, this is a finding: -If the following mitigations do not have a status of "ON", this is a finding: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -DEP: -Enable: ON +Value Name: EnableLUA -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000379-GPOS-00164 <GroupDescription></GroupDescription> - - WN19-EP-000090 - Windows Server 2019 Exploit Protection mitigations must be configured for EXCEL.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-MS-000040 + Windows Server 2019 must restrict unauthenticated Remote Procedure Call (RPC) clients from connecting to the RPC server on domain-joined member servers and standalone systems. + <VulnDiscussion>Unauthenticated RPC clients may allow anonymous access to sensitive information. 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for EXCEL.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name EXCEL.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: + V-93453 + SV-103539 + CCI-001967 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Remote Procedure Call >> "Restrict Unauthenticated RPC clients" to "Enabled" with "Authenticated" selected. + + + + This applies to member servers and standalone systems, it is NA for domain controllers. -DEP: -Enable: ON +If the following registry value does not exist or is not configured as specified, this is a finding: -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Rpc\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: RestrictRemoteClients -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000379-GPOS-00164 <GroupDescription></GroupDescription> - - WN19-EP-000100 - Windows Server 2019 Exploit Protection mitigations must be configured for firefox.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000090 + Windows Server 2019 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 the 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for firefox.exe: + V-93455 + SV-103541 + CCI-001967 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain member: Disable machine account password changes" to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -DEP: -Enable: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -ASLR: -BottomUp: ON -ForceRelocateImages: ON +Value Name: DisablePasswordChange -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000393-GPOS-00173 + <GroupDescription></GroupDescription> + + WN19-CC-000480 + Windows Server 2019 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. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103585 + V-93499 + CCI-002890 + CCI-003123 + Configure 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: -This is applicable to unclassified systems, for other systems this is NA. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -Run "Windows PowerShell" with elevated privileges (run as administrator). +Value Name: AllowUnencryptedTraffic -Enter "Get-ProcessMitigation -Name firefox.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Type: REG_DWORD +Value: 0x00000000 (0) + + + + + SRG-OS-000393-GPOS-00173 + <GroupDescription></GroupDescription> + + WN19-CC-000510 + Windows Server 2019 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. -If the following mitigations do not have a status of "ON", this is a finding: +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103587 + V-93501 + CCI-002890 + CCI-003123 + Configure 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: -DEP: -Enable: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -ASLR: -BottomUp: ON -ForceRelocateImages: ON +Value Name: AllowUnencryptedTraffic -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000420-GPOS-00186 <GroupDescription></GroupDescription> - - WN19-EP-000110 - Windows Server 2019 Exploit Protection mitigations must be configured for FLTLDR.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000060 + Windows Server 2019 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 server's 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for FLTLDR.EXE: - -DEP: -Enable: ON + SV-103627 + V-93541 + CCI-002385 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" to "Enabled". -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Child Process: -DisallowChildProcessCreation: ON +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netbt\Parameters\ -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Value Name: NoNameReleaseOnDemand -This is applicable to unclassified systems, for other systems this is NA. +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000060 + Windows Server 2019 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled. + <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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93547 + SV-103633 + CCI-002421 + CCI-002418 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Enter "Get-ProcessMitigation -Name FLTLDR.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -If the following mitigations do not have a status of "ON", this is a finding: +Value Name: RequireSignOrSeal -DEP: -Enable: ON +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000070 + Windows Server 2019 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to enabled. + <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. -ImageLoad: -BlockRemoteImageLoads: ON +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93549 + SV-103635 + CCI-002418 + CCI-002421 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Child Process: -DisallowChildProcessCreation: ON +Value Name: SealSecureChannel -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000423-GPOS-00187 <GroupDescription></GroupDescription> - - WN19-EP-000120 - Windows Server 2019 Exploit Protection mitigations must be configured for GROOVE.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000080 + Windows Server 2019 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled. + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for GROOVE.EXE: - -DEP: -Enable: ON + V-93551 + SV-103637 + CCI-002421 + CCI-002418 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -ImageLoad: -BlockRemoteImageLoads: ON +Value Name: SignSecureChannel -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000110 + Windows Server 2019 must be configured to require a strong session key. + <VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. -Child Process: -DisallowChildProcessCreation: ON +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103639 + V-93553 + CCI-002418 + CCI-002421 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Value Name: RequireStrongKey -This is applicable to unclassified systems, for other systems this is NA. +Value Type: REG_DWORD +Value: 0x00000001 (1) -Run "Windows PowerShell" with elevated privileges (run as administrator). +This setting may prevent a system from being joined to a domain if not configured consistently between systems. + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000160 + Windows Server 2019 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled. + <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. -Enter "Get-ProcessMitigation -Name GROOVE.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93555 + SV-103641 + CCI-002421 + CCI-002418 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network client: Digitally sign communications (always)" to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If the following mitigations do not have a status of "ON", this is a finding: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -DEP: -Enable: ON +Value Name: RequireSecuritySignature -ASLR: -ForceRelocateImages: ON +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000170 + Windows Server 2019 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled. + <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. -ImageLoad: -BlockRemoteImageLoads: ON +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93557 + SV-103643 + CCI-002418 + CCI-002421 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -Child Process: -DisallowChildProcessCreation: ON +Value Name: EnableSecuritySignature -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000423-GPOS-00187 <GroupDescription></GroupDescription> - - WN19-EP-000130 - Windows Server 2019 Exploit Protection mitigations must be configured for iexplore.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000190 + Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled. + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for iexplore.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON + SV-103645 + V-93559 + CCI-002421 + CCI-002418 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network server: Digitally sign communications (always)" to "Enabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Name: RequireSecuritySignature -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000423-GPOS-00187 + <GroupDescription></GroupDescription> + + WN19-SO-000200 + Windows Server 2019 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled. + <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. -This is applicable to unclassified systems, for other systems this is NA. +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93561 + SV-103647 + CCI-002418 + CCI-002421 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Enter "Get-ProcessMitigation -Name iexplore.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Value Name: EnableSecuritySignature -If the following mitigations do not have a status of "ON", this is a finding: +Value Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000425-GPOS-00189 + <GroupDescription></GroupDescription> + + WN19-00-000260 + Windows Server 2019 must implement protection methods such as TLS, encrypted VPNs, or IPsec if the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. + <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. -DEP: -Enable: ON +Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. -ASLR: -BottomUp: ON -ForceRelocateImages: ON +Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93543 + SV-103629 + CCI-002422 + CCI-002420 + Configure protection methods such as TLS, encrypted VPNs, or IPsec when the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. + + + + If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If protection methods have not been implemented, this is a finding. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000433-GPOS-00192 <GroupDescription></GroupDescription> - - WN19-EP-000140 - Windows Server 2019 Exploit Protection mitigations must be configured for INFOPATH.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000310 + Windows Server 2019 Explorer Data Execution Prevention must be enabled. + <VulnDiscussion>Data Execution Prevention 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for INFOPATH.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. + SV-103649 + V-93563 + CCI-002824 + The default behavior is for data execution prevention to be turned on for File Explorer. -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off Data Execution Prevention for Explorer" to "Not Configured" or "Disabled". + + + + The default behavior is for Data Execution Prevention to be turned on for File Explorer. -Enter "Get-ProcessMitigation -Name INFOPATH.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +If the registry value name below does not exist, this is not a finding. -If the following mitigations do not have a status of "ON", this is a finding: +If it exists and is configured with a value of "0", this is not a finding. -DEP: -Enable: ON +If it exists and is configured with a value of "1", this is a finding. -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: NoDataExecutionPrevention -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000433-GPOS-00193 <GroupDescription></GroupDescription> - - WN19-EP-000150 - Windows Server 2019 Exploit Protection mitigations must be configured for java.exe, javaw.exe, and javaws.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000020 + Windows Server 2019 Exploit Protection system-level mitigation, Randomize memory allocations (Bottom-Up ASLR), must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for java.exe, javaw.exe, and javaws.exe: + V-93565 + SV-103651 + CCI-002824 + Ensure Exploit Protection system-level mitigation, "Randomize memory allocations (Bottom-Up ASLR)" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. -DEP: -Enable: ON +Open "Windows Defender Security Center". -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Select "App & browser control". -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Select "Exploit protection settings". -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Under "System settings", configure "Randomize memory allocations (Bottom-Up ASLR)" to "On by default" or "Use default (<On>)". -This is applicable to unclassified systems, for other systems this is NA. +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Bottom-Up ASLR on (other system level EP requirements can be combined under <SystemConfig>): -Run "Windows PowerShell" with elevated privileges (run as administrator). +<SystemConfig> + <ASLR BottomUp="true" HighEntropy="true"></ASLR> +</SystemConfig> -Enter "Get-ProcessMitigation -Name [application name]" with each of the following substituted for [application name]: -java.exe, javaw.exe, and javaws.exe -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. -If the following mitigations do not have a status of "ON" for each, this is a finding: +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". -DEP: -Enable: ON +Run "Windows PowerShell" with elevated privileges (run as administrator). -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter "Get-ProcessMitigation -System". -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If the status of "ASLR: BottomUp" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration) - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000470-GPOS-00214 <GroupDescription></GroupDescription> - - WN19-EP-000160 - Windows Server 2019 Exploit Protection mitigations must be configured for lync.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000070 + Windows Server 2019 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for lync.exe: + SV-103241 + V-93153 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -DEP: -Enable: ON +Use the "AuditPol" tool to review the current Audit Policy configuration: -ASLR: -ForceRelocateImages: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter "AuditPol /get /category:*" -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Compare the "AuditPol" settings with the following: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +If the system does not audit the following, this is a finding. -This is applicable to unclassified systems, for other systems this is NA. +Account Logon >> Credential Validation - Success + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN19-AU-000080 + Windows Server 2019 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103243 + V-93155 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Enter "Get-ProcessMitigation -Name lync.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Use the "AuditPol" tool to review the current Audit Policy configuration: -If the following mitigations do not have a status of "ON", this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -DEP: -Enable: ON +Enter "AuditPol /get /category:*" -ASLR: -ForceRelocateImages: ON +Compare the "AuditPol" settings with the following: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Account Logon >> Credential Validation - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000470-GPOS-00214 <GroupDescription></GroupDescription> - - WN19-EP-000170 - Windows Server 2019 Exploit Protection mitigations must be configured for MSACCESS.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000170 + Windows Server 2019 must be configured to audit Logon/Logoff - Group Membership 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 Group Membership records information related to the group membership of a user's logon token.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for MSACCESS.EXE: + V-93159 + SV-103247 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Group Membership" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -DEP: -Enable: ON +Use the "AuditPol" tool to review the current Audit Policy configuration: -ASLR: -ForceRelocateImages: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter "AuditPol /get /category:*" -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Compare the "AuditPol" settings with the following: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +If the system does not audit the following, this is a finding. -This is applicable to unclassified systems, for other systems this is NA. +Logon/Logoff >> Group Membership - Success + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN19-AU-000210 + Windows Server 2019 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Special Logon records special logons that have administrative privileges and can be used to elevate processes. -Enter "Get-ProcessMitigation -Name MSACCESS.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93161 + SV-103249 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If the following mitigations do not have a status of "ON", this is a finding: +Use the "AuditPol" tool to review the current Audit Policy configuration: -DEP: -Enable: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -ASLR: -ForceRelocateImages: ON +Enter "AuditPol /get /category:*" -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Compare the "AuditPol" settings with the following: -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If the system does not audit the following, this is a finding. + +Logon/Logoff >> Special Logon - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000470-GPOS-00214 <GroupDescription></GroupDescription> - - WN19-EP-000180 - Windows Server 2019 Exploit Protection mitigations must be configured for MSPUB.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000220 + Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. + +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for MSPUB.EXE: + SV-103251 + V-93163 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -DEP: -Enable: ON +Use the "AuditPol" tool to review the current Audit Policy configuration: -ASLR: -ForceRelocateImages: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter "AuditPol /get /category:*" -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Compare the "AuditPol" settings with the following: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +If the system does not audit the following, this is a finding. -This is applicable to unclassified systems, for other systems this is NA. +Object Access >> Other Object Access Events - Success + + + + + SRG-OS-000470-GPOS-00214 + <GroupDescription></GroupDescription> + + WN19-AU-000230 + Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103253 + V-93165 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Enter "Get-ProcessMitigation -Name MSPUB.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Use the "AuditPol" tool to review the current Audit Policy configuration: -If the following mitigations do not have a status of "ON", this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -DEP: -Enable: ON +Enter "AuditPol /get /category:*" -ASLR: -ForceRelocateImages: ON +Compare the "AuditPol" settings with the following: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the system does not audit the following, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Object Access >> Other Object Access Events - Failure - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000472-GPOS-00217 <GroupDescription></GroupDescription> - - WN19-EP-000190 - Windows Server 2019 Exploit Protection mitigations must be configured for OIS.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000180 + Windows Server 2019 must be configured to audit 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. + +Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for OIS.EXE: + V-93171 + SV-103259 + CCI-000172 + CCI-000366 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -DEP: -Enable: ON +Use the "AuditPol" tool to review the current Audit Policy configuration: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Enter "AuditPol /get /category:*" -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Compare the "AuditPol" settings with the following: -This is applicable to unclassified systems, for other systems this is NA. +If the system does not audit the following, this is a finding. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Logon/Logoff >> Logoff - Success + + + + + SRG-OS-000474-GPOS-00219 + <GroupDescription></GroupDescription> + + WN19-AU-000130 + Windows Server 2019 must be configured to audit Detailed Tracking - Plug and Play 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. -Enter "Get-ProcessMitigation -Name OIS.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Plug and Play activity records events related to the successful connection of external devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93157 + SV-103245 + CCI-000172 + Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> "Audit PNP Activity" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -If the following mitigations do not have a status of "ON", this is a finding: +Use the "AuditPol" tool to review the current Audit Policy configuration: -DEP: -Enable: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter "AuditPol /get /category:*" -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Compare the "AuditPol" settings with the following: + +If the system does not audit the following, this is a finding. + +Detailed Tracking >> Plug and Play Events - Success - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000474-GPOS-00219 <GroupDescription></GroupDescription> - - WN19-EP-000200 - Windows Server 2019 Exploit Protection mitigations must be configured for OneDrive.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AU-000240 + Windows Server 2019 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. + +Removable Storage auditing under Object Access 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for OneDrive.exe: + SV-103255 + V-93167 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -DEP: -Enable: ON +Use the "AuditPol" tool to review the current Audit Policy configuration: -ASLR: -ForceRelocateImages: ON +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -ImageLoad: -BlockRemoteImageLoads: ON +Enter "AuditPol /get /category:*" -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Compare the "AuditPol" settings with the following: -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +If the system does not audit the following, this is a finding. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Object Access >> Removable Storage - Success -This is applicable to unclassified systems, for other systems this is NA. +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. + + + + + SRG-OS-000474-GPOS-00219 + <GroupDescription></GroupDescription> + + WN19-AU-000250 + Windows Server 2019 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Removable Storage auditing under Object Access 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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103257 + V-93169 + CCI-000172 + Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. -Enter "Get-ProcessMitigation -Name OneDrive.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Use the "AuditPol" tool to review the current Audit Policy configuration: -If the following mitigations do not have a status of "ON", this is a finding: +Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator"). -DEP: -Enable: ON +Enter "AuditPol /get /category:*" -ASLR: -ForceRelocateImages: ON +Compare the "AuditPol" settings with the following: -ImageLoad: -BlockRemoteImageLoads: ON +If the system does not audit the following, this is a finding. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Object Access >> Removable Storage - Failure -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. - - SRG-OS-000480-GPOS-00227 + + SRG-OS-000478-GPOS-00223 <GroupDescription></GroupDescription> - - WN19-EP-000210 - Windows Server 2019 Exploit Protection mitigations must be configured for OUTLOOK.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000360 + Windows Server 2019 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing. + <VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for OUTLOOK.EXE: - -DEP: -Enable: ON + SV-103597 + V-93511 + CCI-002450 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -ASLR: -ForceRelocateImages: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Value Name: Enabled -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Type: REG_DWORD +Value: 0x00000001 (1) -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +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; otherwise. the browser will not be able to connect to a secure site. + + + + + SRG-OS-000479-GPOS-00224 + <GroupDescription></GroupDescription> + + WN19-AU-000020 + Windows Server 2019 must, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly. + <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103273 + V-93185 + CCI-001851 + Configure the system to, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly. + + + + Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. -This is applicable to unclassified systems, for other systems this is NA. +If they are not, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-00-000010 + Windows Server 2019 users with Administrative privileges 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93369 + SV-103457 + CCI-000366 + Ensure each user with administrative privileges 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. -Run "Windows PowerShell" with elevated privileges (run as administrator). +If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-00-000030 + Windows Server 2019 administrative accounts must 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 account. -Enter "Get-ProcessMitigation -Name OUTLOOK.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to not access the Internet or use applications such as email. -If the following mitigations do not have a status of "ON", this is a finding: +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. -DEP: -Enable: ON +Whitelisting can be used to enforce the policy to ensure compliance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93205 + SV-103293 + CCI-000366 + Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. Ensure the policy is enforced. -ASLR: -ForceRelocateImages: ON +The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. + + + + Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If it does not, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-EP-000220 - Windows Server 2019 Exploit Protection mitigations must be configured for plugin-container.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000040 + Windows Server 2019 members 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for plugin-container.exe: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name plugin-container.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON + V-93207 + SV-103295 + CCI-000366 + Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions. + + + + If no accounts are members of the Backup Operators group, this is NA. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding. - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-EP-000230 - Windows Server 2019 Exploit Protection mitigations must be configured for POWERPNT.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000060 + Windows Server 2019 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization. + <VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for POWERPNT.EXE: + SV-103297 + V-93209 + CCI-000366 + Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization. -DEP: -Enable: ON +It is recommended that system-managed service accounts be used whenever possible. + + + + Determine if manually managed application/service accounts exist. If none exist, this is NA. -ASLR: -ForceRelocateImages: ON +If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Identify manually managed application/service accounts. -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +To determine the date a password was last changed: -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Domain controllers: -This is applicable to unclassified systems, for other systems this is NA. +Open "PowerShell". -Run "Windows PowerShell" with elevated privileges (run as administrator). +Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. -Enter "Get-ProcessMitigation -Name POWERPNT.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +If the "PasswordLastSet" date is more than one year old, this is a finding. -If the following mitigations do not have a status of "ON", this is a finding: -DEP: -Enable: ON +Member servers and standalone systems: -ASLR: -ForceRelocateImages: ON +Open "Command Prompt". -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If the "Password Last Set" date is more than one year old, this is a finding. - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-EP-000240 - Windows Server 2019 Exploit Protection mitigations must be configured for PPTVIEW.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000090 + Windows Server 2019 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use. + <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for PPTVIEW.EXE: - -DEP: -Enable: ON + V-93213 + SV-103301 + CCI-000366 + Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.) -ASLR: -ForceRelocateImages: ON +The TPM must be enabled in the firmware. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Run "tpm.msc" for configuration options in Windows. + + + + For standalone systems, this is NA. -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Verify the system has a TPM and it is ready for use. -This is applicable to unclassified systems, for other systems this is NA. +Run "tpm.msc". -Run "Windows PowerShell" with elevated privileges (run as administrator). +Review the sections in the center pane. -Enter "Get-ProcessMitigation -Name PPTVIEW.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". -If the following mitigations do not have a status of "ON", this is a finding: +TPM Manufacturer Information - Specific Version = 2.0 or 1.2 -DEP: -Enable: ON +If a TPM is not found or is not ready for use, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-00-000100 + Windows Server 2019 must be maintained at a supported servicing level. + <VulnDiscussion>Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103303 + V-93215 + CCI-000366 + Update the system to a Version 1809 (Build 17763.xxx) or greater. + + + + Open "Command Prompt". -ASLR: -ForceRelocateImages: ON +Enter "winver.exe". -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If the "About Windows" dialog box does not display "Microsoft Windows Server Version 1809 (Build 17763.xxx)" or greater, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Preview versions must not be used in a production environment. - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-EP-000250 - Windows Server 2019 Exploit Protection mitigations must be configured for VISIO.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000110 + Windows Server 2019 must use an anti-virus program. + <VulnDiscussion>Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for VISIO.EXE: + SV-103305 + V-93217 + CCI-000366 + If no anti-virus software is in use, install Windows Defender or third-party anti-virus. -DEP: -Enable: ON +Open "PowerShell". -ASLR: -ForceRelocateImages: ON +Enter "Install-WindowsFeature -Name Windows-Defender”. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +For third-party anti-virus, install per anti-virus instructions and disable Windows Defender. -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Open "PowerShell". -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Enter "Uninstall-WindowsFeature -Name Windows-Defender”. + + + + + Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution. -This is applicable to unclassified systems, for other systems this is NA. +If there is no anti-virus solution installed on the system, this is a finding. -Run "Windows PowerShell" with elevated privileges (run as administrator). +Verify if Windows Defender is in use or enabled: -Enter "Get-ProcessMitigation -Name VISIO.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Open "PowerShell". -If the following mitigations do not have a status of "ON", this is a finding: +Enter “get-service | where {$_.DisplayName -Like "*Defender*"} | Select Status,DisplayName” -DEP: -Enable: ON +Verify if third-party anti-virus is in use or enabled: -ASLR: -ForceRelocateImages: ON +Open "PowerShell". -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Enter "get-service | where {$_.DisplayName -Like "*mcafee*"} | Select Status,DisplayName” -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Enter "get-service | where {$_.DisplayName -Like "*symantec*"} | Select Status,DisplayName” + - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-EP-000260 - Windows Server 2019 Exploit Protection mitigations must be configured for VPREVIEW.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000120 + Windows Server 2019 must have a host-based intrusion detection or prevention system. + <VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for VPREVIEW.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). + SV-103307 + V-93219 + CCI-000366 + Install a HIDS or HIPS on each server. + + + + Determine whether there is a HIDS or HIPS on each server. -Enter "Get-ProcessMitigation -Name VPREVIEW.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. -If the following mitigations do not have a status of "ON", this is a finding: +A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. -DEP: -Enable: ON +If a HIDS is not installed on the system, this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-00-000240 + Windows Server 2019 must have software certificate installation files removed. + <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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93221 + SV-103309 + CCI-000366 + Remove any certificate installation files (*.p12 and *.pfx) found on a system. -ASLR: -ForceRelocateImages: ON +Note: This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. + + + + Search all drives for *.p12 and *.pfx files. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +If any files with these extensions exist, this is a finding. -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. 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. - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-EP-000270 - Windows Server 2019 Exploit Protection mitigations must be configured for WINWORD.EXE. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000420 + Windows Server 2019 FTP servers must be configured to prevent anonymous logons. + <VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. + +Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for WINWORD.EXE: + V-93223 + SV-103311 + CCI-000366 + Configure the FTP service to prevent anonymous logons. -DEP: -Enable: ON +Open "Internet Information Services (IIS) Manager". -ASLR: -ForceRelocateImages: ON +Select the server. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Double-click "FTP Authentication". -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Select "Anonymous Authentication". -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Select "Disabled" under "Actions". + + + + If FTP is not installed on the system, this is NA. -This is applicable to unclassified systems, for other systems this is NA. +Open "Internet Information Services (IIS) Manager". -Run "Windows PowerShell" with elevated privileges (run as administrator). +Select the server. -Enter "Get-ProcessMitigation -Name WINWORD.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Double-click "FTP Authentication". -If the following mitigations do not have a status of "ON", this is a finding: +If the "Anonymous Authentication" status is "Enabled", this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-00-000430 + Windows Server 2019 FTP servers must be configured to prevent access to the system drive. + <VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93225 + SV-103313 + CCI-000366 + Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system. + + + + If FTP is not installed on the system, this is NA. -DEP: -Enable: ON +Open "Internet Information Services (IIS) Manager". -ASLR: -ForceRelocateImages: ON +Select "Sites" under the server name. -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +For any sites with a Binding that lists FTP, right-click the site and select "Explore". -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If the site is not defined to a specific folder for shared FTP resources, this is a finding. + +If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding. - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-EP-000280 - Windows Server 2019 Exploit Protection mitigations must be configured for wmplayer.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-00-000460 + Windows Server 2019 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS. + <VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for wmplayer.exe: - -DEP: -Enable: ON - -Payload: -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + V-93229 + SV-103317 + CCI-000366 + Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode. + + + + Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must run in "UEFI" mode. -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". -This is applicable to unclassified systems, for other systems this is NA. +Run "System Information". -Run "Windows PowerShell" with elevated privileges (run as administrator). +Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-00-000470 + Windows Server 2019 must have Secure Boot enabled. + <VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103319 + V-93231 + CCI-000366 + Enable Secure Boot in the system firmware. + + + + Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must have Secure Boot enabled. -Enter "Get-ProcessMitigation -Name wmplayer.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Run "System Information". -If the following mitigations do not have a status of "ON", this is a finding: +Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. -DEP: -Enable: ON +On server core installations, run the following PowerShell command: -Payload: -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Confirm-SecureBootUEFI -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +If a value of "True" is not returned, this is a finding. - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-EP-000290 - Windows Server 2019 Exploit Protection mitigations must be configured for wordpad.exe. - <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000030 + Windows Server 2019 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following mitigations are turned "ON" for wordpad.exe: + SV-103321 + V-93233 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. -DEP: -Enable: ON +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. +Value Name: DisableIPSourceRouting -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - If the referenced application is not installed on the system, this is NA. +Type: REG_DWORD +Value: 0x00000002 (2) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-CC-000040 + Windows Server 2019 source routing must be configured to the highest protection level to prevent Internet Protocol (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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103323 + V-93235 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. -This is applicable to unclassified systems, for other systems this is NA. +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: -Run "Windows PowerShell" with elevated privileges (run as administrator). +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ -Enter "Get-ProcessMitigation -Name wordpad.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) +Value Name: DisableIPSourceRouting -If the following mitigations do not have a status of "ON", this is a finding: +Value Type: REG_DWORD +Value: 0x00000002 (2) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-CC-000050 + Windows Server 2019 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 the 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103325 + V-93237 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" to "Disabled". -DEP: -Enable: ON +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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: -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. +Value Name: EnableICMPRedirect + +Value Type: REG_DWORD +Value: 0x00000000 (0) - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000010 - Windows Server 2019 users with Administrative privileges 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> + + WN19-CC-000070 + Windows Server 2019 insecure logons to an SMB server must be disabled. + <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure each user with administrative privileges 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. + SV-103327 + V-93239 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Lanman Workstation >> "Enable insecure guest logons" to "Disabled". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation\ + +Value Name: AllowInsecureGuestAuth + +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000368-GPOS-00154 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000210 - Windows Server 2019 Autoplay 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 media is inserted into 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></IAControls> + + WN19-CC-000080 + Windows Server 2019 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares. + <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001764 - Configure 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: + SV-103329 + V-93241 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Network Provider >> "Hardened UNC Paths" to "Enabled" with at least the following configured in "Hardened UNC Paths" (click the "Show" button to display): + +Value Name: \\*\SYSVOL +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Value Name: \\*\NETLOGON +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + + + + This requirement is applicable to domain-joined systems. For standalone systems, 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\Windows\Explorer\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ -Value Name: NoAutoplayfornonVolume +Value Name: \\*\NETLOGON +Value Type: REG_SZ +Value: RequireMutualAuthentication=1, RequireIntegrity=1 -Type: REG_DWORD -Value: 0x00000001 (1) +Value Name: \\*\SYSVOL +Value Type: REG_SZ +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Additional entries would not be a finding. - - SRG-OS-000368-GPOS-00154 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000220 - Windows Server 2019 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></IAControls> + + WN19-CC-000100 + Windows Server 2019 must be configured to enable Remote host allows delegation of non-exportable credentials. + <VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001764 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Set the default behavior for AutoRun" to "Enabled" with "Do not execute any autorun commands" selected. - - - + V-93243 + SV-103331 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Remote host allows delegation of non-exportable 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 -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ -Value Name: NoAutorun +Value Name: AllowProtectedCreds Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000368-GPOS-00154 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000230 - Windows Server 2019 AutoPlay 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 media is inserted into 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. Enabling this policy disables 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> + + WN19-CC-000110 + Windows Server 2019 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection. + <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001764 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Turn off AutoPlay" to "Enabled" with "All Drives" selected. - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93245 + SV-103333 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Secure Boot" or "Secure Boot and DMA Protection" selected. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\ +A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: -Value Name: NoDriveTypeAutoRun +https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard + + + + For standalone systems, this is NA. -Type: REG_DWORD -Value: 0x000000ff (255) - - - - - SRG-OS-000370-GPOS-00155 - <GroupDescription></GroupDescription> - - WN19-00-000080 - Windows Server 2019 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. - <VulnDiscussion>Using a whitelist provides a configuration management method to allow the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. -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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001774 - Configure an application whitelisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. +Open "PowerShell" with elevated privileges (run as administrator). -Configuration of whitelisting applications will vary by the program. AppLocker is a whitelisting application built into Windows Server. +Enter the following: -If AppLocker is used, it is configured through group policy in Computer Configuration >> Windows Settings >> Security Settings >> Application Control Policies >> AppLocker. +"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" -Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: +If "RequiredSecurityProperties" does not include a value of "2" indicating "Secure Boot" (e.g., "{1, 2}"), this is a finding. -https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm - - - - This is applicable to unclassified systems. For other systems, this is NA. +If "Secure Boot and DMA Protection" is configured, "3" will also be displayed in the results (e.g., "{1, 2, 3}"). -Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. +If "VirtualizationBasedSecurityStatus" is not a value of "2" indicating "Running", this is a finding. -If an application whitelisting program is not in use on the system, this is a finding. +Alternately: -Configuration of whitelisting applications will vary by the program. +Run "System Information". -AppLocker is a whitelisting application built into Windows Server. A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules. +Under "System Summary", verify the following: -If AppLocker is used, perform the following to view the configuration of AppLocker: +If "Device Guard Virtualization based security" does not display "Running", this is a finding. -Open "PowerShell". +If "Device Guard Required Security Properties" does not display "Base Virtualization Support, Secure Boot", this is a finding. -If the AppLocker PowerShell module has not been imported previously, execute the following first: +If "Secure Boot and DMA Protection" is configured, "DMA Protection" will also be displayed (e.g., "Base Virtualization Support, Secure Boot, DMA Protection"). -Import-Module AppLocker +The policy settings referenced in the Fix section will configure the following registry values. However, due to hardware requirements, the registry values alone do not ensure proper function. -Execute the following command, substituting [c:\temp\file.xml] with a location and file name appropriate for the system: +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ -Get-AppLockerPolicy -Effective -XML > c:\temp\file.xml +Value Name: EnableVirtualizationBasedSecurity +Value Type: REG_DWORD +Value: 0x00000001 (1) -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. +Value Name: RequirePlatformSecurityFeatures +Value Type: REG_DWORD +Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) -Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: +A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: -https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm +https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000270 - Windows Server 2019 must have the roles and features required by the system documented. - <VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000130 + Windows Server 2019 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad. + <VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Document the roles and features required for the system to operate. Uninstall any that are not required. - - - - Required roles and features will vary based on the function of the individual system. + V-93249 + SV-103337 + CCI-000366 + The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). -Roles and features specifically required to be disabled per the STIG are identified in separate requirements. +If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> "Boot-Start Driver Initialization Policy" to "Not Configured" or "Enabled" with any option other than "All" selected. + + + + The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). -If the organization has not documented the roles and features required for the system(s), this is a finding. +If the registry value name below does not exist, this is not a finding. -The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State". +If it exists and is configured with a value of "0x00000007 (7)", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ + +Value Name: DriverLoadPolicy + +Value Type: REG_DWORD +Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) + +Possible values for this setting are: +8 - Good only +1 - Good and unknown +3 - Good, unknown and bad but critical +7 - All (which includes "bad" and would be a finding) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000320 - Windows Server 2019 must not have the Fax Server role installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + WN19-CC-000140 + Windows Server 2019 group policy objects must be reprocessed even if they have not changed. + <VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "Fax Server" role. - -Start "Server Manager". - -Select the server with the role. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "Fax Server" on the "Roles" page. - -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". + V-93251 + SV-103339 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Group Policy >> "Configure registry policy processing" to "Enabled" with the option "Process even if the Group Policy objects have not changed" selected. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Enter "Get-WindowsFeature | Where Name -eq Fax". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ -If "Installed State" is "Installed", this is a finding. +Value Name: NoGPOListChanges -An Installed State of "Available" or "Removed" is not a finding. +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000340 - Windows Server 2019 must not have the Peer Name Resolution Protocol installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + WN19-CC-000180 + Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (on battery). + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "Peer Name Resolution Protocol" feature. - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. + V-93253 + SV-103341 + CCI-000366 + Configure 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: -Select the appropriate server on the "Server Selection" page and click "Next". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ -Deselect "Peer Name Resolution Protocol" on the "Features" page. +Value Name: DCSettingIndex -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +Type: REG_DWORD +Value: 0x00000001 (1) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-CC-000190 + Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (plugged in). + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93255 + SV-103343 + CCI-000366 + Configure 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: -Enter "Get-WindowsFeature | Where Name -eq PNRP". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ -If "Installed State" is "Installed", this is a finding. +Value Name: ACSettingIndex -An Installed State of "Available" or "Removed" is not a finding. +Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000350 - Windows Server 2019 must not have Simple TCP/IP Services installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + WN19-CC-000250 + Windows Server 2019 Telemetry must be configured to Security or Basic. + <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "Simple TCP/IP Services" feature. - -Start "Server Manager". + SV-103345 + V-93257 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Data Collection and Preview Builds>> "Allow Telemetry" to "Enabled" with "0 - Security [Enterprise Only]" or "1 - Basic" selected in "Options". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Select the server with the feature. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DataCollection\ -Scroll down to "ROLES AND FEATURES" in the right pane. +Value Name: AllowTelemetry -Select "Remove Roles and Features" from the drop-down "TASKS" list. +Type: REG_DWORD +Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic) + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-CC-000260 + Windows Server 2019 Windows Update must not obtain updates from other PCs on the Internet. + <VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103347 + V-93259 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Delivery Optimization >> "Download Mode" to "Enabled" with any option except "Internet" selected. -Select the appropriate server on the "Server Selection" page and click "Next". +Acceptable selections include: -Deselect "Simple TCP/IP Services" on the "Features" page. +Bypass (100) +Group (2) +HTTP only (0) +LAN (1) +Simple (99) + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\ -Enter "Get-WindowsFeature | Where Name -eq Simple-TCPIP". +Value Name: DODownloadMode -If "Installed State" is "Installed", this is a finding. +Value Type: REG_DWORD +Value: 0x00000000 (0) - No peering (HTTP Only) +0x00000001 (1) - Peers on same NAT only (LAN) +0x00000002 (2) - Local Network / Private group peering (Group) +0x00000063 (99) - Simple download mode, no peering (Simple) +0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) -An Installed State of "Available" or "Removed" is not a finding. +A value of 0x00000003 (3), Internet, is a finding. - - SRG-OS-000095-GPOS-00049 - <GroupDescription></GroupDescription> - - WN19-00-000370 - Windows Server 2019 must not have the TFTP Client installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-CC-000320 + Windows Server 2019 Turning 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "TFTP Client" feature. - -Start "Server Manager". - -Select the server with the feature. + V-93261 + SV-103349 + CCI-000366 + The default behavior is for File Explorer heap termination on corruption to be disabled. -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off heap termination on corruption" to "Not Configured" or "Disabled". + + + + The default behavior is for File Explorer heap termination on corruption to be enabled. -Select the appropriate server on the "Server Selection" page and click "Next". +If the registry Value Name below does not exist, this is not a finding. -Deselect "TFTP Client" on the "Features" page. +If it exists and is configured with a value of "0", this is not a finding. -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +If it exists and is configured with a value of "1", this is a finding. -Enter "Get-WindowsFeature | Where Name -eq TFTP-Client". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -If "Installed State" is "Installed", this is a finding. +Value Name: NoHeapTerminationOnCorruption -An Installed State of "Available" or "Removed" is not a finding. +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000380 - Windows Server 2019 must not the Server Message Block (SMB) v1 protocol installed. - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000330 + Windows Server 2019 File Explorer shell protocol must run in protected mode. + <VulnDiscussion>The shell protocol will limit the set of folders that 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the SMBv1 protocol. - -Open "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Uninstall-WindowsFeature -Name FS-SMB1 -Restart". -(Omit the Restart parameter if an immediate restart of the system cannot be done.) - -Alternately: - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. + V-93263 + SV-103351 + CCI-000366 + The default behavior is for shell protected mode to be turned on for File Explorer. -Select the appropriate server on the "Server Selection" page and click "Next". +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off shell protocol protected mode" to "Not Configured" or "Disabled". + + + + The default behavior is for shell protected mode to be turned on for File Explorer. -Deselect "SMB 1.0/CIFS File Sharing Support" on the "Features" page. +If the registry value name below does not exist, this is not a finding. -Click "Next" and "Remove" as prompted. - - - - Different methods are available to disable SMBv1 on Windows Server 2019. This is the preferred method, however if WN19-00-000390 and WN19-00-000400 are configured, this is NA. +If it exists and is configured with a value of "0", this is not a finding. -Open "Windows PowerShell" with elevated privileges (run as administrator). +If it exists and is configured with a value of "1", this is a finding. -Enter "Get-WindowsFeature -Name FS-SMB1". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ -If "Installed State" is "Installed", this is a finding. +Value Name: PreXPSP2ShellProtocolBehavior -An Installed State of "Available" or "Removed" is not a finding. +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000390 - Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server. - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000390 + Windows Server 2019 must prevent attachments 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 Server" to "Disabled". - -The system must be restarted for the change to take effect. - -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. - - - - Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. - -If the following registry value does not exist or is not configured as specified, this is a finding: + V-93265 + SV-103353 + CCI-000366 + Configure 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 -Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ -Value Name: SMB1 +Value Name: DisableEnclosureDownload Type: REG_DWORD -Value: 0x00000000 (0) +Value: 0x00000001 (1) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000400 - Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client. - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000440 + Windows Server 2019 users must be notified if a web-based program attempts to install software. + <VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 client driver" to "Enabled" with "Disable driver (recommended)" selected for "Configure MrxSmb10 driver". + SV-103355 + V-93267 + CCI-000366 + The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. -The system must be restarted for the changes to take effect. +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> "Prevent Internet Explorer security prompt for Windows Installer scripts" to "Not Configured" or "Disabled". + + + + The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. -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. - - - - Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. +If the registry value name below does not exist, this is not a finding. -If the following registry value is not configured as specified, this is a finding: +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: Start +Value Name: SafeForScripting -Type: REG_DWORD -Value: 0x00000004 (4) +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000410 - Windows Server 2019 must not have Windows PowerShell 2.0 installed. - <VulnDiscussion>Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000010 + Windows Server 2019 Exploit Protection system-level mitigation, Data Execution Prevention (DEP), must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Data Execution Prevention (DEP)", are enabled by default at the system level. DEP prevents code from being run from data-only memory pages. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Uninstall the "Windows PowerShell 2.0 Engine". + V-93313 + SV-103401 + CCI-000366 + Ensure Exploit Protection system-level mitigation, "Data Execution Prevention (DEP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. -Start "Server Manager". +Open "Windows Defender Security Center". -Select the server with the feature. +Select "App & browser control". -Scroll down to "ROLES AND FEATURES" in the right pane. +Select "Exploit protection settings". -Select "Remove Roles and Features" from the drop-down "TASKS" list. +Under "System settings", configure "Data Execution Prevention (DEP)" to "On by default" or "Use default (<On>)". -Select the appropriate server on the "Server Selection" page and click "Next". +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn DEP on (other system level EP requirements can be combined under <SystemConfig>): -Deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell" on the "Features" page. +<SystemConfig> + <DEP Enable="true"></DEP> +</SystemConfig> -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. -Enter "Get-WindowsFeature | Where Name -eq PowerShell-v2". +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". -If "Installed State" is "Installed", this is a finding. +Run "Windows PowerShell" with elevated privileges (run as administrator). -An Installed State of "Available" or "Removed" is not a finding. +Enter "Get-ProcessMitigation -System". + +If the status of "DEP: Enable" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000010 - Windows Server 2019 must prevent the display of slide shows on the lock screen. - <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> + + WN19-EP-000030 + Windows Server 2019 Exploit Protection system-level mitigation, Control flow guard (CFG), must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Control flow guard (CFG)", are enabled by default at the system level. CFG ensures flow integrity for indirect calls. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> Control Panel >> Personalization >> "Prevent enabling lock screen slide show" to "Enabled". - - - - Verify the registry value below. + V-93315 + SV-103403 + CCI-000366 + Ensure Exploit Protection system-level mitigation, "Control flow guard (CFG)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. -If it does not exist or is not configured as specified, this is a finding. +Open "Windows Defender Security Center". -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\ +Select "App & browser control". -Value Name: NoLockScreenSlideshow +Select "Exploit protection settings". -Value Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000095-GPOS-00049 - <GroupDescription></GroupDescription> - - WN19-CC-000020 - Windows Server 2019 must have WDigest Authentication 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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "WDigest Authentication (disabling may require KB2871997)" to "Disabled". +Under "System settings", configure "Control flow guard (CFG)" to "On by default" or "Use default (<On>)". -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: +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn CFG on (other system level EP requirements can be combined under <SystemConfig>): -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\ +<SystemConfig> + <ControlFlowGuard Enable="true"></ControlFlowGuard> +</SystemConfig> -Value Name: UseLogonCredential +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000095-GPOS-00049 - <GroupDescription></GroupDescription> - - WN19-CC-000150 - Windows Server 2019 downloading print driver packages over HTTP 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 will prevent uncontrolled updates to the system. +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". -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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000381 - Configure 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: +Run "Windows PowerShell" with elevated privileges (run as administrator). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ +Enter "Get-ProcessMitigation -System". -Value Name: DisableWebPnPDownload +If the status of "CFG: Enable" is "OFF", this is a finding. -Type: REG_DWORD -Value: 0x00000001 (1) +Values that would not be a finding include: + +ON +NOTSET (Default configuration) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000160 - Windows Server 2019 printing over HTTP 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 will prevent 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> + + WN19-EP-000040 + Windows Server 2019 Exploit Protection system-level mitigation, Validate exception chains (SEHOP), must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate exception chains (SEHOP)", are enabled by default at the system level. SEHOP (structured exception handling overwrite protection) ensures the integrity of an exception chain during exception dispatch. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure 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: + SV-103405 + V-93317 + CCI-000366 + Ensure Exploit Protection system-level mitigation, "Validate exception chains (SEHOP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. + +Open "Windows Defender Security Center". + +Select "App & browser control". + +Select "Exploit protection settings". + +Under "System settings", configure "Validate exception chains (SEHOP)" to "On by default" or "Use default (<On>)". + +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn SEHOP on (other system level EP requirements can be combined under <SystemConfig>): + +<SystemConfig> + <SEHOP Enable="true"></SEHOP> +</SystemConfig> + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. + +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ +Run "Windows PowerShell" with elevated privileges (run as administrator). -Value Name: DisableHTTPPrinting +Enter "Get-ProcessMitigation -System". -Type: REG_DWORD -Value: 0x00000001 (1) +If the status of "SEHOP: Enable" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000170 - Windows Server 2019 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 in to Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000050 + Windows Server 2019 Exploit Protection system-level mitigation, Validate heap integrity, must be on. + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate heap integrity", are enabled by default at the system level. "Validate heap integrity" terminates a process when heap corruption is detected. If this is turned off, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure 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. + SV-103407 + V-93319 + CCI-000366 + Ensure Exploit Protection system-level mitigation, "Validate heap integrity" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ +Open "Windows Defender Security Center". -Value Name: DontDisplayNetworkSelectionUI +Select "App & browser control". -Value Type: REG_DWORD -Value: 0x00000001 (1) +Select "Exploit protection settings". + +Under "System settings", configure "Validate heap integrity" to "On by default" or "Use default (<On>)". + +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Validate heap integrity on (other system level EP requirements can be combined under <SystemConfig>): + +<SystemConfig> + <Heap TerminateOnError="true"></Heap> +</SystemConfig> + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + This is applicable to unclassified systems, for other systems this is NA. + +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -System". + +If the status of "Heap: TerminateOnError" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration) - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000200 - Windows Server 2019 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 will prevent 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></IAControls> + + WN19-EP-000060 + Windows Server 2019 Exploit Protection mitigations must be configured for Acrobat.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure 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: + V-93321 + SV-103409 + CCI-000366 + Ensure the following mitigations are turned "ON" for Acrobat.exe: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\ +DEP: +Enable: ON -Value Name: DisableInventory +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Type: REG_DWORD -Value: 0x00000001 (1) +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name Acrobat.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000300 - Windows Server 2019 Windows Defender SmartScreen must be enabled. - <VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000070 + Windows Server 2019 Exploit Protection mitigations must be configured for AcroRd32.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Configure Windows Defender SmartScreen" to "Enabled" with either option "Warn" or "Warn and prevent bypass" selected. + V-93323 + SV-103411 + CCI-000366 + Ensure the following mitigations are turned "ON" for AcroRd32.exe: -Windows 2019 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer. - - - - This is applicable to unclassified systems; for other systems, this is NA. +DEP: +Enable: ON -If the following registry value does not exist or is not configured as specified, this is a finding: +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Value Name: EnableSmartScreen +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Value Type: REG_DWORD -Value: 0x00000001 (1) +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name AcroRd32.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000400 - Windows Server 2019 must disable Basic authentication for RSS feeds over HTTP. - <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000080 + Windows Server 2019 Exploit Protection mitigations must be configured for chrome.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. + SV-103413 + V-93325 + CCI-000366 + Ensure the following mitigations are turned "ON" for chrome.exe: -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> "Turn on Basic feed authentication over HTTP" to "Not Configured" or "Disabled". - - - - The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. +DEP: +Enable: ON -If the registry value name below does not exist, this is not a finding. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -If it exists and is configured with a value of "0", this is not a finding. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -If it exists and is configured with a value of "1", this is a finding. +This is applicable to unclassified systems, for other systems this is NA. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ +Run "Windows PowerShell" with elevated privileges (run as administrator). -Value Name: AllowBasicAuthInClear +Enter "Get-ProcessMitigation -Name chrome.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000410 - Windows Server 2019 must prevent Indexing of encrypted files. - <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></IAControls> + + WN19-EP-000090 + Windows Server 2019 Exploit Protection mitigations must be configured for EXCEL.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure 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: + SV-103415 + V-93327 + CCI-000366 + Ensure the following mitigations are turned "ON" for EXCEL.EXE: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\ +DEP: +Enable: ON -Value Name: AllowIndexingEncryptedStoresOrItems +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name EXCEL.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Value Type: REG_DWORD -Value: 0x00000000 (0) +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000095-GPOS-00049 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-MS-000030 - Windows Server 2019 local users on domain-joined member servers 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></IAControls> + + WN19-EP-000100 + Windows Server 2019 Exploit Protection mitigations must be configured for firefox.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000381 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> "Enumerate local users on domain-joined computers" to "Disabled". - - - - This applies to member servers. For domain controllers and standalone systems, this is NA. + SV-103417 + V-93329 + CCI-000366 + Ensure the following mitigations are turned "ON" for firefox.exe: -If the following registry value does not exist or is not configured as specified, this is a finding: +DEP: +Enable: ON -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Value Name: EnumerateLocalUsers +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Type: REG_DWORD -Value: 0x00000000 (0) +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name firefox.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000096-GPOS-00050 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000330 - Windows Server 2019 must not have the Microsoft FTP service installed unless required by the organization. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000110 + Windows Server 2019 Exploit Protection mitigations must be configured for FLTLDR.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000382 - Uninstall the "FTP Server" role. + V-93331 + SV-103419 + CCI-000366 + Ensure the following mitigations are turned "ON" for FLTLDR.EXE: -Start "Server Manager". +DEP: +Enable: ON -Select the server with the role. +ImageLoad: +BlockRemoteImageLoads: ON -Scroll down to "ROLES AND FEATURES" in the right pane. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select "Remove Roles and Features" from the drop-down "TASKS" list. +Child Process: +DisallowChildProcessCreation: ON -Select the appropriate server on the "Server Selection" page and click "Next". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Deselect "FTP Server" under "Web Server (IIS)" on the "Roles" page. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Click "Next" and "Remove" as prompted. - - - - If the server has the role of an FTP server, this is NA. +This is applicable to unclassified systems, for other systems this is NA. -Open "PowerShell". +Run "Windows PowerShell" with elevated privileges (run as administrator). -Enter "Get-WindowsFeature | Where Name -eq Web-Ftp-Service". +Enter "Get-ProcessMitigation -Name FLTLDR.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -If "Installed State" is "Installed", this is a finding. +If the following mitigations do not have a status of "ON", this is a finding: -An Installed State of "Available" or "Removed" is not a finding. +DEP: +Enable: ON -If the system has the role of an FTP server, this must be documented with the ISSO. +ImageLoad: +BlockRemoteImageLoads: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Child Process: +DisallowChildProcessCreation: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000096-GPOS-00050 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000360 - Windows Server 2019 must not have the Telnet Client installed. - <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> + + WN19-EP-000120 + Windows Server 2019 Exploit Protection mitigations must be configured for GROOVE.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000382 - Uninstall the "Telnet Client" feature. + SV-103421 + V-93333 + CCI-000366 + Ensure the following mitigations are turned "ON" for GROOVE.EXE: -Start "Server Manager". +DEP: +Enable: ON -Select the server with the feature. +ASLR: +ForceRelocateImages: ON -Scroll down to "ROLES AND FEATURES" in the right pane. +ImageLoad: +BlockRemoteImageLoads: ON -Select "Remove Roles and Features" from the drop-down "TASKS" list. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select the appropriate server on the "Server Selection" page and click "Next". +Child Process: +DisallowChildProcessCreation: ON -Deselect "Telnet Client" on the "Features" page. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Click "Next" and "Remove" as prompted. - - - - Open "PowerShell". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Enter "Get-WindowsFeature | Where Name -eq Telnet-Client". +This is applicable to unclassified systems, for other systems this is NA. -If "Installed State" is "Installed", this is a finding. +Run "Windows PowerShell" with elevated privileges (run as administrator). -An Installed State of "Available" or "Removed" is not a finding. - - - - - SRG-OS-000373-GPOS-00157 - <GroupDescription></GroupDescription> - - WN19-CC-000340 - Windows Server 2019 must not save passwords 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. +Enter "Get-ProcessMitigation -Name GROOVE.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-002038 - Configure 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: +If the following mitigations do not have a status of "ON", this is a finding: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ +DEP: +Enable: ON -Value Name: DisablePasswordSaving +ASLR: +ForceRelocateImages: ON -Type: REG_DWORD -Value: 0x00000001 (1) +ImageLoad: +BlockRemoteImageLoads: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Child Process: +DisallowChildProcessCreation: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000373-GPOS-00157 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000360 - Windows Server 2019 Remote 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000130 + Windows Server 2019 Exploit Protection mitigations must be configured for iexplore.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002038 - Configure 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: + SV-103423 + V-93335 + CCI-000366 + Ensure the following mitigations are turned "ON" for iexplore.exe: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ +DEP: +Enable: ON -Value Name: fPromptForPassword +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000373-GPOS-00157 - <GroupDescription></GroupDescription> - - WN19-CC-000520 - Windows Server 2019 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. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-002038 - Configure 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: +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Value Name: DisableRunAs +This is applicable to unclassified systems, for other systems this is NA. -Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000373-GPOS-00157 - <GroupDescription></GroupDescription> - - WN19-SO-000380 - Windows Server 2019 User 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. +Run "Windows PowerShell" with elevated privileges (run as administrator). -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-002038 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). +Enter "Get-ProcessMitigation -Name iexplore.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -If the following registry value does not exist or is not configured as specified, this is a finding: +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +ASLR: +BottomUp: ON +ForceRelocateImages: ON -Value Name: FilterAdministratorToken +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Value Type: REG_DWORD -Value: 0x00000001 (1) +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000373-GPOS-00157 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000410 - Windows Server 2019 User Account Control must automatically deny standard user requests for elevation. - <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000140 + Windows Server 2019 Exploit Protection mitigations must be configured for INFOPATH.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002038 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + SV-103425 + V-93337 + CCI-000366 + Ensure the following mitigations are turned "ON" for INFOPATH.EXE: -If the following registry value does not exist or is not configured as specified, this is a finding: +DEP: +Enable: ON -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +ASLR: +ForceRelocateImages: ON -Value Name: ConsentPromptBehaviorUser +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Value Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000373-GPOS-00157 - <GroupDescription></GroupDescription> - - WN19-SO-000440 - Windows Server 2019 User 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. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-002038 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -If the following registry value does not exist or is not configured as specified, this is a finding: +This is applicable to unclassified systems, for other systems this is NA. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Run "Windows PowerShell" with elevated privileges (run as administrator). -Value Name: EnableLUA +Enter "Get-ProcessMitigation -Name INFOPATH.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Value Type: REG_DWORD -Value: 0x00000001 (1) - - - - - SRG-OS-000104-GPOS-00051 - <GroupDescription></GroupDescription> - - WN19-00-000070 - Windows Server 2019 shared user accounts must not be permitted. - <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 nonrepudiation or individual accountability for system access and resource usage.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000764 - Remove unapproved shared accounts from the system. +If the following mitigations do not have a status of "ON", this is a finding: -Document required shared accounts with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. - - - - Determine whether any shared accounts exist. If no shared accounts exist, this is NA. +DEP: +Enable: ON -Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. +ASLR: +ForceRelocateImages: ON -If unapproved shared accounts exist, this is a finding. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000104-GPOS-00051 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000200 - Windows Server 2019 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. 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> + + WN19-EP-000150 + Windows Server 2019 Exploit Protection mitigations must be configured for java.exe, javaw.exe, and javaws.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000764 - Configure all enabled accounts to require passwords. + SV-103427 + V-93339 + CCI-000366 + Ensure the following mitigations are turned "ON" for java.exe, javaw.exe, and javaws.exe: -The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account. - - - - Review the password required status for enabled user accounts. +DEP: +Enable: ON -Open "PowerShell". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Domain Controllers: +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). +This is applicable to unclassified systems, for other systems this is NA. -If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. +Run "Windows PowerShell" with elevated privileges (run as administrator). -Member servers and standalone systems: +Enter "Get-ProcessMitigation -Name [application name]" with each of the following substituted for [application name]: +java.exe, javaw.exe, and javaws.exe +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. +If the following mitigations do not have a status of "ON" for each, this is a finding: -Exclude disabled accounts (e.g., DefaultAccount, Guest). +DEP: +Enable: ON -If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000379-GPOS-00164 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-MS-000040 - Windows Server 2019 must restrict unauthenticated Remote Procedure Call (RPC) clients from connecting to the RPC server on domain-joined member servers and standalone systems. - <VulnDiscussion>Unauthenticated RPC clients may allow anonymous access to sensitive information. 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> + + WN19-EP-000160 + Windows Server 2019 Exploit Protection mitigations must be configured for lync.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001967 - Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Remote Procedure Call >> "Restrict Unauthenticated RPC clients" to "Enabled" with "Authenticated" selected. - - - - This applies to member servers and standalone systems, it is NA for domain controllers. + SV-103429 + V-93341 + CCI-000366 + Ensure the following mitigations are turned "ON" for lync.exe: -If the following registry value does not exist or is not configured as specified, this is a finding: +DEP: +Enable: ON -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Rpc\ +ASLR: +ForceRelocateImages: ON -Value Name: RestrictRemoteClients +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Type: REG_DWORD -Value: 0x00000001 (1) +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name lync.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000379-GPOS-00164 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000090 - Windows Server 2019 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 the 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> + + WN19-EP-000170 + Windows Server 2019 Exploit Protection mitigations must be configured for MSACCESS.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001967 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain member: Disable machine account password changes" to "Disabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103431 + V-93343 + CCI-000366 + Ensure the following mitigations are turned "ON" for MSACCESS.EXE: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ +DEP: +Enable: ON -Value Name: DisablePasswordChange +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name MSACCESS.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Value Type: REG_DWORD -Value: 0x00000000 (0) +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000118-GPOS-00060 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000190 - Windows Server 2019 outdated or unused accounts must be removed or disabled. - <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, disabled until needed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000180 + Windows Server 2019 Exploit Protection mitigations must be configured for MSPUB.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000795 - Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days. - - - - Open "Windows PowerShell". + SV-103433 + V-93345 + CCI-000366 + Ensure the following mitigations are turned "ON" for MSPUB.EXE: -Domain Controllers: +DEP: +Enable: ON -Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" +ASLR: +ForceRelocateImages: ON -This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Member servers and standalone systems: +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { - $user = ([ADSI]$_.Path) - $lastLogin = $user.Properties.LastLogin.Value - $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 - if ($lastLogin -eq $null) { - $lastLogin = 'Never' - } - Write-Host $user.Name $lastLogin $enabled -}" +This is applicable to unclassified systems, for other systems this is NA. -This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). -For example: User1 10/31/2015 5:49:56 AM True +Run "Windows PowerShell" with elevated privileges (run as administrator). -Review the list of accounts returned by the above queries to determine the finding validity for each account reported. +Enter "Get-ProcessMitigation -Name MSPUB.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Exclude the following accounts: +If the following mitigations do not have a status of "ON", this is a finding: -- Built-in administrator account (Renamed, SID ending in 500) -- Built-in guest account (Renamed, Disabled, SID ending in 501) -- Application accounts +DEP: +Enable: ON -If any enabled accounts have not been logged on to within the past 35 days, this is a finding. +ASLR: +ForceRelocateImages: ON -Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000078-GPOS-00046 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000050 - Windows Server 2019 manually managed application 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></IAControls> + + WN19-EP-000190 + Windows Server 2019 Exploit Protection mitigations must be configured for OIS.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000205 - Establish a policy that requires application/service account passwords that are manually managed to be at least 15 characters in length. Ensure the policy is enforced. - - - - Determine if manually managed application/service accounts exist. If none exist, this is NA. + V-93347 + SV-103435 + CCI-000366 + Ensure the following mitigations are turned "ON" for OIS.EXE: -Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. +DEP: +Enable: ON -If such a policy does not exist or has not been implemented, this is a finding. - - - - - SRG-OS-000073-GPOS-00041 - <GroupDescription></GroupDescription> - - WN19-SO-000300 - Windows Server 2019 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 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000196 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Value Name: NoLMHash +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Value Type: REG_DWORD -Value: 0x00000001 (1) +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name OIS.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000074-GPOS-00042 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000180 - Windows Server 2019 unencrypted passwords must not be sent to third-party Server Message Block (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 determine 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> + + WN19-EP-000200 + Windows Server 2019 Exploit Protection mitigations must be configured for OneDrive.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000197 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93349 + SV-103437 + CCI-000366 + Ensure the following mitigations are turned "ON" for OneDrive.exe: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ +DEP: +Enable: ON -Value Name: EnablePlainTextPassword +ASLR: +ForceRelocateImages: ON -Value Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000076-GPOS-00044 - <GroupDescription></GroupDescription> - - WN19-00-000020 - Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days. - <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. +ImageLoad: +BlockRemoteImageLoads: ON -Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000199 - Change the built-in Administrator account password at least every "60" days. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this. - - - - Review the password last set date for the built-in Administrator account. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Domain controllers: +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Open "PowerShell". +This is applicable to unclassified systems, for other systems this is NA. -Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". +Run "Windows PowerShell" with elevated privileges (run as administrator). -If the "PasswordLastSet" date is greater than "60" days old, this is a finding. +Enter "Get-ProcessMitigation -Name OneDrive.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Member servers and standalone systems: +If the following mitigations do not have a status of "ON", this is a finding: -Open "Command Prompt". +DEP: +Enable: ON -Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. +ASLR: +ForceRelocateImages: ON -(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) +ImageLoad: +BlockRemoteImageLoads: ON -If the "PasswordLastSet" date is greater than "60" days old, this is a finding. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000076-GPOS-00044 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000210 - Windows Server 2019 passwords must be configured to expire. - <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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> + + WN19-EP-000210 + Windows Server 2019 Exploit Protection mitigations must be configured for OUTLOOK.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000199 - Configure all enabled user account passwords to expire. + V-93351 + SV-103439 + CCI-000366 + Ensure the following mitigations are turned "ON" for OUTLOOK.EXE: -Uncheck "Password never expires" for all enabled user accounts in Active Directory Users and Computers for domain accounts and Users in Computer Management for member servers and standalone systems. Document any exceptions with the ISSO. - - - - Review the password never expires status for enabled user accounts. +DEP: +Enable: ON -Open "PowerShell". +ASLR: +ForceRelocateImages: ON -Domain Controllers: +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. +This is applicable to unclassified systems, for other systems this is NA. -Member servers and standalone systems: +Run "Windows PowerShell" with elevated privileges (run as administrator). -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. +Enter "Get-ProcessMitigation -Name OUTLOOK.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). +If the following mitigations do not have a status of "ON", this is a finding: -If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding. +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000066-GPOS-00034 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-PK-000010 - Windows Server 2019 must have the DoD Root Certificate Authority (CA) certificates 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 CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000220 + Windows Server 2019 Exploit Protection mitigations must be configured for plugin-container.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000185 - CCI-002470 - Install the DoD Root CA certificates: - -DoD Root CA 2 -DoD Root CA 3 -DoD Root CA 4 -DoD Root CA 5 - -The InstallRoot tool is available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx. - - - - The certificates and thumbprints referenced below apply to unclassified systems; see PKE documentation for other networks. - -Open "Windows PowerShell" as an administrator. - -Execute the following command: - -Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint, NotAfter + V-93353 + SV-103441 + CCI-000366 + Ensure the following mitigations are turned "ON" for plugin-container.exe: -If the following certificate "Subject" and "Thumbprint" information is not displayed, this is a finding. +DEP: +Enable: ON -If an expired certificate ("NotAfter" date) is not listed in the results, this is not a finding. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 -NotAfter: 12/5/2029 +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB -NotAfter: 12/30/2029 +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 -NotAfter: 7/25/2032 +This is applicable to unclassified systems, for other systems this is NA. -Subject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B -NotAfter: 6/14/2041 +Run "Windows PowerShell" with elevated privileges (run as administrator). -Alternately, use the Certificates MMC snap-in: +Enter "Get-ProcessMitigation -Name plugin-container.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Run "MMC". +If the following mitigations do not have a status of "ON", this is a finding: -Select "File", "Add/Remove Snap-in". +DEP: +Enable: ON -Select "Certificates" and click "Add". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select "Computer account" and click "Next". +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-EP-000230 + Windows Server 2019 Exploit Protection mitigations must be configured for POWERPNT.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93355 + SV-103443 + CCI-000366 + Ensure the following mitigations are turned "ON" for POWERPNT.EXE: -Select "Local computer: (the computer this console is running on)" and click "Finish". +DEP: +Enable: ON -Click "OK". +ASLR: +ForceRelocateImages: ON -Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -For each of the DoD Root CA certificates noted below: +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Right-click on the certificate and select "Open". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Select the "Details" Tab. +This is applicable to unclassified systems, for other systems this is NA. -Scroll to the bottom and select "Thumbprint". +Run "Windows PowerShell" with elevated privileges (run as administrator). -If the DoD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. +Enter "Get-ProcessMitigation -Name POWERPNT.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -If an expired certificate ("Valid to" date) is not listed in the results, this is not a finding. +If the following mitigations do not have a status of "ON", this is a finding: -DoD Root CA 2 -Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 -Valid to: Wednesday, December 5, 2029 +DEP: +Enable: ON -DoD Root CA 3 -Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB -Valid to: Sunday, December 30, 2029 +ASLR: +ForceRelocateImages: ON -DoD Root CA 4 -Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 -Valid to: Sunday, July 25, 2032 +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -DoD Root CA 5 -Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B -Valid to: Friday, June 14, 2041 +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000066-GPOS-00034 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-PK-000020 - Windows Server 2019 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates 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. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000240 + Windows Server 2019 Exploit Protection mitigations must be configured for PPTVIEW.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000185 - CCI-002470 - Install 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 + V-93357 + SV-103445 + CCI-000366 + Ensure the following mitigations are turned "ON" for PPTVIEW.EXE: -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. +DEP: +Enable: ON -The FBCA Cross-Certificate Remover Tool and User Guide are available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx. - - - - This is applicable to unclassified systems. It is NA for others. +ASLR: +ForceRelocateImages: ON -Open "PowerShell" as an administrator. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Execute the following command: +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Get-ChildItem -Path Cert:Localmachine\disallowed | Where {$_.Issuer -Like "*DoD Interoperability*" -and $_.Subject -Like "*DoD*"} | FL Subject, Issuer, Thumbprint, NotAfter +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. +This is applicable to unclassified systems, for other systems this is NA. -If an expired certificate ("NotAfter" date) is not listed in the results, this is not a finding. +Run "Windows PowerShell" with elevated privileges (run as administrator). -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 -NotAfter: 9/6/2019 +Enter "Get-ProcessMitigation -Name PPTVIEW.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -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 -NotAfter: 2/17/2019 +If the following mitigations do not have a status of "ON", this is a finding: -Alternately, use the Certificates MMC snap-in: +DEP: +Enable: ON -Run "MMC". +ASLR: +ForceRelocateImages: ON -Select "File", "Add/Remove Snap-in". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select "Certificates" and click "Add". +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-EP-000250 + Windows Server 2019 Exploit Protection mitigations must be configured for VISIO.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + SV-103447 + V-93359 + CCI-000366 + Ensure the following mitigations are turned "ON" for VISIO.EXE: -Select "Computer account" and click "Next". +DEP: +Enable: ON -Select "Local computer: (the computer this console is running on)" and click "Finish". +ASLR: +ForceRelocateImages: ON -Click "OK". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -For each certificate with "DoD Root CA..." under "Issued To" and "DoD Interoperability Root CA..." under "Issued By": +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Right-click on the certificate and select "Open". +This is applicable to unclassified systems, for other systems this is NA. -Select the "Details" Tab. +Run "Windows PowerShell" with elevated privileges (run as administrator). -Scroll to the bottom and select "Thumbprint". +Enter "Get-ProcessMitigation -Name VISIO.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -If the certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. +If the following mitigations do not have a status of "ON", this is a finding: -If an expired certificate ("Valid to" date) is not listed in the results, this is not a finding. +DEP: +Enable: ON -Issued To: DoD Root CA 2 -Issued By: DoD Interoperability Root CA 1 -Thumbprint: 22BBE981F0694D246CC1472ED2B021DC8540A22F -Valid to: Friday, September 6, 2019 +ASLR: +ForceRelocateImages: ON -Issued To: DoD Root CA 3 -Issued By: DoD Interoperability Root CA 2 -Thumbprint: FFAD03329B9E527A43EEC66A56F9CBB5393E6E13 -Valid to: Sunday, September 23, 2018 +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Issued To: DoD Root CA 3 -Issued By: DoD Interoperability Root CA 2 -Thumbprint: FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4 -Valid to: Sunday, February 17, 2019 +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000066-GPOS-00034 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-PK-000030 - Windows Server 2019 must have the US DoD CCEB Interoperability Root CA cross-certificates 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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000260 + Windows Server 2019 Exploit Protection mitigations must be configured for VPREVIEW.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000185 - CCI-002470 - Install 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 + SV-103449 + V-93361 + CCI-000366 + Ensure the following mitigations are turned "ON" for VPREVIEW.EXE: -DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - 929BF3196896994C0A201DF4A5B71F603FEFBF2E +DEP: +Enable: ON -Administrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user. +ASLR: +ForceRelocateImages: ON -The FBCA Cross-Certificate Remover Tool and User Guide are available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx. - - - - This is applicable to unclassified systems. It is NA for others. +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Open "PowerShell" as an administrator. +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Execute the following command: +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter +This is applicable to unclassified systems, for other systems this is NA. -If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. +Run "Windows PowerShell" with elevated privileges (run as administrator). -If an expired certificate ("NotAfter" date) is not listed in the results, this is not a finding. +Enter "Get-ProcessMitigation -Name VPREVIEW.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -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 -NotAfter: 3/9/2019 +If the following mitigations do not have a status of "ON", this is a finding: -Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US -Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E -NotAfter: 9/27/2019 +DEP: +Enable: ON -Alternately, use the Certificates MMC snap-in: +ASLR: +ForceRelocateImages: ON -Run "MMC". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Select "File", "Add/Remove Snap-in". +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. + + + + + SRG-OS-000480-GPOS-00227 + <GroupDescription></GroupDescription> + + WN19-EP-000270 + Windows Server 2019 Exploit Protection mitigations must be configured for WINWORD.EXE. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93363 + SV-103451 + CCI-000366 + Ensure the following mitigations are turned "ON" for WINWORD.EXE: -Select "Certificates" and click "Add". +DEP: +Enable: ON -Select "Computer account" and click "Next". +ASLR: +ForceRelocateImages: ON -Select "Local computer: (the computer this console is running on)" and click "Finish". +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Click "OK". +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Expand "Certificates" and navigate to "Untrusted Certificates >> Certificates". +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -For each certificate with "US DoD CCEB Interoperability Root CA ..." under "Issued By": +This is applicable to unclassified systems, for other systems this is NA. -Right-click on the certificate and select "Open". +Run "Windows PowerShell" with elevated privileges (run as administrator). -Select the "Details" Tab. +Enter "Get-ProcessMitigation -Name WINWORD.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Scroll to the bottom and select "Thumbprint". +If the following mitigations do not have a status of "ON", this is a finding: -If the certificate below is not listed or the value for the "Thumbprint" field is not as noted, this is a finding. +DEP: +Enable: ON -If an expired certificate ("Valid to" date) is not listed in the results, this is not a finding. +ASLR: +ForceRelocateImages: ON -Issued To: DoD Root CA 2 -Issued By: US DoD CCEB Interoperability Root CA 1 -Thumbprint: DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3 -Valid to: Saturday, March 9, 2019 +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Issued To: DoD Root CA 3 -Issuer by: US DoD CCEB Interoperability Root CA 2 -Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E -Valid: Friday, September 27, 2019 +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000067-GPOS-00035 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000350 - Windows Server 2019 users must be required to enter a password to access private keys stored on the computer. - <VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. - -The cornerstone of the PKI is the private key used to encrypt or digitally sign information. - -If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. - -Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000280 + Windows Server 2019 Exploit Protection mitigations must be configured for wmplayer.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000186 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "System cryptography: Force strong key protection for user keys stored on the computer" to "User must enter a password each time they use a key". - - - - 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\Cryptography\ - -Value Name: ForceKeyProtection + V-93365 + SV-103453 + CCI-000366 + Ensure the following mitigations are turned "ON" for wmplayer.exe: -Type: REG_DWORD -Value: 0x00000002 (2) - - - - - SRG-OS-000120-GPOS-00061 - <GroupDescription></GroupDescription> - - WN19-SO-000290 - Windows Server 2019 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites. - <VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. +DEP: +Enable: ON -Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000803 - Configure 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: +Payload: +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -AES128_HMAC_SHA1 -AES256_HMAC_SHA1 -Future encryption types +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship. - - - - If the following registry value does not exist or is not configured as specified, this is a finding: +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\ +This is applicable to unclassified systems, for other systems this is NA. -Value Name: SupportedEncryptionTypes +Run "Windows PowerShell" with elevated privileges (run as administrator). -Value Type: REG_DWORD -Value: 0x7ffffff8 (2147483640) - - - - - SRG-OS-000393-GPOS-00173 - <GroupDescription></GroupDescription> - - WN19-CC-000480 - Windows Server 2019 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. +Enter "Get-ProcessMitigation -Name wmplayer.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-002890 - CCI-003123 - Configure 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: +If the following mitigations do not have a status of "ON", this is a finding: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ +DEP: +Enable: ON -Value Name: AllowUnencryptedTraffic +Payload: +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Type: REG_DWORD -Value: 0x00000000 (0) +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000393-GPOS-00173 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000510 - Windows Server 2019 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. - -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-EP-000290 + Windows Server 2019 Exploit Protection mitigations must be configured for wordpad.exe. + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002890 - CCI-003123 - Configure 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: + SV-103455 + V-93367 + CCI-000366 + Ensure the following mitigations are turned "ON" for wordpad.exe: -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ +DEP: +Enable: ON -Value Name: AllowUnencryptedTraffic +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000125-GPOS-00065 - <GroupDescription></GroupDescription> - - WN19-CC-000470 - Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000877 - Configure 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: +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. + + + + If the referenced application is not installed on the system, this is NA. -Value Name: AllowBasic +This is applicable to unclassified systems, for other systems this is NA. -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000125-GPOS-00065 - <GroupDescription></GroupDescription> - - WN19-CC-000490 - Windows Server 2019 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. Disallowing Digest authentication will reduce this potential.</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000877 - Configure 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: +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name wordpad.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ +If the following mitigations do not have a status of "ON", this is a finding: -Value Name: AllowDigest +DEP: +Enable: ON -Type: REG_DWORD -Value: 0x00000000 (0) +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - - SRG-OS-000125-GPOS-00065 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000500 - Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-MS-000050 + Windows Server 2019 must limit the caching of logon credentials to four or less on domain-joined member servers. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000877 - Configure 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: + SV-103363 + V-93275 + CCI-000366 + 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. + + + + This applies to member servers. For domain controllers and standalone systems, this is NA. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ +If the following registry value does not exist or is not configured as specified, this is a finding: -Value Name: AllowBasic +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ -Type: REG_DWORD -Value: 0x00000000 (0) +Value Name: CachedLogonsCount + +Value Type: REG_SZ +Value: 4 (or less) - - SRG-OS-000478-GPOS-00223 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000360 - Windows Server 2019 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing. - <VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-MS-000140 + Windows Server 2019 must be running Credential Guard on domain-joined member servers. + <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. This authentication information, which was stored in the Local Security Authority (LSA) in previous versions of Windows, is isolated from the rest of operating system and can only be accessed by privileged system 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002450 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93277 + SV-103365 + CCI-000366 + Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Enabled with UEFI lock" selected for "Credential Guard Configuration". -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ - -Value Name: Enabled +A Microsoft article on Credential Guard system requirement can be found at the following link: -Value Type: REG_DWORD -Value: 0x00000001 (1) +https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements + +Severity Override Guidance: The AO can allow the severity override if they have reviewed the overall protection provided to the affected servers that are not capable of complying with the Credential Guard requirement. Items that should be reviewed/considered for compliance or mitigation for non-Credential Guard compliance are: + +The use of Microsoft Local Administrator Password Solution (LAPS) or similar products to control different local administrative passwords for all affected affected servers. This is to include a strict password change requirement (60 days or less). +…. +Strict separation of roles and duties. Server administrator credentials cannot be used on Windows 10 desktop to administer it. Documentation of all exceptions should be supplied. +…. +Use of a Privileged Access Workstation (PAW) and adherence to the Clean Source principle for administering affected affected servers. +…. +Boundary Protection that is currently in place to protect from vulnerabilities in the network/servers. +…. +Windows Defender rule block credential stealing from LSASS.exe is applied. This rule can only be applied if Windows Defender is in use. +…. +The overall number of vulnerabilities that are unmitigated on the network/servers. + + + + + For domain controllers and standalone systems, this is NA. -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; otherwise. the browser will not be able to connect to a secure site. - - - - - SRG-OS-000185-GPOS-00079 - <GroupDescription></GroupDescription> - - WN19-00-000250 - Windows Server 2019 systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. - <VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. -Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). +Open "PowerShell" with elevated privileges (run as administrator). -Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001199 - CCI-002475 - CCI-002476 - Configure systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data to employ encryption to protect the confidentiality and integrity of all information at rest. - - - - Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. +Enter the following: -If they do not, this is a finding. - - - - - SRG-OS-000134-GPOS-00068 - <GroupDescription></GroupDescription> - - WN19-CC-000240 - Windows Server 2019 administrator accounts must not be enumerated during elevation. - <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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001084 - Configure 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: +"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ +If "SecurityServicesRunning" does not include a value of "1" (e.g., "{1, 2}"), this is a finding. -Value Name: EnumerateAdministrators +Alternately: -Type: REG_DWORD -Value: 0x00000000 (0) - - - - - SRG-OS-000134-GPOS-00068 - <GroupDescription></GroupDescription> - - WN19-MS-000020 - Windows Server 2019 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers. - <VulnDiscussion>A compromised local administrator account can provide means for an attacker to move laterally between domain systems. +Run "System Information". -With User Account Control enabled, filtering the privileged token for local 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-001084 - Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Apply UAC restrictions to local accounts on network logons" to "Enabled". +Under "System Summary", verify the following: -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. - - - - This applies to member servers. For domain controllers and standalone systems, this is NA. +If "Device Guard Security Services Running" does not list "Credential Guard", this is a finding. -If the following registry value does not exist or is not configured as specified, this is a finding: +The policy settings referenced in the Fix section will configure the following registry value. However, due to hardware requirements, the registry value alone does not ensure proper function. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ -Value Name: LocalAccountTokenFilterPolicy +Value Name: LsaCfgFlags +Value Type: REG_DWORD +Value: 0x00000001 (1) (Enabled with UEFI lock) -Type: REG_DWORD -Value: 0x00000000 (0) +A Microsoft article on Credential Guard system requirement can be found at the following link: -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. +https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements - - SRG-OS-000134-GPOS-00068 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000390 - Windows Server 2019 UIAccess applications must not be allowed to prompt for elevation without using 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 prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000020 + Windows Server 2019 must prevent local accounts with blank passwords from being used 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 does 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001084 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" to "Disabled". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + V-93279 + SV-103367 + CCI-000366 + Configure 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". + + + + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: EnableUIADesktopToggle +Value Name: LimitBlankPasswordUse Value Type: REG_DWORD -Value: 0x00000000 (0) +Value: 0x00000001 (1) - - SRG-OS-000134-GPOS-00068 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000400 - Windows Server 2019 User Account Control must, at a 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></IAControls> + + WN19-SO-000100 + Windows Server 2019 maximum age for machine account passwords must be configured to 30 days or less. + <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 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001084 - Configure 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". + SV-103373 + V-93285 + CCI-000366 + This is the default configuration for this setting (30 days). -The more secure option for this setting, "Prompt for credentials on the secure desktop", would also be acceptable. - - - - UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). +Configure 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). + + + + This is the default configuration for this setting (30 days). 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: ConsentPromptBehaviorAdmin +Value Name: MaximumPasswordAge Value Type: REG_DWORD -Value: 0x00000002 (2) (Prompt for consent on the secure desktop) -0x00000001 (1) (Prompt for credentials on the secure desktop) +Value: 0x0000001e (30) (or less, but not 0) - - SRG-OS-000134-GPOS-00068 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000420 - Windows Server 2019 User 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></IAControls> + + WN19-SO-000150 + Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001084 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + V-93287 + SV-103375 + CCI-000366 + Configure 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". + + + + 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\ +Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ -Value Name: EnableInstallerDetection +Value Name: scremoveoption -Value Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_SZ +Value: 1 (Lock Workstation) or 2 (Force Logoff) + +If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO. - - SRG-OS-000134-GPOS-00068 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000430 - Windows Server 2019 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations. - <VulnDiscussion>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> + + WN19-SO-000210 + Windows Server 2019 must not allow anonymous SID/Name translation. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001084 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103377 + V-93289 + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Allow anonymous SID/Name translation" to "Disabled". + + + + Verify the effective setting in Local Group Policy Editor. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Run "gpedit.msc". -Value Name: EnableSecureUIAPaths +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. -Value Type: REG_DWORD -Value: 0x00000001 (1) +If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding. - - SRG-OS-000134-GPOS-00068 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000450 - Windows Server 2019 User Account Control (UAC) must virtualize file and registry write failures to per-user locations. - <VulnDiscussion>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></IAControls> + + WN19-SO-000220 + Windows Server 2019 must not allow anonymous enumeration of Security Account Manager (SAM) accounts. + <VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001084 - Configure 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". - - - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + V-93291 + SV-103379 + CCI-000366 + Configure 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". + + + + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: EnableVirtualization +Value Name: RestrictAnonymousSAM Value Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000138-GPOS-00069 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000230 - Windows Server 2019 non-system-created file shares must limit access to groups that require it. - <VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000240 + Windows Server 2019 must be configured to prevent anonymous users from having the same permissions as the Everyone group. + <VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001090 - If a non-system-created 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. - - - - If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) - -Run "Computer Management". - -Navigate to System Tools >> Shared Folders >> Shares. - -Right-click any non-system-created shares. - -Select "Properties". - -Select the "Share Permissions" tab. + V-93293 + SV-103381 + CCI-000366 + Configure 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". + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Select the "Security" tab. +Value Name: EveryoneIncludesAnonymous -If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. +Value Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000138-GPOS-00069 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000350 - Windows Server 2019 Remote Desktop Services must prevent drive redirection. - <VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls> + + WN19-SO-000260 + Windows Server 2019 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously. + <VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001090 - Configure 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". - - - + SV-103383 + V-93295 + CCI-000366 + Configure 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". + + + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\ -Value Name: fDisableCdm +Value Name: UseMachineId Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000138-GPOS-00069 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000230 - Windows Server 2019 must not allow anonymous enumeration of shares. - <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></IAControls> + + WN19-SO-000270 + Windows Server 2019 must prevent NTLM 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001090 - Configure 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". - - - + V-93297 + SV-103385 + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network security: Allow LocalSystem NULL session fallback" 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: \SYSTEM\CurrentControlSet\Control\Lsa\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ -Value Name: RestrictAnonymous +Value Name: allownullsessionfallback -Value Type: REG_DWORD -Value: 0x00000001 (1) +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000138-GPOS-00069 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000250 - Windows Server 2019 must restrict anonymous access to Named Pipes and Shares. - <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></IAControls> + + WN19-SO-000280 + Windows Server 2019 must prevent PKU2U authentication using online identities. + <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001090 - Configure 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". - - - + SV-103387 + V-93299 + CCI-000366 + Configure 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". + + + 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\Services\LanManServer\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\pku2u\ -Value Name: RestrictNullSessAccess +Value Name: AllowOnlineID -Value Type: REG_DWORD -Value: 0x00000001 (1) +Type: REG_DWORD +Value: 0x00000000 (0) - - SRG-OS-000420-GPOS-00186 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-CC-000060 - Windows Server 2019 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 server's 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> + + WN19-SO-000310 + Windows Server 2019 LAN Manager authentication level must be configured 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 standalone 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002385 - Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" to "Enabled". - -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively. - - - + SV-103389 + V-93301 + CCI-000366 + Configure 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". + + + 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\Services\Netbt\Parameters\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: NoNameReleaseOnDemand +Value Name: LmCompatibilityLevel -Value Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_DWORD +Value: 0x00000005 (5) - - SRG-OS-000425-GPOS-00189 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-00-000260 - Windows Server 2019 must implement protection methods such as TLS, encrypted VPNs, or IPsec if the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. - <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. - -Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. - -Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. - -Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000320 + Windows Server 2019 must be configured to at least negotiate signing for LDAP client signing. + <VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002420 - CCI-002422 - Configure protection methods such as TLS, encrypted VPNs, or IPsec when the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. - - - - If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. + SV-103391 + V-93303 + CCI-000366 + Configure 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. + + + + If the following registry value does not exist or is not configured as specified, this is a finding: -If protection methods have not been implemented, this is a finding. +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LDAP\ + +Value Name: LDAPClientIntegrity + +Value Type: REG_DWORD +Value: 0x00000001 (1) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000060 - Windows Server 2019 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000330 + Windows Server 2019 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption. + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - + SV-103393 + V-93305 + CCI-000366 + Configure 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). + + + 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ -Value Name: RequireSignOrSeal +Value Name: NTLMMinClientSec Value Type: REG_DWORD -Value: 0x00000001 (1) +Value: 0x20080000 (537395200) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000070 - Windows Server 2019 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000340 + Windows Server 2019 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption. + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - + SV-103395 + V-93307 + CCI-000366 + Configure 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). + + + 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ -Value Name: SealSecureChannel +Value Name: NTLMMinServerSec Value Type: REG_DWORD -Value: 0x00000001 (1) +Value: 0x20080000 (537395200) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000080 - Windows Server 2019 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-SO-000370 + Windows Server 2019 default permissions of global system objects must be strengthened. + <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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - + V-93309 + SV-103397 + CCI-000366 + Configure 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". + + + 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\ -Value Name: SignSecureChannel +Value Name: ProtectionMode Value Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000110 - Windows Server 2019 must be configured to require a strong session key. - <VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-UC-000010 + Windows Server 2019 must preserve zone information when saving attachments. + <VulnDiscussion>Attachments from outside sources may contain malicious code. 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103399 + V-93311 + CCI-000366 + The default behavior is for Windows to mark file attachments with their zone information. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ +If this needs to be corrected, configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager >> "Do not preserve zone information in file attachments" to "Not Configured" or "Disabled". + + + + The default behavior is for Windows to mark file attachments with their zone information. -Value Name: RequireStrongKey +If the registry Value Name below does not exist, this is not a finding. -Value Type: REG_DWORD -Value: 0x00000001 (1) +If it exists and is configured with a value of "2", this is not a finding. -This setting may prevent a system from being joined to a domain if not configured consistently between systems. +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ + +Value Name: SaveZoneInformation + +Value Type: REG_DWORD +Value: 0x00000002 (2) (or if the Value Name does not exist) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00229 <GroupDescription></GroupDescription> - - WN19-SO-000160 - Windows Server 2019 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-CC-000450 + Windows Server 2019 must disable automatically signing in the last interactive user after a system-initiated restart. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network client: Digitally sign communications (always)" to "Enabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103357 + V-93269 + CCI-000366 + Configure 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: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: RequireSecuritySignature +Value Name: DisableAutomaticRestartSignOn Value Type: REG_DWORD Value: 0x00000001 (1) - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - - WN19-SO-000170 - Windows Server 2019 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled. - <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. + + WN19-00-000280 + Windows Server 2019 must have a host-based firewall installed and enabled. + <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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93571 + SV-103657 + CCI-002080 + CCI-000366 + Install and enable a host-based firewall on the system. + + + + Determine if a host-based firewall is installed and enabled on the system. -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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. + + + + + SRG-OS-000095-GPOS-00049 + <GroupDescription></GroupDescription> + + WN19-CC-000451 + The Windows Explorer Preview pane must be disabled for Windows Server 2019. + <VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. + +Organizations must disable the Windows Preview pane and Windows Detail pane.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-102625 + SV-111575 + CCI-000366 + Ensure the following settings are configured for Windows Server 2019 locally or applied through group policy. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ +Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn off Preview Pane" to "Enabled". -Value Name: EnableSecuritySignature +Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn on or off details pane" to "Enabled" and "Configure details pane" to "Always hide". + + + + If the following registry values do not exist or are not configured as specified, this is a finding: + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + +Value Name: NoPreviewPane Value Type: REG_DWORD -Value: 0x00000001 (1) + +Value: 1 + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + +Value Name: NoReadingPane + +Value Type: REG_DWORD + +Value: 1 - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000021-GPOS-00005 <GroupDescription></GroupDescription> - - WN19-SO-000190 - Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled. - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AC-000020 + Windows Server 2019 must have the number of allowed bad logon attempts configured to three or less. + <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 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network server: Digitally sign communications (always)" to "Enabled". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + V-93141 + SV-103229 + CCI-000044 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout threshold" to "3" or fewer invalid logon attempts (excluding "0", which is unacceptable). + + + + Verify the effective setting in Local Group Policy Editor. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ +Run "gpedit.msc". -Value Name: RequireSecuritySignature +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. -Value Type: REG_DWORD -Value: 0x00000001 (1) +If the "Account lockout threshold" is "0" or more than "3" attempts, this is a finding. + + - - SRG-OS-000423-GPOS-00187 + + SRG-OS-000021-GPOS-00005 <GroupDescription></GroupDescription> - - WN19-SO-000200 - Windows Server 2019 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled. - <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. + + WN19-AC-000030 + Windows Server 2019 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater. + <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. -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002418 - CCI-002421 - Configure 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". - - - - If the following registry value does not exist or is not configured as specified, this is a finding: + SV-103231 + V-93143 + CCI-000044 + CCI-002238 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Reset account lockout counter after" to at least "15" minutes. + + + + Verify the effective setting in Local Group Policy Editor. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ +Run "gpedit.msc". -Value Name: EnableSecuritySignature +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. -Value Type: REG_DWORD -Value: 0x00000001 (1) +If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding. + + - - SRG-OS-000433-GPOS-00192 + + SRG-OS-000057-GPOS-00027 <GroupDescription></GroupDescription> - - WN19-CC-000310 - Windows Server 2019 Explorer Data Execution Prevention must be enabled. - <VulnDiscussion>Data Execution Prevention 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></IAControls> + + WN19-UR-000170 + Windows Server 2019 Manage auditing and security log user right must only be assigned to the Administrators group. + <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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002824 - The default behavior is for data execution prevention to be turned on for File Explorer. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off Data Execution Prevention for Explorer" to "Not Configured" or "Disabled". - - - - The default behavior is for Data Execution Prevention to be turned on for File Explorer. + V-93197 + SV-103285 + CCI-000171 + CCI-000164 + CCI-000162 + CCI-000163 + CCI-001914 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Manage auditing and security log" to include only the following accounts or groups: -If the registry value name below does not exist, this is not a finding. +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. -If it exists and is configured with a value of "0", this is not a finding. +Run "gpedit.msc". -If it exists and is configured with a value of "1", this is a finding. +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ +If any accounts or groups other than the following are granted the "Manage auditing and security log" user right, this is a finding. -Value Name: NoDataExecutionPrevention +- Administrators -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) + - - SRG-OS-000433-GPOS-00193 + + SRG-OS-000069-GPOS-00037 <GroupDescription></GroupDescription> - - WN19-EP-000020 - Windows Server 2019 Exploit Protection system-level mitigation, Randomize memory allocations (Bottom-Up ASLR), must be on. - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AC-000080 + Windows Server 2019 must have the built-in Windows password complexity policy 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 three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. + +Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002824 - Ensure Exploit Protection system-level mitigation, "Randomize memory allocations (Bottom-Up ASLR)" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Randomize memory allocations (Bottom-Up ASLR)" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Bottom-Up ASLR on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <ASLR BottomUp="true" HighEntropy="true"></ASLR> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location. - - - - This is applicable to unclassified systems, for other systems this is NA. - -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". - -Run "Windows PowerShell" with elevated privileges (run as administrator). + V-93459 + SV-103545 + CCI-000192 + CCI-000193 + CCI-000194 + CCI-001619 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Password must meet complexity requirements" to "Enabled". + + + + Verify the effective setting in Local Group Policy Editor. -Enter "Get-ProcessMitigation -System". +Run "gpedit.msc". -If the status of "ASLR: BottomUp" is "OFF", this is a finding. +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. -Values that would not be a finding include: +If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding. -ON -NOTSET (Default configuration) + - - SRG-OS-000191-GPOS-00080 + + SRG-OS-000073-GPOS-00041 <GroupDescription></GroupDescription> - - WN19-00-000290 - Windows Server 2019 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Host Based Security System (HBSS) is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). - <VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AC-000090 + Windows Server 2019 reversible password encryption must be disabled. + <VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-001233 - Install a DoD approved HBSS software and ensure it is operating continuously. - - - - Verify DoD approved HBSS software is installed, configured, and properly operating. Ask the operator to document the HBSS software installation and configuration. + SV-103551 + V-93465 + CCI-000196 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Store passwords using reversible encryption" to "Disabled". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for "Store passwords using reversible encryption" is not set to "Disabled", this is a finding. -If the operator is not able to provide a documented configuration for an installed HBSS or if the HBSS software is not properly configured, maintained, or used, this is a finding. + - - SRG-OS-000480-GPOS-00231 + + SRG-OS-000075-GPOS-00043 <GroupDescription></GroupDescription> - - WN19-00-000280 - Windows Server 2019 must have a host-based firewall installed and enabled. - <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></IAControls> + + WN19-AC-000060 + Windows Server 2019 minimum password age must be configured to at least one day. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - CCI-002080 - Install and enable a host-based firewall on the system. - - - - Determine if a host-based firewall is installed and enabled on the system. + SV-103557 + V-93471 + CCI-000198 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password age" to at least "1" day. + + + + Verify the effective setting in Local Group Policy Editor. -If a host-based firewall is not installed and enabled on the system, this is a finding. +Run "gpedit.msc". -The configuration requirements will be determined by the applicable firewall STIG. +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for the "Minimum password age" is set to "0" days ("Password can be changed immediately"), this is a finding. + + - - WN19-CC-000451 + + SRG-OS-000076-GPOS-00044 <GroupDescription></GroupDescription> - - WN19-CC-000451 - The Windows Explorer Preview pane must be disabled for Windows Server 2019. - <VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. - -Organizations must disable the Windows Preview pane and Windows Detail pane.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + WN19-AC-000050 + Windows Server 2019 maximum password age must be configured to 60 days or less. + <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Ensure the following settings are configured for Windows Server 2019 locally or applied through group policy. - -Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn off Preview Pane" to "Enabled". - -Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn on or off details pane" to "Enabled" and "Configure details pane" to "Always hide". - - - - - If the following registry values do not exist or are not configured as specified, this is a finding: - -Registry Hive: HKEY_CURRENT_USER -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer - -Value Name: NoPreviewPane - -Value Type: REG_DWORD + V-93477 + SV-103563 + CCI-000199 + Configure 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). + + + + Verify the effective setting in Local Group Policy Editor. -Value: 1 +Run "gpedit.msc". -Registry Hive: HKEY_CURRENT_USER -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. -Value Name: NoReadingPane +If the value for the "Maximum password age" is greater than "60" days, this is a finding. -Value Type: REG_DWORD +If the value is set to "0" (never expires), this is a finding. -Value: 1 - - SRG-OS-000297-GPOS-00115 + + SRG-OS-000077-GPOS-00045 <GroupDescription></GroupDescription> - - WN19-MS-000120 - Windows Server 2019 Deny log on through Remote Desktop Services user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and all local accounts and from 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" user right defines the accounts that are prevented from logging on using Remote Desktop Services. - -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> + + WN19-AC-000040 + Windows Server 2019 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 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002314 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on through Remote Desktop Services" to include the following: + V-93479 + SV-103565 + CCI-000200 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Enforce password history" to "24" passwords remembered. + + + + Verify the effective setting in Local Group Policy Editor. -Domain Systems Only: -- Enterprise Admins group -- Domain Admins group -- Local account (see Note below) +Run "gpedit.msc". -All Systems: -- Guests group +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. -Note: "Local account" is referring to the Windows built-in security group. - - - - This applies to member servers and standalone systems. A separate version applies to domain controllers. +If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding. -Verify the effective setting in Local Group Policy Editor. + + + + + + SRG-OS-000078-GPOS-00046 + <GroupDescription></GroupDescription> + + WN19-AC-000070 + Windows Server 2019 minimum password length must be configured to 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93463 + SV-103549 + CCI-000205 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password length" to "14" characters. + + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: - -Domain Systems Only: -- Enterprise Admins group -- Domain Admins group -- Local account (see Note below) +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. -All Systems: -- Guests group +If the value for the "Minimum password length," is less than "14" characters, this is a finding. - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-MS-000070 Windows Server 2019 Access this computer from the network user right must only be assigned to the Administrators and Authenticated Users groups on domain-joined member servers and standalone systems. <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 this right must be limited to those requiring it.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Access this computer from the network" to include only the following accounts or groups: + V-93007 + SV-103095 + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Access this computer from the network" to include only the following accounts or groups: - Administrators - Authenticated Users - - - + + + This applies to member servers and standalone systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. @@ -12050,10 +12780,10 @@ If any accounts or groups other than the following are granted the "Access this - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-MS-000080 Windows Server 2019 Deny access to this computer from the network user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and local accounts and from unauthenticated access on all systems. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -12066,14 +12796,16 @@ Local accounts on domain-joined systems must also be assigned this right to decr 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure 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: + V-93009 + SV-103097 + CCI-000213 + Configure 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 @@ -12084,9 +12816,9 @@ All Systems: - Guests group Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering. - - - + + + This applies to member servers and standalone systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. @@ -12109,10 +12841,10 @@ All Systems: - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-MS-000090 Windows Server 2019 Deny log on as a batch job user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from unauthenticated access on all systems. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -12123,14 +12855,16 @@ In an Active Directory Domain, denying logons to the Enterprise Admins and Domai 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure 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: + V-93011 + SV-103099 + CCI-000213 + Configure 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 Admins Group @@ -12138,9 +12872,9 @@ Domain Systems Only: All Systems: - Guests Group - - - + + + This applies to member servers and standalone systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. @@ -12162,10 +12896,10 @@ All Systems: - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-MS-000100 Windows Server 2019 Deny log on as a service user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts. No other groups or accounts must be assigned this right. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -12176,21 +12910,23 @@ In an Active Directory Domain, denying logons to the Enterprise Admins and Domai Incorrect configurations could prevent services from starting and result in a denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure 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: + SV-103101 + V-93013 + CCI-000213 + Configure 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: Domain systems: - Enterprise Admins Group - Domain Admins Group - - - + + + This applies to member servers and standalone systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. @@ -12210,10 +12946,10 @@ If any accounts or groups are defined for the "Deny log on as a service" user ri - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-MS-000110 Windows Server 2019 Deny log on locally user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from unauthenticated access on all systems. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -12224,14 +12960,16 @@ In an Active Directory Domain, denying logons to the Enterprise Admins and Domai 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on locally" to include the following: + SV-103103 + V-93015 + CCI-000213 + Configure 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 @@ -12239,9 +12977,9 @@ Domain Systems Only: All Systems: - Guests Group - - - + + + This applies to member servers and standalone systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. @@ -12263,64 +13001,162 @@ All Systems: - + SRG-OS-000080-GPOS-00048 <GroupDescription></GroupDescription> - + WN19-UR-000030 Windows Server 2019 Allow log on locally user right must only be assigned to the Administrators group. <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></IAControls> +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></IAControls> + + DPMS Target MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93017 + SV-103105 + CCI-000213 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on locally" to include only the following accounts or groups: + +- Administrators + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 + + + + + + + SRG-OS-000121-GPOS-00062 + <GroupDescription></GroupDescription> + + WN19-SO-000010 + Windows Server 2019 must have the built-in guest account disabled. + <VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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 MS Windows Server 2019 + DISA + DPMS Target + MS Windows Server 2019 + 2907 + + V-93497 + SV-103583 + CCI-000804 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Guest account status" to "Disabled". + + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. + +If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. + + + + + + + SRG-OS-000297-GPOS-00115 + <GroupDescription></GroupDescription> + + WN19-MS-000120 + Windows Server 2019 Deny log on through Remote Desktop Services user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and all local accounts and from 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" user right defines the accounts that are prevented from logging on using Remote Desktop Services. + +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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000213 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on locally" to include only the following accounts or groups: + SV-103053 + V-92965 + CCI-002314 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on through Remote Desktop Services" to include the following: -- Administrators - - - - Verify the effective setting in Local Group Policy Editor. +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- Local account (see Note below) + +All Systems: +- Guests group + +Note: "Local account" is referring to the Windows built-in security group. + + + + This applies to member servers and standalone systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: +If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: -- Administrators +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- Local account (see Note below) + +All Systems: +- Guests group - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-MS-000130 Windows Server 2019 Enable computer and user accounts to be trusted for delegation user right must not be assigned to any groups or accounts on domain-joined member servers and standalone systems. <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 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + SV-103135 + V-93047 + CCI-002235 + Configure 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). + + + This applies to member servers and standalone systems. A separate version applies to domain controllers. Verify the effective setting in Local Group Policy Editor. @@ -12335,27 +13171,29 @@ If any accounts or groups are granted the "Enable computer and user accounts to - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000010 Windows Server 2019 Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + V-93049 + SV-103137 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12368,27 +13206,29 @@ If any accounts or groups are granted the "Access Credential Manager as a truste - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000020 Windows Server 2019 Act as part of the operating system user right must not be assigned to any groups or accounts. <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 the 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + SV-103139 + V-93051 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12401,29 +13241,31 @@ If any accounts or groups (to include administrators), are granted the "Act as p - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000040 Windows Server 2019 Back up files and directories user right must only be assigned to the Administrators group. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Back up files and directories" to include only the following accounts or groups: + V-93053 + SV-103141 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Back up files and directories" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12438,29 +13280,31 @@ If any accounts or groups other than the following are granted the "Back up file - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000050 Windows Server 2019 Create a pagefile user right must only be assigned to the Administrators group. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create a pagefile" to include only the following accounts or groups: + SV-103143 + V-93055 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create a pagefile" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12475,27 +13319,29 @@ If any accounts or groups other than the following are granted the "Create a pag - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000060 Windows Server 2019 Create a token object user right must not be assigned to any groups or accounts. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + V-93057 + SV-103145 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12508,32 +13354,34 @@ If any accounts or groups are granted the "Create a token object" user right, th - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000070 Windows Server 2019 Create global objects user right must only be assigned to Administrators, Service, Local Service, and Network Service. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create global objects" to include only the following accounts or groups: + V-93059 + SV-103147 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create global objects" to include only the following accounts or groups: - Administrators - Service - Local Service - Network Service - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12551,27 +13399,29 @@ If any accounts or groups other than the following are granted the "Create globa - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000080 Windows Server 2019 Create permanent shared objects user right must not be assigned to any groups or accounts. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + SV-103149 + V-93061 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12584,31 +13434,33 @@ If any accounts or groups are granted the "Create permanent shared objects" user - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000090 Windows Server 2019 Create symbolic links user right must only be assigned to the Administrators group. <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 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create symbolic links" to include only the following accounts or groups: + SV-103151 + V-93063 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create symbolic links" to include only the following accounts or groups: - Administrators Systems that have the Hyper-V role will also have "Virtual Machines" given this user right. If this needs to be added manually, enter it as "NT Virtual Machine\Virtual Machines". - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12623,29 +13475,31 @@ If any accounts or groups other than the following are granted the "Create symbo - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000100 Windows Server 2019 Debug programs: user right must only be assigned to the Administrators group. <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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Debug programs" to include only the following accounts or groups: + V-93065 + SV-103153 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Debug programs" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12660,29 +13514,31 @@ If any accounts or groups other than the following are granted the "Debug progra - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000110 Windows Server 2019 Force shutdown from a remote system user right must only be assigned to the Administrators group. <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 denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Force shutdown from a remote system" to include only the following accounts or groups: + V-93067 + SV-103155 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Force shutdown from a remote system" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12697,30 +13553,32 @@ If any accounts or groups other than the following are granted the "Force shutdo - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000120 Windows Server 2019 Generate security audits user right must only be assigned to Local Service and Network Service. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Generate security audits" to include only the following accounts or groups: + V-93069 + SV-103157 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Generate security audits" to include only the following accounts or groups: - Local Service - Network Service - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12736,32 +13594,34 @@ If any accounts or groups other than the following are granted the "Generate sec - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000130 Windows Server 2019 Impersonate a client after authentication user right must only be assigned to Administrators, Service, Local Service, and Network Service. <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 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Impersonate a client after authentication" to include only the following accounts or groups: + SV-103159 + V-93071 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Impersonate a client after authentication" to include only the following accounts or groups: - Administrators - Service - Local Service - Network Service - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12779,29 +13639,31 @@ If any accounts or groups other than the following are granted the "Impersonate - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000140 Windows Server 2019 Increase scheduling priority: user right must only be assigned to the Administrators group. <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 denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Increase scheduling priority" to include only the following accounts or groups: + SV-103161 + V-93073 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Increase scheduling priority" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12816,29 +13678,31 @@ If any accounts or groups other than the following are granted the "Increase sch - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000150 Windows Server 2019 Load and unload device drivers user right must only be assigned to the Administrators group. <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Load and unload device drivers" user right allows a user to load device drivers dynamically on a system. This could be used by an attacker to install malicious code.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Load and unload device drivers" to include only the following accounts or groups: + SV-103163 + V-93075 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Load and unload device drivers" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12853,27 +13717,29 @@ If any accounts or groups other than the following are granted the "Load and unl - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000160 Windows Server 2019 Lock pages in memory user right must not be assigned to any groups or accounts. <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 denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure 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). - - - + V-93077 + SV-103165 + CCI-002235 + Configure 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). + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12886,29 +13752,31 @@ If any accounts or groups are granted the "Lock pages in memory" user right, thi - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000180 Windows Server 2019 Modify firmware environment values user right must only be assigned to the Administrators group. <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 denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Modify firmware environment values" to include only the following accounts or groups: + V-93079 + SV-103167 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Modify firmware environment values" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12923,29 +13791,31 @@ If any accounts or groups other than the following are granted the "Modify firmw - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000190 Windows Server 2019 Perform volume maintenance tasks user right must only be assigned to the Administrators group. <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. This could be used to delete volumes, resulting in data loss or a denial of 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Perform volume maintenance tasks" to include only the following accounts or groups: + V-93081 + SV-103169 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Perform volume maintenance tasks" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12960,29 +13830,31 @@ If any accounts or groups other than the following are granted the "Perform volu - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000200 Windows Server 2019 Profile single process user right must only be assigned to the Administrators group. <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 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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Profile single process" to include only the following accounts or groups: + V-93083 + SV-103171 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Profile single process" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -12997,29 +13869,31 @@ If any accounts or groups other than the following are granted the "Profile sing - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000210 Windows Server 2019 Restore files and directories user right must only be assigned to the Administrators group. <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 overwrite more current 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Restore files and directories" to include only the following accounts or groups: + V-93085 + SV-103173 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Restore files and directories" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -13034,29 +13908,31 @@ If any accounts or groups other than the following are granted the "Restore file - + SRG-OS-000324-GPOS-00125 <GroupDescription></GroupDescription> - + WN19-UR-000220 Windows Server 2019 Take ownership of files or other objects user right must only be assigned to the Administrators group. <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></IAControls> - DPMS Target Windows 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002235 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Take ownership of files or other objects" to include only the following accounts or groups: + V-93087 + SV-103175 + CCI-002235 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Take ownership of files or other objects" to include only the following accounts or groups: - Administrators - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -13071,92 +13947,29 @@ If any accounts or groups other than the following are granted the "Take ownersh - - SRG-OS-000021-GPOS-00005 - <GroupDescription></GroupDescription> - - WN19-AC-000020 - Windows Server 2019 must have the number of allowed bad logon attempts configured to three or less. - <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 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000044 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout threshold" to "3" or fewer invalid logon attempts (excluding "0", which is unacceptable). - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. - -If the "Account lockout threshold" is "0" or more than "3" attempts, this is a finding. - - - - - - - SRG-OS-000021-GPOS-00005 - <GroupDescription></GroupDescription> - - WN19-AC-000030 - Windows Server 2019 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater. - <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. - -Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000044 - CCI-002238 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Reset account lockout counter after" to at least "15" minutes. - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. - -If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding. - - - - - - + SRG-OS-000329-GPOS-00128 <GroupDescription></GroupDescription> - + WN19-AC-000010 Windows Server 2019 account lockout duration must be configured to 15 minutes or greater. <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-002238 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout duration" to "15" minutes or greater. + V-93145 + SV-103233 + CCI-002238 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout duration" to "15" minutes or greater. A value of "0" is also acceptable, requiring an administrator to unlock the account. - - - + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -13169,68 +13982,27 @@ If the "Account lockout duration" is less than "15" minutes (excluding "0"), thi - - SRG-OS-000057-GPOS-00027 - <GroupDescription></GroupDescription> - - WN19-UR-000170 - Windows Server 2019 Manage auditing and security log user right must only be assigned to the Administrators group. - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000162 - CCI-000163 - CCI-000164 - CCI-000171 - CCI-001914 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Manage auditing and security log" to include only the following accounts or groups: - -- Administrators - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -- Administrators - - - - - - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - + WN19-00-000450 Windows Server 2019 must have orphaned security identifiers (SIDs) removed from user rights. <VulnDiscussion>Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be established for some reason.</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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Remove any unresolved SIDs found in User Rights assignments and determined to not be for currently valid accounts or groups by removing the accounts or groups from the appropriate group policy. - - - + V-93227 + SV-103315 + CCI-000366 + Remove any unresolved SIDs found in User Rights assignments and determined to not be for currently valid accounts or groups by removing the accounts or groups from the appropriate group policy. + + + Review the effective User Rights setting in Local Group Policy Editor. Run "gpedit.msc". @@ -13244,25 +14016,27 @@ If any unresolved SIDs exist and are not for currently valid accounts or groups, - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - + WN19-SO-000030 Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Rename administrator account" to a name other than "Administrator". - - - + V-93281 + SV-103369 + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Rename administrator account" to a name other than "Administrator". + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -13275,25 +14049,27 @@ If the value for "Accounts: Rename administrator account" is not set to a value - + SRG-OS-000480-GPOS-00227 <GroupDescription></GroupDescription> - + WN19-SO-000040 Windows Server 2019 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 2019 + DPMS Target MS Windows Server 2019 DISA DPMS Target - Windows 2019 - 3483 + MS Windows Server 2019 + 2907 - CCI-000366 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Rename guest account" to a name other than "Guest". - - - + SV-103371 + V-93283 + CCI-000366 + Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Rename guest account" to a name other than "Guest". + + + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". @@ -13302,230 +14078,6 @@ Navigate to Local Computer Policy >> Computer Configuration >> Windo If the value for "Accounts: Rename guest account" is not set to a value other than "Guest", this is a finding. - - - - - - SRG-OS-000069-GPOS-00037 - <GroupDescription></GroupDescription> - - WN19-AC-000080 - Windows Server 2019 must have the built-in Windows password complexity policy 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 three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. - -Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101</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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000192 - CCI-000193 - CCI-000194 - CCI-001619 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Password must meet complexity requirements" to "Enabled". - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding. - - - - - - - SRG-OS-000078-GPOS-00046 - <GroupDescription></GroupDescription> - - WN19-AC-000070 - Windows Server 2019 minimum password length must be configured to 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000205 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password length" to "14" characters. - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for the "Minimum password length," is less than "14" characters, this is a finding. - - - - - - - SRG-OS-000073-GPOS-00041 - <GroupDescription></GroupDescription> - - WN19-AC-000090 - Windows Server 2019 reversible password encryption must be disabled. - <VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. 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></IAControls> - - DPMS Target Windows 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000196 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Store passwords using reversible encryption" to "Disabled". - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for "Store passwords using reversible encryption" is not set to "Disabled", this is a finding. - - - - - - - SRG-OS-000075-GPOS-00043 - <GroupDescription></GroupDescription> - - WN19-AC-000060 - Windows Server 2019 minimum password age must be configured to at least one day. - <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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000198 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password age" to at least "1" day. - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for the "Minimum password age" is set to "0" days ("Password can be changed immediately"), this is a finding. - - - - - - - SRG-OS-000076-GPOS-00044 - <GroupDescription></GroupDescription> - - WN19-AC-000050 - Windows Server 2019 maximum password age must be configured to 60 days or less. - <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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000199 - Configure 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). - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - - - - - - - SRG-OS-000077-GPOS-00045 - <GroupDescription></GroupDescription> - - WN19-AC-000040 - Windows Server 2019 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 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000200 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Enforce password history" to "24" passwords remembered. - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding. - - - - - - - SRG-OS-000121-GPOS-00062 - <GroupDescription></GroupDescription> - - WN19-SO-000010 - Windows Server 2019 must have the built-in guest account disabled. - <VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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 2019 - DISA - DPMS Target - Windows 2019 - 3483 - - CCI-000804 - Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Guest account status" to "Disabled". - - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. - -If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. - diff --git a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_STIG_V1R5_Manual-xccdf.xml b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_STIG_V1R5_Manual-xccdf.xml deleted file mode 100644 index 13c9e3533..000000000 --- a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_STIG_V1R5_Manual-xccdf.xml +++ /dev/null @@ -1,6642 +0,0 @@ -acceptedWindows Server 2019 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 5 Benchmark Date: 17 Jun 20201I - 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>SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>WN19-SO-000120Windows Server 2019 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver.<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. - -Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</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 2019DISADPMS TargetWindows 20193483CCI-000056CCI-000057CCI-000060Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Interactive logon: Machine inactivity limit" to "900" seconds or less, excluding "0" which is effectively 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\Microsoft\Windows\CurrentVersion\Policies\System\ - -Value Name: InactivityTimeoutSecs - -Value Type: REG_DWORD -Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled)SRG-OS-000297-GPOS-00115<GroupDescription></GroupDescription>WN19-DC-000410Windows Server 2019 Deny log on through Remote Desktop Services user right on domain controllers must be configured to prevent unauthenticated access.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. - -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 2019DISADPMS TargetWindows 20193483CCI-002314Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on through Remote Desktop Services" to include the following: - -- Guests GroupThis applies to domain controllers. A separate version applies to other systems. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: - -- Guests Group - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If the following SID(s) are not defined for the "SeDenyRemoteInteractiveLogonRight" user right, this is a finding. - -S-1-5-32-546 (Guests)SRG-OS-000297-GPOS-00115<GroupDescription></GroupDescription>WN19-MS-000120Windows Server 2019 Deny log on through Remote Desktop Services user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and all local accounts and from 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" user right defines the accounts that are prevented from logging on using Remote Desktop Services. - -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 2019DISADPMS TargetWindows 20193483CCI-002314Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on through Remote Desktop Services" to include the following: - -Domain Systems Only: -- Enterprise Admins group -- Domain Admins group -- Local account (see Note below) - -All Systems: -- Guests group - -Note: "Local account" is referring to the Windows built-in security group.This applies to member servers and standalone systems. A separate version applies to domain controllers. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: - -Domain Systems Only: -- Enterprise Admins group -- Domain Admins group -- Local account (see Note below) - -All Systems: -- Guests group - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If the following SIDs are not defined for the "SeDenyRemoteInteractiveLogonRight" user right, this is a finding. - -Domain Systems Only: -S-1-5-root domain-519 (Enterprise Admins) -S-1-5-domain-512 (Domain Admins) -S-1-5-113 ("Local account") - -All Systems: -S-1-5-32-546 (Guests) - -Note: "Local account" is referring to the Windows built-in security group.SRG-OS-000032-GPOS-00013<GroupDescription></GroupDescription>WN19-AU-000190Windows Server 2019 must be configured to audit 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. - -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000032-GPOS-00013<GroupDescription></GroupDescription>WN19-AU-000200Windows Server 2019 must be configured to audit 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. - -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - FailureSRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>WN19-CC-000370Windows Server 2019 Remote Desktop Services must require secure Remote Procedure Call (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. - -Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</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 2019DISADPMS TargetWindows 20193483CCI-000068CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ - -Value Name: fEncryptRPCTraffic - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>WN19-CC-000380Windows Server 2019 Remote Desktop Services must be configured with the client connection encryption set to High 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. - -Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</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 2019DISADPMS TargetWindows 20193483CCI-000068CCI-001453Configure 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" with "High Level" 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 NT\Terminal Services\ - -Value Name: MinEncryptionLevel - -Type: REG_DWORD -Value: 0x00000003 (3)SRG-OS-000002-GPOS-00002<GroupDescription></GroupDescription>WN19-00-000300Windows Server 2019 must automatically remove or disable temporary user accounts after 72 hours.<VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. - -Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. - -If temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. - -To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</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 2019DISADPMS TargetWindows 20193483CCI-000016Configure temporary user accounts to automatically expire within 72 hours. - -Domain accounts can be configured with an account expiration date, under "Account" properties. - -Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. - -Delete any temporary user accounts that are no longer necessary.Review temporary user accounts for expiration dates. - -Determine if temporary user accounts are used and identify any that exist. If none exist, this is NA. - -Domain Controllers: - -Open "PowerShell". - -Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". - -If "AccountExpirationDate" has not been defined within 72 hours for any temporary user account, this is a finding. - -Member servers and standalone systems: - -Open "Command Prompt". - -Run "Net user [username]", where [username] is the name of the temporary user account. - -If "Account expires" has not been defined within 72 hours for any temporary user account, this is a finding.SRG-OS-000123-GPOS-00064<GroupDescription></GroupDescription>WN19-00-000310Windows Server 2019 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours.<VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. - -Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. - -To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</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 2019DISADPMS TargetWindows 20193483CCI-001682Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours. - -Domain accounts can be configured with an account expiration date, under "Account" properties. - -Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account.Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. - -If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. - -If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. - -Domain Controllers: - -Open "PowerShell". - -Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". - -If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. - -Member servers and standalone systems: - -Open "Command Prompt". - -Run "Net user [username]", where [username] is the name of the emergency account. - -If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>WN19-AU-000100Windows Server 2019 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 security groups, including changes in group members. - -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019DISADPMS TargetWindows 20193483CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>WN19-AU-000110Windows Server 2019 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. - -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019DISADPMS TargetWindows 20193483CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>WN19-AU-000120Windows Server 2019 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. - -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019DISADPMS TargetWindows 20193483CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - FailureSRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>WN19-DC-000230Windows Server 2019 must be configured to audit Account Management - Computer 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. - -Computer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts. - -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</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 2019DISADPMS TargetWindows 20193483CCI-000018CCI-000172CCI-001403CCI-001404CCI-001405CCI-002130Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Management >> "Audit Computer Account Management" with "Success" selected.This applies to domain controllers. It is NA for other systems. - -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Computer Account Management - SuccessSRG-OS-000240-GPOS-00090<GroupDescription></GroupDescription>WN19-AU-000150Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. - -Account Lockout events can be used to identify potentially malicious logon attempts. - -Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-001404Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Account Lockout - SuccessSRG-OS-000240-GPOS-00090<GroupDescription></GroupDescription>WN19-AU-000160Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. - -Account Lockout events can be used to identify potentially malicious logon attempts. - -Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-001404Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Account Lockout - FailureSRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-00-000130Windows Server 2019 local volumes must use a format that supports NTFS attributes.<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 a file system that supports NTFS attributes.</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 2019DISADPMS TargetWindows 20193483CCI-000213Format volumes to use NTFS or ReFS.Open "Computer Management". - -Select "Disk Management" under "Storage". - -For each local volume, if the file system does not indicate "NTFS", this is a finding. - -"ReFS" (resilient file system) is also acceptable and would not be a finding. - -This does not apply to system partitions such the Recovery and EFI System Partition.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-00-000180Windows Server 2019 non-administrative accounts or groups must only have print permissions on printer shares.<VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</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 2019DISADPMS TargetWindows 20193483CCI-000213Configure the permissions on shared printers to restrict standard users to only have Print permissions.Open "Printers & scanners" in "Settings". - -If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) - -For each printer: - -Select the printer and "Manage". - -Select "Printer Properties". - -Select the "Sharing" tab. - -If "Share this printer" is checked, select the "Security" tab. - -If any standard user accounts or groups have permissions other than "Print", this is a finding. - -The default is for the "Everyone" group to be given "Print" permission. - -"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000340Windows Server 2019 Access this computer from the network user right must only be assigned to the Administrators, Authenticated Users, and -Enterprise Domain Controllers groups on domain controllers.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -Accounts with the "Access this computer from the network" right may access resources on the system, and this right must be limited to those requiring it.</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 2019DISADPMS TargetWindows 20193483CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Access this computer from the network" to include only the following accounts or groups: - -- Administrators -- Authenticated Users -- Enterprise Domain ControllersThis applies to domain controllers. It is NA for other systems. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If any accounts or groups other than the following are granted the "Access this computer from the network" right, this is a finding. - -- Administrators -- Authenticated Users -- Enterprise Domain Controllers - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeNetworkLogonRight" user right, this is a finding. - -S-1-5-32-544 (Administrators) -S-1-5-11 (Authenticated Users) -S-1-5-9 (Enterprise Domain Controllers) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000360Windows Server 2019 Allow log on through Remote Desktop Services user right must only be assigned to the Administrators group on domain controllers.<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 2019DISADPMS TargetWindows 20193483CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on through Remote Desktop Services" to include only the following accounts or groups: - -- AdministratorsThis applies to domain controllers, it is NA for other systems. - -Verify the effective setting in Local Group Policy Editor. -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If any accounts or groups other than the following are granted the "Allow log on through Remote Desktop Services" user right, this is a finding. - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeRemoteInteractiveLogonRight" user right, this is a finding. - -S-1-5-32-544 (Administrators)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000370Windows Server 2019 Deny access to this computer from the network user right on domain controllers must be configured to prevent unauthenticated access.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -The "Deny access to this computer from the network" user right defines the accounts that are prevented from logging on from the network. - -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 2019DISADPMS TargetWindows 20193483CCI-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: - -- Guests GroupThis applies to domain controllers. A separate version applies to other systems. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding: - -- Guests Group - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If the following SIDs are not defined for the "SeDenyNetworkLogonRight" user right, this is a finding. - -S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000380Windows Server 2019 Deny log on as a batch job user right on domain controllers must be configured to prevent unauthenticated access.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -The "Deny log on as a batch job" user right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler. - -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 2019DISADPMS TargetWindows 20193483CCI-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: - -- Guests GroupThis applies to domain controllers. A separate version applies to other systems. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding: - -- Guests Group - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If the following SID(s) are not defined for the "SeDenyBatchLogonRight" user right, this is a finding: - -S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000390Windows Server 2019 Deny log on as a service user right must be configured to include no accounts or groups (blank) on domain controllers.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -The "Deny log on as a service" user right defines accounts that are denied logon as a service. - -Incorrect configurations could prevent services from starting and result in a denial of 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 2019DISADPMS TargetWindows 20193483CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on as a service" to include no entries (blank).This applies to domain controllers. A separate version applies to other systems. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If any accounts or groups are defined for the "Deny log on as a service" user right, this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs are granted the "SeDenyServiceLogonRight" user right, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000400Windows Server 2019 Deny log on locally user right on domain controllers must be configured to prevent unauthenticated access.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -The "Deny log on locally" user right defines accounts that are prevented from logging on interactively. - -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 2019DISADPMS TargetWindows 20193483CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on locally" to include the following: - -- Guests GroupThis applies to domain controllers. A separate version applies to other systems. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: - -- Guests Group - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If the following SID(s) are not defined for the "SeDenyInteractiveLogonRight" user right, this is a finding: - -S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000070Windows Server 2019 Access this computer from the network user right must only be assigned to the Administrators and Authenticated Users groups on domain-joined member servers and standalone systems.<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 this right must be limited to those requiring it.</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 2019DISADPMS TargetWindows 20193483CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Access this computer from the network" to include only the following accounts or groups: - -- Administrators -- Authenticated UsersThis applies to member servers and standalone systems. A separate version applies to domain controllers. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators -- Authenticated Users - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeNetworkLogonRight" user right, this is a finding: - -S-1-5-32-544 (Administrators) -S-1-5-11 (Authenticated Users) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000080Windows Server 2019 Deny access to this computer from the network user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and local accounts and from 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" user 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 2019DISADPMS TargetWindows 20193483CCI-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 and member of Administrators group" or "Local account" (see Note below) - -All Systems: -- Guests group - -Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering.This applies to member servers and standalone systems. A separate version applies to domain controllers. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding: - -Domain Systems Only: -- Enterprise Admins group -- Domain Admins group -- "Local account and member of Administrators group" or "Local account" (see Note below) - -All Systems: -- Guests group - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If the following SIDs are not defined for the "SeDenyNetworkLogonRight" user right, this is a finding. - -Domain Systems Only: -S-1-5-root domain-519 (Enterprise Admins) -S-1-5-domain-512 (Domain Admins) -S-1-5-114 ("Local account and member of Administrators group") or S-1-5-113 ("Local account") - -All Systems: -S-1-5-32-546 (Guests) - -Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000090Windows Server 2019 Deny log on as a batch job user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from 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" user 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 2019DISADPMS TargetWindows 20193483CCI-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 Admins Group -- Domain Admins Group - -All Systems: -- Guests GroupThis applies to member servers and standalone systems. A separate version applies to domain controllers. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding: - -Domain Systems Only: -- Enterprise Admins Group -- Domain Admins Group - -All Systems: -- Guests Group - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If the following SIDs are not defined for the "SeDenyBatchLogonRight" user right, this is a finding. - -Domain Systems Only: -S-1-5-root domain-519 (Enterprise Admins) -S-1-5-domain-512 (Domain Admins) - -All Systems: -S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000100Windows Server 2019 Deny log on as a service user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts. No other groups or accounts must be assigned this right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -The "Deny log on as a service" user right defines accounts that are denied logon 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 denial of 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 2019DISADPMS TargetWindows 20193483CCI-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: - -Domain systems: -- Enterprise Admins Group -- Domain Admins GroupThis applies to member servers and standalone systems. A separate version applies to domain controllers. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on as a service" user right on domain-joined systems, this is a finding: - -- Enterprise Admins Group -- Domain Admins Group - -If any accounts or groups are defined for the "Deny log on as a service" user right on non-domain-joined systems, this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If the following SIDs are not defined for the "SeDenyServiceLogonRight" user right on domain-joined systems, this is a finding: - -S-1-5-root domain-519 (Enterprise Admins) -S-1-5-domain-512 (Domain Admins) - -If any SIDs are defined for the user right on non-domain-joined systems, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000110Windows Server 2019 Deny log on locally user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from 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" user 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 2019DISADPMS TargetWindows 20193483CCI-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 - -All Systems: -- Guests GroupThis applies to member servers and standalone systems. A separate version applies to domain controllers. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: - -Domain Systems Only: -- Enterprise Admins Group -- Domain Admins Group - -All Systems: -- Guests Group - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If the following SIDs are not defined for the "SeDenyInteractiveLogonRight" user right, this is a finding: - -Domain Systems Only: -S-1-5-root domain-519 (Enterprise Admins) -S-1-5-domain-512 (Domain Admins) - -All Systems: -S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-UR-000030Windows Server 2019 Allow log on locally user right must only be assigned to the Administrators group.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on locally" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeInteractiveLogonRight" user right, this is a finding: - -S-1-5-32-544 (Administrators) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000312-GPOS-00122<GroupDescription></GroupDescription>WN19-00-000140Windows Server 2019 permissions for the system drive root directory (usually C:\) 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. - -The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). - -Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</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 2019DISADPMS TargetWindows 20193483CCI-002165Maintain the default permissions for the system drive's root directory and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). - -Default Permissions -C:\ -Type - "Allow" for all -Inherited from - "None" for all - -Principal - Access - Applies to - -SYSTEM - Full control - This folder, subfolders, and files -Administrators - Full control - This folder, subfolders, and files -Users - Read & execute - This folder, subfolders, and files -Users - Create folders/append data - This folder and subfolders -Users - Create files/write data - Subfolders only -CREATOR OWNER - Full Control - Subfolders and files onlyThe default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). - -Review the permissions for the system drive's root directory (usually C:\). 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. - -If permissions are not as restrictive as the default permissions listed below, this is a finding. - -Viewing in File Explorer: - -View the Properties of the system drive's root directory. - -Select the "Security" tab, and the "Advanced" button. - -Default permissions: -C:\ -Type - "Allow" for all -Inherited from - "None" for all - -Principal - Access - Applies to - -SYSTEM - Full control - This folder, subfolders, and files -Administrators - Full control - This folder, subfolders, and files -Users - Read & execute - This folder, subfolders, and files -Users - Create folders/append data - This folder and subfolders -Users - Create files/write data - Subfolders only -CREATOR OWNER - Full Control - Subfolders and files only - -Alternately, use icacls: - -Open "Command Prompt (Admin)". - -Enter "icacls" followed by the directory: - -"icacls c:\" - -The following results should be displayed: - -c:\ -NT AUTHORITY\SYSTEM:(OI)(CI)(F) -BUILTIN\Administrators:(OI)(CI)(F) -BUILTIN\Users:(OI)(CI)(RX) -BUILTIN\Users:(CI)(AD) -BUILTIN\Users:(CI)(IO)(WD) -CREATOR OWNER:(OI)(CI)(IO)(F) -Successfully processed 1 files; Failed processing 0 filesSRG-OS-000312-GPOS-00122<GroupDescription></GroupDescription>WN19-00-000150Windows Server 2019 permissions for program file 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. - -The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). - -Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</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 2019DISADPMS TargetWindows 20193483CCI-002165Maintain the default permissions for the program file directories and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). - -Default permissions: -\Program Files and \Program Files (x86) -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and filesThe default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). - -Review the permissions for the program file directories (Program Files and Program Files [x86]). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. - -If permissions are not as restrictive as the default permissions listed below, this is a finding. - -Viewing in File Explorer: - -For each folder, view the Properties. - -Select the "Security" tab, and the "Advanced" button. - -Default permissions: -\Program Files and \Program Files (x86) -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files - -Alternately, use icacls: - -Open a Command prompt (admin). - -Enter "icacls" followed by the directory: - -'icacls "c:\program files"' -'icacls "c:\program files (x86)"' - -The following results should be displayed for each when entered: - -c:\program files (c:\program files (x86)) -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) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) -Successfully processed 1 files; Failed processing 0 filesSRG-OS-000312-GPOS-00122<GroupDescription></GroupDescription>WN19-00-000160Windows Server 2019 permissions for the Windows installation directory 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. - -The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). - -Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</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 2019DISADPMS TargetWindows 20193483CCI-002165Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). - -Default permissions: -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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and filesThe default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). - -Review the permissions for the Windows installation directory (usually C:\Windows). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. - -If permissions are not as restrictive as the default permissions listed below, this is a finding: - -Viewing in File Explorer: - -For each folder, view the Properties. - -Select the "Security" tab and the "Advanced" button. - -Default permissions: -\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 -ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files - -Alternately, use icacls: - -Open a Command prompt (admin). - -Enter "icacls" followed by the directory: - -"icacls c:\windows" - -The following results should be displayed for each when entered: - -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) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) -APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) -Successfully processed 1 files; Failed processing 0 filesSRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-00-000170Windows Server 2019 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained.<VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating 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 2019DISADPMS TargetWindows 20193483CCI-002235Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive. - -The default permissions of the higher-level keys are noted below. - -HKEY_LOCAL_MACHINE\SECURITY - -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -SYSTEM - Full Control - This key and subkeys -Administrators - Special - This key and subkeys - -HKEY_LOCAL_MACHINE\SOFTWARE - -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - This key and subkeys -ALL APPLICATION PACKAGES - Read - This key and subkeys - -HKEY_LOCAL_MACHINE\SYSTEM - -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - Subkeys only -ALL APPLICATION PACKAGES - Read - This key and subkeys - -Microsoft has also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID. -S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. - -If any non-privileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. - -If permissions are not as restrictive as the default permissions listed below, this is a finding: - -Run "Regedit". - -Right-click on the registry areas noted below. - -Select "Permissions" and the "Advanced" button. - -HKEY_LOCAL_MACHINE\SECURITY - -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -SYSTEM - Full Control - This key and subkeys -Administrators - Special - This key and subkeys - -HKEY_LOCAL_MACHINE\SOFTWARE - -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - This key and subkeys -ALL APPLICATION PACKAGES - Read - This key and subkeys - -HKEY_LOCAL_MACHINE\SYSTEM - -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - Subkeys only -ALL APPLICATION PACKAGES - Read - This key and subkeys - -Other examples under the noted keys may also be sampled. There may be some instances where non-privileged groups have greater than Read permission. - -Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID, this is currently not a finding. -S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 - -If the defaults have not been changed, these are not a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000010Windows Server 2019 must only allow administrators responsible for the domain controller to 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 using only accounts with the minimum level of authority necessary. - -Standard user accounts must not be members of the built-in 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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the Administrators group to include only administrator groups or accounts that are responsible for the system. - -Remove any standard user accounts.This applies to domain controllers. A separate version applies to other systems. - -Review the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group. - -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. - -If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000070Windows Server 2019 permissions on the Active Directory data files must only allow System and Administrators access.<VulnDiscussion>Improper access permissions for directory data-related files could allow unauthorized users to read, modify, or delete directory data or audit trails.</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 2019DISADPMS TargetWindows 20193483CCI-002235Maintain the permissions on NTDS database and log files as follows: - -NT AUTHORITY\SYSTEM:(I)(F) -BUILTIN\Administrators:(I)(F) - -(I) - permission inherited from parent container -(F) - full accessThis applies to domain controllers. It is NA for other systems. - -Run "Regedit". - -Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". - -Note the directory locations in the values for: - -Database log files path -DSA Database file - -By default, they will be \Windows\NTDS. - -If the locations are different, the following will need to be run for each. - -Open "Command Prompt (Admin)". - -Navigate to the NTDS directory (\Windows\NTDS by default). - -Run "icacls *.*". - -If the permissions on each file are not as restrictive as the following, this is a finding: - -NT AUTHORITY\SYSTEM:(I)(F) -BUILTIN\Administrators:(I)(F) - -(I) - permission inherited from parent container -(F) - full accessSRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000080Windows Server 2019 Active Directory SYSVOL directory must have the proper access control permissions.<VulnDiscussion>Improper access permissions for directory data files could allow unauthorized users to read, modify, or delete directory data. - -The SYSVOL directory contains public files (to the domain) such as policies and logon scripts. Data in shared subdirectories are replicated to all domain controllers in a 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 2019DISADPMS TargetWindows 20193483CCI-002235Maintain the permissions on the SYSVOL directory. Do not allow greater than "Read & execute" permissions for standard user accounts or groups. The defaults below meet this requirement: - -C:\Windows\SYSVOL -Type - "Allow" for all -Inherited from - "None" for all - -Principal - Access - Applies to - -Authenticated Users - Read & execute - This folder, subfolder, and files -Server Operators - Read & execute- This folder, subfolder, and files -Administrators - Special - This folder only (Special = Basic Permissions: all selected except Full control) -CREATOR OWNER - Full control - Subfolders and files only -Administrators - Full control - Subfolders and files only -SYSTEM - Full control - This folder, subfolders, and filesThis applies to domain controllers. It is NA for other systems. - -Open a command prompt. - -Run "net share". - -Make note of the directory location of the SYSVOL share. - -By default, this will be \Windows\SYSVOL\sysvol. For this requirement, permissions will be verified at the first SYSVOL directory level. - -If any standard user accounts or groups have greater than "Read & execute" permissions, this is a finding. - -The default permissions noted below meet this requirement: - -Open "Command Prompt". - -Run "icacls c:\Windows\SYSVOL". - -The following results should be displayed: - -NT AUTHORITY\Authenticated Users:(RX) -NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(GR,GE) -BUILTIN\Server Operators:(RX) -BUILTIN\Server Operators:(OI)(CI)(IO)(GR,GE) -BUILTIN\Administrators:(M,WDAC,WO) -BUILTIN\Administrators:(OI)(CI)(IO)(F) -NT AUTHORITY\SYSTEM:(F) -NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) -CREATOR OWNER:(OI)(CI)(IO)(F) - -(RX) - Read & execute - -Run "icacls /help" to view definitions of other permission codes. - -Alternately, open "File Explorer". - -Navigate to \Windows\SYSVOL (or the directory noted previously if different). - -Right-click the directory and select properties. - -Select the "Security" tab and click "Advanced". - -Default permissions: - -C:\Windows\SYSVOL -Type - "Allow" for all -Inherited from - "None" for all - -Principal - Access - Applies to - -Authenticated Users - Read & execute - This folder, subfolder, and files -Server Operators - Read & execute- This folder, subfolder, and files -Administrators - Special - This folder only (Special = Basic Permissions: all selected except Full control) -CREATOR OWNER - Full control - Subfolders and files only -Administrators - Full control - Subfolders and files only -SYSTEM - Full control - This folder, subfolders, and filesSRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000090Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions.<VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems relying on the directory service. - -For Active Directory (AD), the Group Policy objects require special attention. In a distributed administration model (i.e., help desk), Group Policy objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for Group Policy objects, this could allow an intruder to change the security policy applied to all domain client computers (workstations and servers).</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 2019DISADPMS TargetWindows 20193483CCI-002235Maintain the permissions on Group Policy objects to not allow greater than "Read" and "Apply group policy" for standard user accounts or groups. The default permissions below meet this requirement: - -Authenticated Users - Read, Apply group policy, Special permissions - -The special permissions for Authenticated Users are for Read-type Properties. - -CREATOR OWNER - Special permissions -SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions -Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions - -Document any other access permissions that allow the objects to be updated with the ISSO. - -The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on created Group Policy objects.This applies to domain controllers. It is NA for other systems. - -Review the permissions on Group Policy objects. - -Open "Group Policy Management" (available from various menus or run "gpmc.msc"). - -Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). - -For each Group Policy object: - -Select the Group Policy object item in the left pane. - -Select the "Delegation" tab in the right pane. - -Select the "Advanced" button. - -Select each Group or user name. - -View the permissions. - -If any standard user accounts or groups have "Allow" permissions greater than "Read" and "Apply group policy", this is a finding. - -Other access permissions that allow the objects to be updated are considered findings unless specifically documented by the ISSO. - -The default permissions noted below satisfy this requirement. - -The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next "Advanced" button, the desired Permission entry, and the "Edit" button. - -Authenticated Users - Read, Apply group policy, Special permissions - -The special permissions for Authenticated Users are for Read-type Properties. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. - -The special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties: - -CREATOR OWNER - Special permissions -SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions -Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions - -The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on organization created Group Policy objects.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000100Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions.<VulnDiscussion>When Active Directory objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. - -The Domain Controllers OU object requires special attention as the Domain Controllers are central to the configuration and management of the domain. Inappropriate access permissions defined for the Domain Controllers OU could allow an intruder or unauthorized personnel to make changes that could lead to the compromise of 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 2019DISADPMS TargetWindows 20193483CCI-002235Limit the permissions on the Domain Controllers OU to restrict changes to System, Domain Admins, Enterprise Admins and Administrators. - -The default permissions listed below satisfy this requirement. - -Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions. - -CREATOR OWNER - Special permissions - -SELF - Special permissions - -Authenticated Users - Read, Special permissions - -The special permissions for Authenticated Users are Read types. - -SYSTEM - Full Control - -Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions - -Enterprise Admins - Full Control - -Key Admins - Special permissions - -Enterprise Key Admins - Special permissions - -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions - -Pre-Windows 2000 Compatible Access - Special permissions - -The special permissions for Pre-Windows 2000 Compatible Access are Read types. - -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissionsThis applies to domain controllers. It is NA for other systems. - -Review the permissions on the Domain Controllers OU. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Select "Advanced Features" in the "View" menu if not previously selected. - -Select the "Domain Controllers" OU (folder in folder icon). - -Right-click and select "Properties". - -Select the "Security" tab. - -If the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding. - -The default permissions listed below satisfy this requirement. - -Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions and are not a finding. - -The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "View" or "Edit" button. - -Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. - -CREATOR OWNER - Special permissions - -SELF - Special permissions - -Authenticated Users - Read, Special permissions - -The special permissions for Authenticated Users are Read types. - -If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. - -SYSTEM - Full Control - -Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions - -Enterprise Admins - Full Control - -Key Admins - Special permissions - -Enterprise Key Admins - Special permissions - -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions - -Pre-Windows 2000 Compatible Access - Special permissions - -The Special permissions for Pre-Windows 2000 Compatible Access are Read types. - -If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. - -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissionsSRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000110Windows Server 2019 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions.<VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. - -For Active Directory, the OU objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a denial of service (DoS) to authorized users.</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 2019DISADPMS TargetWindows 20193483CCI-002235Maintain the Allow type permissions on domain-defined OUs to be at least as restrictive as the defaults below. - -Document any additional permissions above Read with the ISSO if an approved distributed administration model (help desk or other user support staff) is implemented. - -CREATOR OWNER - Special permissions - -Self - Special permissions - -Authenticated Users - Read, Special permissions - -The special permissions for Authenticated Users are Read type. - -SYSTEM - Full Control - -Domain Admins - Full Control - -Enterprise Admins - Full Control - -Key Admins - Special permissions - -Enterprise Key Admins - Special permissions - -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions - -Pre-Windows 2000 Compatible Access - Special permissions - -The special permissions for Pre-Windows 2000 Compatible Access are for Read types. - -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissionsThis applies to domain controllers. It is NA for other systems. - -Review the permissions on domain-defined OUs. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -For each OU that is defined (folder in folder icon) excluding the Domain Controllers OU: - -Right-click the OU and select "Properties". - -Select the "Security" tab. - -If the Allow type permissions on the OU are not at least as restrictive as those below, this is a finding. - -The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "Edit" or "View" button. - -Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. - -CREATOR OWNER - Special permissions - -Self - Special permissions - -Authenticated Users - Read, Special permissions - -The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. - -SYSTEM - Full Control - -Domain Admins - Full Control - -Enterprise Admins - Full Control - -Key Admins - Special permissions - -Enterprise Key Admins - Special permissions - -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions - -Pre-Windows 2000 Compatible Access - Special permissions - -The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. - -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions - -If an ISSO-approved distributed administration model (help desk or other user support staff) is implemented, permissions above Read may be allowed for groups documented by the ISSO. - -If any OU with improper permissions includes identification or authentication data (e.g., accounts, passwords, or password hash data) used by systems to determine access control, the severity is CAT I (e.g., OUs that include user accounts, including service/application accounts). - -If an OU with improper permissions does not include identification and authentication data used by systems to determine access control, the severity is CAT II (e.g., Workstation, Printer OUs).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000350Windows Server 2019 Add workstations to domain user right must only be assigned to the Administrators group on domain controllers.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -Accounts with the "Add workstations to domain" right may add computers to a domain. This could result in unapproved or incorrectly configured systems being added to a 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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Add workstations to domain" to include only the following accounts or groups: - -- AdministratorsThis applies to domain controllers. It is NA for other systems. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If any accounts or groups other than the following are granted the "Add workstations to domain" right, this is a finding. - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeMachineAccountPrivilege" user right, this is a finding. - -S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000420Windows Server 2019 Enable computer and user accounts to be trusted for delegation user right must only be assigned to the Administrators group on domain controllers.<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 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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 include only the following accounts or groups: - -- AdministratorsThis applies to domain controllers. A separate version applies to other systems. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If any accounts or groups other than the following are granted the "Enable computer and user accounts to be trusted for delegation" user right, this is a finding. - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeEnableDelegationPrivilege" user right, this is a finding. - -S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-MS-000010Windows Server 2019 must only allow administrators responsible for the member server or standalone system to 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 using only accounts with the minimum level of authority necessary. - -For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group (see V-36433 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. - -Standard user accounts must not be members of the built-in 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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the local "Administrators" group to include only administrator groups or accounts responsible for administration of the system. - -For domain-joined member servers, replace the Domain Admins group with a domain member server administrator group. - -Remove any standard user accounts.This applies to member servers and standalone systems. A separate version applies to domain controllers. - -Open "Computer Management". - -Navigate to "Groups" under "Local Users and Groups". - -Review the local "Administrators" group. - -Only administrator groups or accounts responsible for administration of the system may be members of the group. - -For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group. - -Standard user accounts must not be members of the local Administrator group. - -If accounts that do not have responsibility for administration of the system are members of the local Administrators group, this is a finding. - -If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-MS-000060Windows Server 2019 must restrict remote calls to the Security Account Manager (SAM) to Administrators on domain-joined member servers and standalone systems.<VulnDiscussion>The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.</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 2019DISADPMS TargetWindows 20193483CCI-002235Navigate to the policy Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Restrict clients allowed to make remote calls to SAM". -Select "Edit Security" to configure the "Security descriptor:". - -Add "Administrators" in "Group or user names:" if it is not already listed (this is the default). - -Select "Administrators" in "Group or user names:". - -Select "Allow" for "Remote Access" in "Permissions for "Administrators". - -Click "OK". - -The "Security descriptor:" must be populated with "O:BAG:BAD:(A;;RC;;;BA) for the policy to be enforced.This applies to member servers and standalone systems; it is NA for domain controllers. - -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\Lsa\ - -Value Name: RestrictRemoteSAM - -Value Type: REG_SZ -Value: O:BAG:BAD:(A;;RC;;;BA)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-MS-000130Windows Server 2019 Enable computer and user accounts to be trusted for delegation user right must not be assigned to any groups or accounts on domain-joined member servers and standalone systems.<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 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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).This applies to member servers and standalone systems. A separate version applies to domain controllers. - -Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs are granted the "SeEnableDelegationPrivilege" user right, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000010Windows Server 2019 Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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).Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs are granted the "SeTrustedCredManAccessPrivilege" user right, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000020Windows Server 2019 Act as part of the operating system user right must not be assigned to any groups or accounts.<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 the 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 2019DISADPMS TargetWindows 20193483CCI-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).Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs are granted the "SeTcbPrivilege" user right, this is a finding. - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060). - -Passwords for accounts with this user right must be protected as highly privileged accounts.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000040Windows Server 2019 Back up files and directories user right must only be assigned to the Administrators group.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Back up files and directories" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeBackupPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000050Windows Server 2019 Create a pagefile user right must only be assigned to the Administrators group.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create a pagefile" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeCreatePagefilePrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000060Windows Server 2019 Create a token object user right must not be assigned to any groups or accounts.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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).Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If any accounts or groups are granted the "Create a token object" user right, this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs are granted the "SeCreateTokenPrivilege" user right, this is a finding. - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060). - -Passwords for application accounts with this user right must be protected as highly privileged accounts.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000070Windows Server 2019 Create global objects user right must only be assigned to Administrators, Service, Local Service, and Network Service.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create global objects" to include only the following accounts or groups: - -- Administrators -- Service -- Local Service -- Network ServiceVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 Service - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeCreateGlobalPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators) -S-1-5-6 (Service) -S-1-5-19 (Local Service) -S-1-5-20 (Network Service) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000080Windows Server 2019 Create permanent shared objects user right must not be assigned to any groups or accounts.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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).Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If any accounts or groups are granted the "Create permanent shared objects" user right, this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs are granted the "SeCreatePermanentPrivilege" user right, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000090Windows Server 2019 Create symbolic links user right must only be assigned to the Administrators group.<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 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create symbolic links" to include only the following accounts or groups: - -- Administrators - -Systems that have the Hyper-V role will also have "Virtual Machines" given this user right. If this needs to be added manually, enter it as "NT Virtual Machine\Virtual Machines".Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeCreateSymbolicLinkPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators) - -Systems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines", SID S-1-5-83-0). This is not a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000100Windows Server 2019 Debug programs: user right must only be assigned to the Administrators group.<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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Debug programs" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeDebugPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060). - -Passwords for application accounts with this user right must be protected as highly privileged accounts.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000110Windows Server 2019 Force shutdown from a remote system user right must only be assigned to the Administrators group.<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 denial of 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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Force shutdown from a remote system" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeRemoteShutdownPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000120Windows Server 2019 Generate security audits user right must only be assigned to Local Service and Network Service.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Generate security audits" to include only the following accounts or groups: - -- Local Service -- Network ServiceVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 Service - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeAuditPrivilege" user right, this is a finding: - -S-1-5-19 (Local Service) -S-1-5-20 (Network Service) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000130Windows Server 2019 Impersonate a client after authentication user right must only be assigned to Administrators, Service, Local Service, and Network Service.<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 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Impersonate a client after authentication" to include only the following accounts or groups: - -- Administrators -- Service -- Local Service -- Network ServiceVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 Service - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeImpersonatePrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators) -S-1-5-6 (Service) -S-1-5-19 (Local Service) -S-1-5-20 (Network Service) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000140Windows Server 2019 Increase scheduling priority: user right must only be assigned to the Administrators group.<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 denial of 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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Increase scheduling priority" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeIncreaseBasePriorityPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000150Windows Server 2019 Load and unload device drivers user right must only be assigned to the Administrators group.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. - -The "Load and unload device drivers" user right allows a user to load device drivers dynamically on a system. This could be used by an attacker to install malicious code.</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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Load and unload device drivers" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeLoadDriverPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000160Windows Server 2019 Lock pages in memory user right must not be assigned to any groups or accounts.<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 denial of 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 2019DISADPMS TargetWindows 20193483CCI-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).Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -If any accounts or groups are granted the "Lock pages in memory" user right, this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs are granted the "SeLockMemoryPrivilege" user right, this is a finding. - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000180Windows Server 2019 Modify firmware environment values user right must only be assigned to the Administrators group.<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 denial of 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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Modify firmware environment values" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeSystemEnvironmentPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000190Windows Server 2019 Perform volume maintenance tasks user right must only be assigned to the Administrators group.<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. This could be used to delete volumes, resulting in data loss or a denial of 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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Perform volume maintenance tasks" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeManageVolumePrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000200Windows Server 2019 Profile single process user right must only be assigned to the Administrators group.<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 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Profile single process" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeProfileSingleProcessPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000210Windows Server 2019 Restore files and directories user right must only be assigned to the Administrators group.<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 overwrite more current 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 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Restore files and directories" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeRestorePrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000220Windows Server 2019 Take ownership of files or other objects user right must only be assigned to the Administrators group.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Take ownership of files or other objects" to include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeTakeOwnershipPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators) - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000090Windows Server 2019 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 Events records events such as the access of a password hash or the Password Policy Checking API being called. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000140Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000260Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-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 "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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000270Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000280Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000290Windows Server 2019 must be configured to audit Policy Change - Authorization 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. - -Authorization Policy Change records events related to changes in user rights, such as "Create a token object". - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> "Audit Authorization 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Authorization Policy Change - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000300Windows Server 2019 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". - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000310Windows Server 2019 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". - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000320Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000330Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000340Windows Server 2019 must be configured to audit System - Other System 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. - -Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Other System Events - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000350Windows Server 2019 must be configured to audit System - Other System 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. - -Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Other System Events - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000360Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000370Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000380Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000390Windows Server 2019 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. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000170Windows Server 2019 Active Directory Group Policy objects must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure the audit settings for Group Policy objects to include the following: - -This can be done at the Policy level in Active Directory to apply to all group policies. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Select "Advanced Features" from the "View" Menu. - -Navigate to [Domain] >> System >> Policies in the left panel. - -Right click "Policies", select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button. - -Select the "Auditing" tab. - -Type - Fail -Principal - Everyone -Access - Full Control -Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects - -The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. - -Type - Success -Principal - Everyone -Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) -Inherited from - Parent Object -Applies to - Descendant groupPolicyContainer objects - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) -Inherited from - Parent Object -Applies to - Descendant Organization Unit ObjectsThis applies to domain controllers. It is NA for other systems. - -Review the auditing configuration for all Group Policy objects. - -Open "Group Policy Management" (available from various menus or run "gpmc.msc"). - -Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). - -For each Group Policy object: - -Select the Group Policy object item in the left pane. - -Select the "Delegation" tab in the right pane. - -Select the "Advanced" button. - -Select the "Advanced" button again and then the "Auditing" tab. - -If the audit settings for any Group Policy object are not at least as inclusive as those below, this is a finding: - -Type - Fail -Principal - Everyone -Access - Full Control -Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects - -The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. - -Type - Success -Principal - Everyone -Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) -Inherited from - Parent Object -Applies to - Descendant groupPolicyContainer objects - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) -Inherited from - Parent Object -Applies to - Descendant Organization Unit ObjectsSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000180Windows Server 2019 Active Directory Domain object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select the domain being reviewed in the left pane. - -Right-click the domain name and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -Configure the audit settings for Domain object to include the following: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - None -Applies to - Special - -Type - Success -Principal - Domain Users -Access - All extended rights -Inherited from - None -Applies to - This object only - -Type - Success -Principal - Administrators -Access - All extended rights -Inherited from - None -Applies to - This object only - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner.)This applies to domain controllers. It is NA for other systems. - -Review the auditing configuration for the Domain object. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select the domain being reviewed in the left pane. - -Right-click the domain name and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -If the audit settings on the Domain object are not at least as inclusive as those below, this is a finding: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - None -Applies to - Special - -Type - Success -Principal - Domain Users -Access - All extended rights -Inherited from - None -Applies to - This object only - -Type - Success -Principal - Administrators -Access - All extended rights -Inherited from - None -Applies to - This object only - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner)SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000190Windows Server 2019 Active Directory Infrastructure object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select the domain being reviewed in the left pane. - -Right-click the "Infrastructure" object in the right pane and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -Configure the audit settings for Infrastructure object to include the following: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain)This applies to domain controllers. It is NA for other systems. - -Review the auditing configuration for Infrastructure object. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select the domain being reviewed in the left pane. - -Right-click the "Infrastructure" object in the right pane and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -If the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain)SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000200Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select the "Domain Controllers OU" under the domain being reviewed in the left pane. - -Right-click the "Domain Controllers OU" object and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -Configure the audit settings for Domain Controllers OU object to include the following: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: all create, delete and modify permissions) - -Type - Success -Principal - Everyone -Access - Write all properties -Inherited from - None -Applies to - This object and all descendant objects - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objectsThis applies to domain controllers. It is NA for other systems. - -Review the auditing configuration for the Domain Controller OU object. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select the "Domain Controllers OU" under the domain being reviewed in the left pane. - -Right-click the "Domain Controllers OU" object and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -If the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object and all descendant objects - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: all create, delete and modify permissions) - -Type - Success -Principal - Everyone -Access - Write all properties -Inherited from - None -Applies to - This object and all descendant objects - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objectsSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000210Windows Server 2019 Active Directory AdminSDHolder object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select "System" under the domain being reviewed in the left pane. - -Right-click the "AdminSDHolder" object in the right pane and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -Configure the audit settings for AdminSDHolder object to include the following: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Write all properties, Modify permissions, Modify owner) - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objectsThis applies to domain controllers. It is NA for other systems. - -Review the auditing configuration for the "AdminSDHolder" object. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select "System" under the domain being reviewed in the left pane. - -Right-click the "AdminSDHolder" object in the right pane and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -If the audit settings on the "AdminSDHolder" object are not at least as inclusive as those below, this is a finding: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Write all properties, Modify permissions, Modify owner) - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objectsSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000220Windows Server 2019 Active Directory RID Manager$ object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select "System" under the domain being reviewed in the left pane. - -Right-click the "RID Manager$" object in the right pane and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -Configure the audit settings for RID Manager$ object to include the following: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None - (Access - Special = Write all properties, All extended rights, Change RID master) - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain)This applies to domain controllers. It is NA for other systems. - -Review the auditing configuration for the "RID Manager$" object. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select "System" under the domain being reviewed in the left pane. - -Right-click the "RID Manager$" object in the right pane and select "Properties". - -Select the "Security" tab. - -Select the "Advanced" button and then the "Auditing" tab. - -If the audit settings on the "RID Manager$" object are not at least as inclusive as those below, this is a finding: - -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None - -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. - -Type - Success -Principal - Everyone -Access - Special -Inherited from - None - (Access - Special = Write all properties, All extended rights, Change RID master) - -Two instances with the following summary information will be listed: - -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain)SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000240Windows Server 2019 must be configured to audit DS Access - Directory Service Access 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 Directory Service Access records events related to users accessing an Active Directory object. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Access" with "Success" selected.This applies to domain controllers. It is NA for other systems. - -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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. - -DS Access >> Directory Service Access - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000250Windows Server 2019 must be configured to audit DS Access - Directory Service Access 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 Directory Service Access records events related to users accessing an Active Directory object. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Access" with "Failure" selected.This applies to domain controllers. It is NA for other systems. - -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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. - -DS Access >> Directory Service Access - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000260Windows Server 2019 must be configured to audit DS Access - Directory Service Changes 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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Changes" with "Success" selected.This applies to domain controllers. It is NA for other systems. - -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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. - -DS Access >> Directory Service Changes - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000270Windows Server 2019 must be configured to audit DS Access - Directory Service Changes 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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Changes" with "Failure" selected.This applies to domain controllers. It is NA for other systems. - -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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. - -DS Access >> Directory Service Changes - FailureSRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>WN19-AC-000020Windows Server 2019 must have the number of allowed bad logon attempts configured to three or less.<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 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 2019DISADPMS TargetWindows 20193483CCI-000044Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout threshold" to "3" or fewer invalid logon attempts (excluding "0", which is unacceptable).Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. - -If the "Account lockout threshold" is "0" or more than "3" attempts, this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "LockoutBadCount" equals "0" or is greater than "3" in the file, this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>WN19-AC-000030Windows Server 2019 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.<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. - -Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128</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 2019DISADPMS TargetWindows 20193483CCI-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 "15" minutes.Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. - -If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "ResetLockoutCount" is less than "15" in the file, this is a finding.SRG-OS-000329-GPOS-00128<GroupDescription></GroupDescription>WN19-AC-000010Windows Server 2019 account lockout duration must be configured to 15 minutes or greater.<VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</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 2019DISADPMS TargetWindows 20193483CCI-002238Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout duration" to "15" minutes or greater. - -A value of "0" is also acceptable, requiring an administrator to unlock the account.Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. - -If the "Account lockout duration" is less than "15" minutes (excluding "0"), this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "LockoutDuration" is less than "15" (excluding "0") in the file, this is a finding. - -Configuring this to "0", requiring an administrator to unlock the account, is more restrictive and is not a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>WN19-SO-000130Windows Server 2019 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. - -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</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 2019DISADPMS TargetWindows 20193483CCI-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.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: LegalNoticeText - -Value Type: REG_SZ -Value: See message text below - -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.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>WN19-SO-000140Windows Server 2019 title for legal banner dialog box must be configured with the appropriate text.<VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. - -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</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 2019DISADPMS TargetWindows 20193483CCI-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 an organization-defined equivalent. - -If an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN19-SO-000150.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: LegalNoticeCaption - -Value Type: REG_SZ -Value: See message title options below - -"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. - -If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. - -Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required.SRG-OS-000062-GPOS-00031<GroupDescription></GroupDescription>WN19-SO-000050Windows Server 2019 must force audit policy subcategory settings to override audit policy category settings.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".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\Lsa\ - -Value Name: SCENoApplyLegacyAuditPolicy - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000070Windows Server 2019 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000080Windows Server 2019 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - FailureSRG-OS-000474-GPOS-00219<GroupDescription></GroupDescription>WN19-AU-000130Windows Server 2019 must be configured to audit Detailed Tracking - Plug and Play 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. - -Plug and Play activity records events related to the successful connection of external devices.</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 2019DISADPMS TargetWindows 20193483CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> "Audit PNP Activity" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Plug and Play Events - SuccessSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000170Windows Server 2019 must be configured to audit Logon/Logoff - Group Membership 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 Group Membership records information related to the group membership of a user's logon token.</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 2019DISADPMS TargetWindows 20193483CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Group Membership" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Group Membership - SuccessSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000210Windows Server 2019 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 that have administrative privileges and can be used to elevate processes. - -Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</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 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000220Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. - -Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</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 2019DISADPMS TargetWindows 20193483CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Other Object Access Events - SuccessSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000230Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. - -Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</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 2019DISADPMS TargetWindows 20193483CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 >> Other Object Access Events - FailureSRG-OS-000474-GPOS-00219<GroupDescription></GroupDescription>WN19-AU-000240Windows Server 2019 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. - -Removable Storage auditing under Object Access 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - Success - -Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding.SRG-OS-000474-GPOS-00219<GroupDescription></GroupDescription>WN19-AU-000250Windows Server 2019 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. - -Removable Storage auditing under Object Access 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - Failure - -Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding.SRG-OS-000472-GPOS-00217<GroupDescription></GroupDescription>WN19-AU-000180Windows Server 2019 must be configured to audit 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. - -Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</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 2019DISADPMS TargetWindows 20193483CCI-000172CCI-000366Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. - -Use the "AuditPol" tool to review the current Audit Policy configuration: - -Open "PowerShell" or 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 - SuccessSRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>WN19-CC-000090Windows Server 2019 command 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 2019DISADPMS TargetWindows 20193483CCI-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: 0x00000001 (1)SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>WN19-CC-000460Windows Server 2019 PowerShell script block logging 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. - -Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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 2019DISADPMS TargetWindows 20193483CCI-000135Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> "Turn on PowerShell Script Block 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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ - -Value Name: EnableScriptBlockLogging - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>WN19-CC-000270Windows Server 2019 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 2019DISADPMS TargetWindows 20193483CCI-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 write events directly to an audit server, 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\Windows\EventLog\Application\ - -Value Name: MaxSize - -Type: REG_DWORD -Value: 0x00008000 (32768) (or greater)SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>WN19-CC-000280Windows Server 2019 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 2019DISADPMS TargetWindows 20193483CCI-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 write events directly to an audit server, 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\Windows\EventLog\Security\ - -Value Name: MaxSize - -Type: REG_DWORD -Value: 0x00030000 (196608) (or greater)SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>WN19-CC-000290Windows Server 2019 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 2019DISADPMS TargetWindows 20193483CCI-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 write events directly to an audit server, 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\Windows\EventLog\System\ - -Value Name: MaxSize - -Type: REG_DWORD -Value: 0x00008000 (32768) (or greater)SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>WN19-AU-000010Windows Server 2019 audit records must be backed up to a different system or media than the system being audited.<VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</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 2019DISADPMS TargetWindows 20193483CCI-001851Establish and implement a process for backing up log data to another system or media other than the system being audited.Determine if a process to back up log data to a different system or media than the system being audited has been implemented. - -If it has not, this is a finding.SRG-OS-000479-GPOS-00224<GroupDescription></GroupDescription>WN19-AU-000020Windows Server 2019 must, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly.<VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</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 2019DISADPMS TargetWindows 20193483CCI-001851Configure the system to, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly.Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. - -If they are not, this is a finding.SRG-OS-000355-GPOS-00143<GroupDescription></GroupDescription>WN19-00-000440The Windows Server 2019 time service must synchronize with an appropriate DoD time source.<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 2019DISADPMS TargetWindows 20193483CCI-001891Configure the system to synchronize time with an appropriate DoD time source. - -Domain-joined systems use NT5DS to synchronize time from other systems in the domain by default. - -If 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 appropriate DoD time server. - -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.Review the Windows time service configuration. - -Open an elevated "Command Prompt" (run as administrator). - -Enter "W32tm /query /configuration". - -Domain-joined systems (excluding the domain controller with the PDC emulator role): - -If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. - -Other systems: - -If systems are configured with a "Type" of "NTP", including standalone systems and the domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. - -To determine the domain controller with the PDC Emulator role: - -Open "PowerShell". - -Enter "Get-ADDomain | FT PDCEmulator".SRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>WN19-AU-000030Windows Server 2019 permissions 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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</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 2019DISADPMS TargetWindows 20193483CCI-000162CCI-000163CCI-000164Configure the permissions on the Application event log file (Application.evtx) to prevent access by non-privileged accounts. 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" folder. - -If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".Navigate to the Application event log file. - -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. - -If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: - -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full ControlSRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>WN19-AU-000040Windows Server 2019 permissions 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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</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 2019DISADPMS TargetWindows 20193483CCI-000162CCI-000163CCI-000164Configure the permissions on the Security event log file (Security.evtx) to prevent access by non-privileged accounts. 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" folder. - -If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".Navigate to the Security event log file. - -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. - -If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: - -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full ControlSRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>WN19-AU-000050Windows Server 2019 permissions 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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</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 2019DISADPMS TargetWindows 20193483CCI-000162CCI-000163CCI-000164Configure the permissions on the System event log file (System.evtx) to prevent access by non-privileged accounts. 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" folder. - -If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".Navigate to the System event log file. - -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. - -If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: - -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full ControlSRG-OS-000257-GPOS-00098<GroupDescription></GroupDescription>WN19-AU-000060Windows Server 2019 Event Viewer must be protected from unauthorized modification and deletion.<VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. - -Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. - -Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</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 2019DISADPMS TargetWindows 20193483CCI-001494CCI-001495Configure the permissions on the "Eventvwr.exe" file to prevent modification by any groups or accounts other than TrustedInstaller. The default permissions listed below satisfy this requirement: - -TrustedInstaller - Full Control -Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute - -The default location is the "%SystemRoot%\System32" folder.Navigate to "%SystemRoot%\System32". - -View the permissions on "Eventvwr.exe". - -If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. - -The default permissions below satisfy this requirement: - -TrustedInstaller - Full Control -Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & ExecuteSRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>WN19-UR-000170Windows Server 2019 Manage auditing and security log user right must only be assigned to the Administrators group.<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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</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 2019DISADPMS TargetWindows 20193483CCI-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 include only the following accounts or groups: - -- AdministratorsVerify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -- Administrators - -For server core installations, run the following command: - -Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt - -Review the text file. - -If any SIDs other than the following are granted the "SeSecurityPrivilege" user right, this is a finding: - -S-1-5-32-544 (Administrators) - -If the organization has an Auditors group, the assignment of this group to the user right would not be a finding. - -If an application requires this user right, this would not be a finding. - -Vendor documentation must support the requirement for having the user right. - -The requirement must be documented with the ISSO. - -The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000362-GPOS-00149<GroupDescription></GroupDescription>WN19-CC-000420Windows Server 2019 must prevent users 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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ - -Value Name: EnableUserControl - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000362-GPOS-00149<GroupDescription></GroupDescription>WN19-CC-000430Windows Server 2019 must disable the Windows Installer Always install with elevated privileges option.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ - -Value Name: AlwaysInstallElevated - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>WN19-00-000220Windows Server 2019 system files must be monitored for unauthorized changes.<VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code 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 2019DISADPMS TargetWindows 20193483CCI-001744Monitor the system for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools.Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. - -If system files are not monitored for unauthorized changes, this is a finding. - -A properly configured HBSS Policy Auditor 5.2 or later File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. The Asset module within HBSS does not meet this requirement.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000030Windows Server 2019 administrative accounts must 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 account. - -Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to 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. - -Whitelisting can be used to enforce the policy to ensure compliance.</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 2019DISADPMS TargetWindows 20193483CCI-000366Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. Ensure the policy is enforced. - -The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. - -If it does not, this is a finding. - -The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000040Windows Server 2019 members 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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions.If no accounts are members of the Backup Operators group, this is NA. - -Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. - -If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000060Windows Server 2019 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization.<VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account 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 2019DISADPMS TargetWindows 20193483CCI-000366Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization. - -It is recommended that system-managed service accounts be used whenever possible.Determine if manually managed application/service accounts exist. If none exist, this is NA. - -If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. - -Identify manually managed application/service accounts. - -To determine the date a password was last changed: - -Domain controllers: - -Open "PowerShell". - -Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. - -If the "PasswordLastSet" date is more than one year old, this is a finding. - - -Member servers and standalone systems: - -Open "Command Prompt". - -Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. - -If the "Password Last Set" date is more than one year old, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-DC-000430The password for the krbtgt account on a domain must be reset at least every 180 days.<VulnDiscussion>The krbtgt account acts as a service account for the Kerberos Key Distribution Center (KDC) service. The account and password are created when a domain is created and the password is typically not changed. If the krbtgt account is compromised, attackers can create valid Kerberos Ticket Granting Tickets (TGT). - -The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and the amount of time equal to or greater than the maximum Kerberos ticket lifetime, and changing again reduces the risk of 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 2019DISADPMS TargetWindows 20193483CCI-000366Reset the password for the krbtgt account a least every 180 days. The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and changing again reduces the risk of issues. Changing twice in rapid succession forces clients to re-authenticate (including application services) but is desired if a compromise is suspected. - -PowerShell scripts are available to accomplish this such as at the following link: - -https://gallery.technet.microsoft.com/Reset-the-krbtgt-account-581a9e51 - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Select "Advanced Features" in the "View" menu if not previously selected. - -Select the "Users" node. - -Right click on the krbtgt account and select "Reset password" - -Enter a password that meets password complexity requirements. - -Clear the "User must change password at next logon" check box. - -The system will automatically change this to a system-generated complex password.This requirement is applicable to domain controllers; it is NA for other systems. - -Open "Windows PowerShell". - -Enter "Get-ADUser krbtgt -Property PasswordLastSet". - -If the "PasswordLastSet" date is more than 180 days old, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000090Windows Server 2019 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use.<VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using 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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.) - -The TPM must be enabled in the firmware. - -Run "tpm.msc" for configuration options in Windows.For standalone systems, this is NA. - -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. - -Verify the system has a TPM and it is ready for use. - -Run "tpm.msc". - -Review the sections in the center pane. - -"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". - -TPM Manufacturer Information - Specific Version = 2.0 or 1.2 - -If a TPM is not found or is not ready for use, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000100Windows Server 2019 must be maintained at a supported servicing level.<VulnDiscussion>Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level 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 2019DISADPMS TargetWindows 20193483CCI-000366Update the system to a Version 1809 (Build 17763.xxx) or greater.Open "Command Prompt". - -Enter "winver.exe". - -If the "About Windows" dialog box does not display "Microsoft Windows Server Version 1809 (Build 17763.xxx)" or greater, this is a finding. - -Preview versions must not be used in a production environment.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000110Windows Server 2019 must use an anti-virus program.<VulnDiscussion>Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating 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 2019DISADPMS TargetWindows 20193483CCI-000366Install an anti-virus solution on the system.Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution. - -If there is no anti-virus solution installed on the system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000120Windows Server 2019 must have a host-based intrusion detection or prevention system.<VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to 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 2019DISADPMS TargetWindows 20193483CCI-000366Install a HIDS or HIPS on each server.Determine whether there is a HIDS or HIPS on each server. - -If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. - -A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. - -If a HIDS is not installed on the system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000240Windows Server 2019 must have software certificate installation files removed.<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 2019DISADPMS TargetWindows 20193483CCI-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 or Adobe PreFlight certificate files.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 or Adobe PreFlight certificate files. 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000420Windows Server 2019 FTP servers must be configured to prevent anonymous logons.<VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. - -Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized 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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the FTP service to prevent anonymous logons. - -Open "Internet Information Services (IIS) Manager". - -Select the server. - -Double-click "FTP Authentication". - -Select "Anonymous Authentication". - -Select "Disabled" under "Actions".If FTP is not installed on the system, this is NA. - -Open "Internet Information Services (IIS) Manager". - -Select the server. - -Double-click "FTP Authentication". - -If the "Anonymous Authentication" status is "Enabled", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000430Windows Server 2019 FTP servers must be configured to prevent access to the system drive.<VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system.If FTP is not installed on the system, this is NA. - -Open "Internet Information Services (IIS) Manager". - -Select "Sites" under the server name. - -For any sites with a Binding that lists FTP, right-click the site and select "Explore". - -If the site is not defined to a specific folder for shared FTP resources, this is a finding. - -If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000450Windows Server 2019 must have orphaned security identifiers (SIDs) removed from user rights.<VulnDiscussion>Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be established for some reason.</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 2019DISADPMS TargetWindows 20193483CCI-000366Remove any unresolved SIDs found in User Rights assignments and determined to not be for currently valid accounts or groups by removing the accounts or groups from the appropriate group policy.Review the effective User Rights setting in Local Group Policy Editor. -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. - -Review each User Right listed for any unresolved SIDs to determine whether they are valid, such as due to being temporarily disconnected from the domain. (Unresolved SIDs have the format that begins with "*S-1-".) - -If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding. - -For server core installations, run the following command: - -Secedit /export /areas USER_RIGHTS /cfg c:\path\UserRights.txt - -The results in the file identify user right assignments by SID instead of group name. Review the SIDs for unidentified ones. A list of typical SIDs \ Groups is below, search Microsoft for articles on well-known SIDs for others. - -If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding. - -SID - Group -S-1-5-11 - Authenticated Users -S-1-5-113 - Local account -S-1-5-114 - Local account and member of Administrators group -S-1-5-19 - Local Service -S-1-5-20 - Network Service -S-1-5-32-544 - Administrators -S-1-5-32-546 - Guests -S-1-5-6 - Service -S-1-5-9 - Enterprise Domain Controllers -S-1-5-domain-512 - Domain Admins -S-1-5-root domain-519 - Enterprise Admins -S-1-5-80-3139157870-2983391045-3678747466-658725712-1809340420 - NT Service\WdiServiceHostSRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000460Windows Server 2019 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS.<VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these 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 2019DISADPMS TargetWindows 20193483CCI-000366Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode.Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must run in "UEFI" mode. - -Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". - -Run "System Information". - -Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000470Windows Server 2019 must have Secure Boot enabled.<VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</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 2019DISADPMS TargetWindows 20193483CCI-000366Enable Secure Boot in the system firmware.Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must have Secure Boot enabled. - -Run "System Information". - -Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. - -On server core installations, run the following PowerShell command: - -Confirm-SecureBootUEFI - -If a value of "True" is not returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000030Windows Server 2019 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. - -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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\Services\Tcpip6\Parameters\ - -Value Name: DisableIPSourceRouting - -Type: REG_DWORD -Value: 0x00000002 (2)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000040Windows Server 2019 source routing must be configured to the highest protection level to prevent Internet Protocol (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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. - -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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\Services\Tcpip\Parameters\ - -Value Name: DisableIPSourceRouting - -Value Type: REG_DWORD -Value: 0x00000002 (2)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000050Windows Server 2019 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 the 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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" to "Disabled". - -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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\Services\Tcpip\Parameters\ - -Value Name: EnableICMPRedirect - -Value Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000070Windows Server 2019 insecure logons to an SMB server must be disabled.<VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper 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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Lanman Workstation >> "Enable insecure guest logons" 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\LanmanWorkstation\ - -Value Name: AllowInsecureGuestAuth - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000080Windows Server 2019 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares.<VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Network Provider >> "Hardened UNC Paths" to "Enabled" with at least the following configured in "Hardened UNC Paths" (click the "Show" button to display): - -Value Name: \\*\SYSVOL -Value: RequireMutualAuthentication=1, RequireIntegrity=1 - -Value Name: \\*\NETLOGON -Value: RequireMutualAuthentication=1, RequireIntegrity=1This requirement is applicable to domain-joined systems. For standalone systems, 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\Windows\NetworkProvider\HardenedPaths\ - -Value Name: \\*\NETLOGON -Value Type: REG_SZ -Value: RequireMutualAuthentication=1, RequireIntegrity=1 - -Value Name: \\*\SYSVOL -Value Type: REG_SZ -Value: RequireMutualAuthentication=1, RequireIntegrity=1 - -Additional entries would not be a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000100Windows Server 2019 must be configured to enable Remote host allows delegation of non-exportable credentials.<VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Remote host allows delegation of non-exportable 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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ - -Value Name: AllowProtectedCreds - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000110Windows Server 2019 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection.<VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Secure Boot" or "Secure Boot and DMA Protection" selected. - -A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: - -https://technet.microsoft.com/itpro/windows/keep-secure/credential-guardFor standalone systems, this is NA. - -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. - -Open "PowerShell" with elevated privileges (run as administrator). - -Enter the following: - -"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" - -If "RequiredSecurityProperties" does not include a value of "2" indicating "Secure Boot" (e.g., "{1, 2}"), this is a finding. - -If "Secure Boot and DMA Protection" is configured, "3" will also be displayed in the results (e.g., "{1, 2, 3}"). - -If "VirtualizationBasedSecurityStatus" is not a value of "2" indicating "Running", this is a finding. - -Alternately: - -Run "System Information". - -Under "System Summary", verify the following: - -If "Device Guard Virtualization based security" does not display "Running", this is a finding. - -If "Device Guard Required Security Properties" does not display "Base Virtualization Support, Secure Boot", this is a finding. - -If "Secure Boot and DMA Protection" is configured, "DMA Protection" will also be displayed (e.g., "Base Virtualization Support, Secure Boot, DMA Protection"). - -The policy settings referenced in the Fix section will configure the following registry values. However, due to hardware requirements, the registry values alone do not ensure proper function. - -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ - -Value Name: EnableVirtualizationBasedSecurity -Value Type: REG_DWORD -Value: 0x00000001 (1) - -Value Name: RequirePlatformSecurityFeatures -Value Type: REG_DWORD -Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) - -A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: - -https://technet.microsoft.com/itpro/windows/keep-secure/credential-guardSRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000130Windows Server 2019 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad.<VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000366The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). - -If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> "Boot-Start Driver Initialization Policy" to "Not Configured" or "Enabled" with any option other than "All" selected.The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000007 (7)", this is a finding. - -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ - -Value Name: DriverLoadPolicy - -Value Type: REG_DWORD -Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) - -Possible values for this setting are: -8 - Good only -1 - Good and unknown -3 - Good, unknown and bad but critical -7 - All (which includes "bad" and would be a finding)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000140Windows Server 2019 group policy objects must be reprocessed even if they have not changed.<VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Group Policy >> "Configure registry policy processing" to "Enabled" with the option "Process even if the Group Policy objects have not changed" 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\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ - -Value Name: NoGPOListChanges - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000180Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (on battery).<VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000366Configure 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 -Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ - -Value Name: DCSettingIndex - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000190Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (plugged in).<VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000366Configure 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 -Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ - -Value Name: ACSettingIndex - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000250Windows Server 2019 Telemetry must be configured to Security or Basic.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft 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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Data Collection and Preview Builds>> "Allow Telemetry" to "Enabled" with "0 - Security [Enterprise Only]" or "1 - Basic" selected in "Options".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\DataCollection\ - -Value Name: AllowTelemetry - -Type: REG_DWORD -Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000260Windows Server 2019 Windows Update must not obtain updates from other PCs on the Internet.<VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Delivery Optimization >> "Download Mode" to "Enabled" with any option except "Internet" selected. - -Acceptable selections include: - -Bypass (100) -Group (2) -HTTP only (0) -LAN (1) -Simple (99)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\DeliveryOptimization\ - -Value Name: DODownloadMode - -Value Type: REG_DWORD -Value: 0x00000000 (0) - No peering (HTTP Only) -0x00000001 (1) - Peers on same NAT only (LAN) -0x00000002 (2) - Local Network / Private group peering (Group) -0x00000063 (99) - Simple download mode, no peering (Simple) -0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) - -A value of 0x00000003 (3), Internet, is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000320Windows Server 2019 Turning 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000366The default behavior is for File Explorer heap termination on corruption to be disabled. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off heap termination on corruption" to "Not Configured" or "Disabled".The default behavior is for File Explorer heap termination on corruption to be enabled. - -If the registry Value Name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. - -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ - -Value Name: NoHeapTerminationOnCorruption - -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000330Windows Server 2019 File Explorer shell protocol must run in protected mode.<VulnDiscussion>The shell protocol will limit the set of folders that 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 2019DISADPMS TargetWindows 20193483CCI-000366The default behavior is for shell protected mode to be turned on for File Explorer. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off shell protocol protected mode" to "Not Configured" or "Disabled".The default behavior is for shell protected mode to be turned on for File Explorer. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. - -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ - -Value Name: PreXPSP2ShellProtocolBehavior - -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000390Windows Server 2019 must prevent attachments 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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ - -Value Name: DisableEnclosureDownload - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000440Windows Server 2019 users must be notified if a web-based program attempts to install software.<VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</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 2019DISADPMS TargetWindows 20193483CCI-000366The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> "Prevent Internet Explorer security prompt for Windows Installer scripts" to "Not Configured" or "Disabled".The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. - -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ - -Value Name: SafeForScripting - -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>WN19-CC-000450Windows Server 2019 must disable automatically signing in the last interactive user after a system-initiated restart.<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 2019DISADPMS TargetWindows 20193483CCI-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: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-DC-000150Windows Server 2019 directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access.<VulnDiscussion>To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory 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 2019DISADPMS TargetWindows 20193483CCI-000366Configure directory data (outside the root DSE) of a non-public directory to prevent anonymous access. - -For AD, there are multiple configuration items that could enable anonymous access. - -Changing the access permissions on the domain naming context object (from the secure defaults) could enable anonymous access. If the check procedures indicate this is the cause, the process that was used to change the permissions should be reversed. This could have been through the Windows Support Tools ADSI Edit console (adsiedit.msc). - -The dsHeuristics option is used. This is addressed in check V-8555 in the AD Forest STIG.This applies to domain controllers. It is NA for other systems. - -Open "Command Prompt" (not elevated). - -Run "ldp.exe". - -From the "Connection menu", select "Bind". - -Clear the User, Password, and Domain fields. - -Select "Simple bind" for the Bind type and click "OK". - -Confirmation of anonymous access will be displayed at the end: - -res = ldap_simple_bind_s -Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON' - -From the "Browse" menu, select "Search". - -In the Search dialog, enter the DN of the domain naming context (generally something like "dc=disaost,dc=mil") in the Base DN field. - -Clear the Attributes field and select "Run". - -Error messages should display related to Bind and user not authenticated. - -If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding. - -The following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access. - -Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. - -Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-DC-000330Windows Server 2019 domain controllers must be configured to allow reset of machine account passwords.<VulnDiscussion>Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.</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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain controller: Refuse machine account password changes" to "Disabled".This applies to domain controllers. It is NA for other systems. - -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\Services\Netlogon\Parameters\ - -Value Name: RefusePasswordChange - -Value Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-MS-000050Windows Server 2019 must limit the caching of logon credentials to four or less on domain-joined member servers.<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 2019DISADPMS TargetWindows 20193483CCI-000366Configure 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.This applies to member servers. For domain controllers and standalone systems, 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 NT\CurrentVersion\Winlogon\ - -Value Name: CachedLogonsCount - -Value Type: REG_SZ -Value: 4 (or less)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-MS-000140Windows Server 2019 must be running Credential Guard on domain-joined member servers.<VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. This authentication information, which was stored in the Local Security Authority (LSA) in previous versions of Windows, is isolated from the rest of operating system and can only be accessed by privileged system 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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Enabled with UEFI lock" selected for "Credential Guard Configuration". - -A Microsoft article on Credential Guard system requirement can be found at the following link: - -https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirementsFor domain controllers and standalone systems, this is NA. - -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. - -Open "PowerShell" with elevated privileges (run as administrator). - -Enter the following: - -"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" - -If "SecurityServicesRunning" does not include a value of "1" (e.g., "{1, 2}"), this is a finding. - -Alternately: - -Run "System Information". - -Under "System Summary", verify the following: - -If "Device Guard Security Services Running" does not list "Credential Guard", this is a finding. - -The policy settings referenced in the Fix section will configure the following registry value. However, due to hardware requirements, the registry value alone does not ensure proper function. - -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ - -Value Name: LsaCfgFlags -Value Type: REG_DWORD -Value: 0x00000001 (1) (Enabled with UEFI lock) - -A Microsoft article on Credential Guard system requirement can be found at the following link: - -https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirementsSRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000020Windows Server 2019 must prevent local accounts with blank passwords from being used 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 does 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 2019DISADPMS TargetWindows 20193483CCI-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".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\Lsa\ - -Value Name: LimitBlankPasswordUse - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000030Windows Server 2019 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 2019DISADPMS TargetWindows 20193483CCI-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".Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "NewAdministratorName" is not something other than "Administrator" in the file, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000040Windows Server 2019 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 2019DISADPMS TargetWindows 20193483CCI-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".Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "NewGuestName" is not something other than "Guest" in the file, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000100Windows Server 2019 maximum age for machine account passwords must be configured to 30 days or less.<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 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 2019DISADPMS TargetWindows 20193483CCI-000366This is the default configuration for this setting (30 days). - -Configure 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).This is the default configuration for this setting (30 days). - -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\Services\Netlogon\Parameters\ - -Value Name: MaximumPasswordAge - -Value Type: REG_DWORD -Value: 0x0000001e (30) (or less, but not 0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000150Windows Server 2019 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 2019DISADPMS TargetWindows 20193483CCI-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".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 NT\CurrentVersion\Winlogon\ - -Value Name: scremoveoption - -Value Type: REG_SZ -Value: 1 (Lock Workstation) or 2 (Force Logoff) - -If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000210Windows Server 2019 must not allow anonymous SID/Name translation.<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 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Allow anonymous SID/Name translation" to "Disabled".Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. - -If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000220Windows Server 2019 must not allow anonymous enumeration of Security Account Manager (SAM) accounts.<VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".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\Lsa\ - -Value Name: RestrictAnonymousSAM - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000240Windows Server 2019 must be configured to prevent anonymous users from having the same permissions as the Everyone group.<VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".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\Lsa\ - -Value Name: EveryoneIncludesAnonymous - -Value Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000260Windows Server 2019 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously.<VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000366Configure 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".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\LSA\ - -Value Name: UseMachineId - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000270Windows Server 2019 must prevent NTLM 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000366Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network security: Allow LocalSystem NULL session fallback" 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: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ - -Value Name: allownullsessionfallback - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000280Windows Server 2019 must prevent PKU2U authentication using online identities.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".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\LSA\pku2u\ - -Value Name: AllowOnlineID - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000310Windows Server 2019 LAN Manager authentication level must be configured 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 standalone 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".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\Lsa\ - -Value Name: LmCompatibilityLevel - -Value Type: REG_DWORD -Value: 0x00000005 (5)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000320Windows Server 2019 must be configured to at least negotiate signing for LDAP client signing.<VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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 2019DISADPMS TargetWindows 20193483CCI-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.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\Services\LDAP\ - -Value Name: LDAPClientIntegrity - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000330Windows Server 2019 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption.<VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 2019DISADPMS TargetWindows 20193483CCI-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).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\Lsa\MSV1_0\ - -Value Name: NTLMMinClientSec - -Value Type: REG_DWORD -Value: 0x20080000 (537395200)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000340Windows Server 2019 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption.<VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 2019DISADPMS TargetWindows 20193483CCI-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).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\Lsa\MSV1_0\ - -Value Name: NTLMMinServerSec - -Value Type: REG_DWORD -Value: 0x20080000 (537395200)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000370Windows Server 2019 default permissions of global system objects must be strengthened.<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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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 2019DISADPMS TargetWindows 20193483CCI-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".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\ - -Value Name: ProtectionMode - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-UC-000010Windows Server 2019 must preserve zone information when saving attachments.<VulnDiscussion>Attachments from outside sources may contain malicious code. 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 2019DISADPMS TargetWindows 20193483CCI-000366The default behavior is for Windows to mark file attachments with their zone information. - -If this needs to be corrected, configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager >> "Do not preserve zone information in file attachments" to "Not Configured" or "Disabled".The default behavior is for Windows to mark file attachments with their zone information. - -If the registry Value Name below does not exist, this is not a finding. - -If it exists and is configured with a value of "2", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. - -Registry Hive: HKEY_CURRENT_USER -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ - -Value Name: SaveZoneInformation - -Value Type: REG_DWORD -Value: 0x00000002 (2) (or if the Value Name does not exist)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000010Windows Server 2019 Exploit Protection system-level mitigation, Data Execution Prevention (DEP), must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Data Execution Prevention (DEP)", are enabled by default at the system level. DEP prevents code from being run from data-only memory pages. If this is turned off, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure Exploit Protection system-level mitigation, "Data Execution Prevention (DEP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Data Execution Prevention (DEP)" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn DEP on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <DEP Enable="true"></DEP> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. - -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -System". - -If the status of "DEP: Enable" is "OFF", this is a finding. - -Values that would not be a finding include: - -ON -NOTSET (Default configuration)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000030Windows Server 2019 Exploit Protection system-level mitigation, Control flow guard (CFG), must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Control flow guard (CFG)", are enabled by default at the system level. CFG ensures flow integrity for indirect calls. If this is turned off, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure Exploit Protection system-level mitigation, "Control flow guard (CFG)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Control flow guard (CFG)" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn CFG on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <ControlFlowGuard Enable="true"></ControlFlowGuard> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. - -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -System". - -If the status of "CFG: Enable" is "OFF", this is a finding. - -Values that would not be a finding include: - -ON -NOTSET (Default configuration)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000040Windows Server 2019 Exploit Protection system-level mitigation, Validate exception chains (SEHOP), must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate exception chains (SEHOP)", are enabled by default at the system level. SEHOP (structured exception handling overwrite protection) ensures the integrity of an exception chain during exception dispatch. If this is turned off, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure Exploit Protection system-level mitigation, "Validate exception chains (SEHOP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Validate exception chains (SEHOP)" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn SEHOP on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <SEHOP Enable="true"></SEHOP> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. - -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -System". - -If the status of "SEHOP: Enable" is "OFF", this is a finding. - -Values that would not be a finding include: - -ON -NOTSET (Default configuration)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000050Windows Server 2019 Exploit Protection system-level mitigation, Validate heap integrity, must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate heap integrity", are enabled by default at the system level. "Validate heap integrity" terminates a process when heap corruption is detected. If this is turned off, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure Exploit Protection system-level mitigation, "Validate heap integrity" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Validate heap integrity" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Validate heap integrity on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <Heap TerminateOnError="true"></Heap> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. - -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -System". - -If the status of "Heap: TerminateOnError" is "OFF", this is a finding. - -Values that would not be a finding include: - -ON -NOTSET (Default configuration)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000060Windows Server 2019 Exploit Protection mitigations must be configured for Acrobat.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for Acrobat.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name Acrobat.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000070Windows Server 2019 Exploit Protection mitigations must be configured for AcroRd32.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for AcroRd32.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name AcroRd32.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000080Windows Server 2019 Exploit Protection mitigations must be configured for chrome.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for chrome.exe: - -DEP: -Enable: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name chrome.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000090Windows Server 2019 Exploit Protection mitigations must be configured for EXCEL.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for EXCEL.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name EXCEL.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000100Windows Server 2019 Exploit Protection mitigations must be configured for firefox.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for firefox.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name firefox.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000110Windows Server 2019 Exploit Protection mitigations must be configured for FLTLDR.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for FLTLDR.EXE: - -DEP: -Enable: ON - -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Child Process: -DisallowChildProcessCreation: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name FLTLDR.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Child Process: -DisallowChildProcessCreation: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000120Windows Server 2019 Exploit Protection mitigations must be configured for GROOVE.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for GROOVE.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Child Process: -DisallowChildProcessCreation: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name GROOVE.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Child Process: -DisallowChildProcessCreation: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000130Windows Server 2019 Exploit Protection mitigations must be configured for iexplore.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for iexplore.exe: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name iexplore.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -BottomUp: ON -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000140Windows Server 2019 Exploit Protection mitigations must be configured for INFOPATH.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for INFOPATH.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name INFOPATH.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000150Windows Server 2019 Exploit Protection mitigations must be configured for java.exe, javaw.exe, and javaws.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for java.exe, javaw.exe, and javaws.exe: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name [application name]" with each of the following substituted for [application name]: -java.exe, javaw.exe, and javaws.exe -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON" for each, this is a finding: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000160Windows Server 2019 Exploit Protection mitigations must be configured for lync.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for lync.exe: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name lync.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000170Windows Server 2019 Exploit Protection mitigations must be configured for MSACCESS.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for MSACCESS.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name MSACCESS.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000180Windows Server 2019 Exploit Protection mitigations must be configured for MSPUB.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for MSPUB.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name MSPUB.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000190Windows Server 2019 Exploit Protection mitigations must be configured for OIS.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for OIS.EXE: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name OIS.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000200Windows Server 2019 Exploit Protection mitigations must be configured for OneDrive.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for OneDrive.exe: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name OneDrive.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -ImageLoad: -BlockRemoteImageLoads: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000210Windows Server 2019 Exploit Protection mitigations must be configured for OUTLOOK.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for OUTLOOK.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name OUTLOOK.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000220Windows Server 2019 Exploit Protection mitigations must be configured for plugin-container.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for plugin-container.exe: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name plugin-container.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000230Windows Server 2019 Exploit Protection mitigations must be configured for POWERPNT.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for POWERPNT.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name POWERPNT.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000240Windows Server 2019 Exploit Protection mitigations must be configured for PPTVIEW.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for PPTVIEW.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name PPTVIEW.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000250Windows Server 2019 Exploit Protection mitigations must be configured for VISIO.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for VISIO.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name VISIO.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000260Windows Server 2019 Exploit Protection mitigations must be configured for VPREVIEW.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for VPREVIEW.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name VPREVIEW.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000270Windows Server 2019 Exploit Protection mitigations must be configured for WINWORD.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for WINWORD.EXE: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name WINWORD.EXE". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -ASLR: -ForceRelocateImages: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000280Windows Server 2019 Exploit Protection mitigations must be configured for wmplayer.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for wmplayer.exe: - -DEP: -Enable: ON - -Payload: -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name wmplayer.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -Payload: -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000290Windows Server 2019 Exploit Protection mitigations must be configured for wordpad.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following mitigations are turned "ON" for wordpad.exe: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. - -This is applicable to unclassified systems, for other systems this is NA. - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -Name wordpad.exe". -(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) - -If the following mitigations do not have a status of "ON", this is a finding: - -DEP: -Enable: ON - -Payload: -EnableExportAddressFilter: ON -EnableExportAddressFilterPlus: ON -EnableImportAddressFilter: ON -EnableRopStackPivot: ON -EnableRopCallerCheck: ON -EnableRopSimExec: ON - -The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000010Windows Server 2019 users with Administrative privileges 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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure each user with administrative privileges 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. - -If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding.SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>WN19-CC-000210Windows Server 2019 Autoplay 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 media is inserted into 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ - -Value Name: NoAutoplayfornonVolume - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>WN19-CC-000220Windows Server 2019 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-001764Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Set the default behavior for AutoRun" to "Enabled" with "Do not execute any autorun commands" 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\Microsoft\Windows\CurrentVersion\Policies\Explorer\ - -Value Name: NoAutorun - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>WN19-CC-000230Windows Server 2019 AutoPlay 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 media is inserted into 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. Enabling this policy disables 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 2019DISADPMS TargetWindows 20193483CCI-001764Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Turn off AutoPlay" to "Enabled" with "All Drives" 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\Microsoft\Windows\CurrentVersion\policies\Explorer\ - -Value Name: NoDriveTypeAutoRun - -Type: REG_DWORD -Value: 0x000000ff (255)SRG-OS-000370-GPOS-00155<GroupDescription></GroupDescription>WN19-00-000080Windows Server 2019 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.<VulnDiscussion>Using a whitelist provides a configuration management method to allow 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 2019DISADPMS TargetWindows 20193483CCI-001774Configure 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 Server. - -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" at the following link: - -https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfmThis 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. - -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 Server. 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 imported previously, 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" at the following link: - -https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfmSRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000270Windows Server 2019 must have the roles and features required by the system documented.<VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</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 2019DISADPMS TargetWindows 20193483CCI-000381Document the roles and features required for the system to operate. Uninstall any that are not required.Required roles and features will vary based on the function of the individual system. - -Roles and features specifically required to be disabled per the STIG are identified in separate requirements. - -If the organization has not documented the roles and features required for the system(s), this is a finding. - -The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State".SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000320Windows Server 2019 must not have the Fax Server role installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019DISADPMS TargetWindows 20193483CCI-000381Uninstall the "Fax Server" role. - -Start "Server Manager". - -Select the server with the role. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "Fax Server" on the "Roles" page. - -Click "Next" and "Remove" as prompted.Open "PowerShell". - -Enter "Get-WindowsFeature | Where Name -eq Fax". - -If "Installed State" is "Installed", this is a finding. - -An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000340Windows Server 2019 must not have the Peer Name Resolution Protocol installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019DISADPMS TargetWindows 20193483CCI-000381Uninstall the "Peer Name Resolution Protocol" feature. - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "Peer Name Resolution Protocol" on the "Features" page. - -Click "Next" and "Remove" as prompted.Open "PowerShell". - -Enter "Get-WindowsFeature | Where Name -eq PNRP". - -If "Installed State" is "Installed", this is a finding. - -An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000350Windows Server 2019 must not have Simple TCP/IP Services installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019DISADPMS TargetWindows 20193483CCI-000381Uninstall the "Simple TCP/IP Services" feature. - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "Simple TCP/IP Services" on the "Features" page. - -Click "Next" and "Remove" as prompted.Open "PowerShell". - -Enter "Get-WindowsFeature | Where Name -eq Simple-TCPIP". - -If "Installed State" is "Installed", this is a finding. - -An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000370Windows Server 2019 must not have the TFTP Client installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019DISADPMS TargetWindows 20193483CCI-000381Uninstall the "TFTP Client" feature. - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "TFTP Client" on the "Features" page. - -Click "Next" and "Remove" as prompted.Open "PowerShell". - -Enter "Get-WindowsFeature | Where Name -eq TFTP-Client". - -If "Installed State" is "Installed", this is a finding. - -An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000380Windows Server 2019 must not the Server Message Block (SMB) v1 protocol installed.<VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.</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 2019DISADPMS TargetWindows 20193483CCI-000381Uninstall the SMBv1 protocol. - -Open "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Uninstall-WindowsFeature -Name FS-SMB1 -Restart". -(Omit the Restart parameter if an immediate restart of the system cannot be done.) - -Alternately: - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "SMB 1.0/CIFS File Sharing Support" on the "Features" page. - -Click "Next" and "Remove" as prompted.Different methods are available to disable SMBv1 on Windows Server 2019. This is the preferred method, however if WN19-00-000390 and WN19-00-000400 are configured, this is NA. - -Open "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-WindowsFeature -Name FS-SMB1". - -If "Installed State" is "Installed", this is a finding. - -An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000390Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server.<VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</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 2019DISADPMS TargetWindows 20193483CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 Server" to "Disabled". - -The system must be restarted for the change to take effect. - -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.Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, 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: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ - -Value Name: SMB1 - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000400Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client.<VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</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 2019DISADPMS TargetWindows 20193483CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 client driver" to "Enabled" with "Disable driver (recommended)" selected for "Configure MrxSmb10 driver". - -The system must be restarted for the changes to take effect. - -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.Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. - -If the following registry value is not configured as specified, this is a finding: - -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ - -Value Name: Start - -Type: REG_DWORD -Value: 0x00000004 (4)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000410Windows Server 2019 must not have Windows PowerShell 2.0 installed.<VulnDiscussion>Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.</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 2019DISADPMS TargetWindows 20193483CCI-000381Uninstall the "Windows PowerShell 2.0 Engine". - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell" on the "Features" page. - -Click "Next" and "Remove" as prompted.Open "PowerShell". - -Enter "Get-WindowsFeature | Where Name -eq PowerShell-v2". - -If "Installed State" is "Installed", this is a finding. - -An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000010Windows Server 2019 must prevent the display of slide shows on the lock screen.<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 2019DISADPMS TargetWindows 20193483CCI-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: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000020Windows Server 2019 must have WDigest Authentication 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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is 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 2019DISADPMS TargetWindows 20193483CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "WDigest Authentication (disabling may require KB2871997)" to "Disabled". - -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)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000150Windows Server 2019 downloading print driver packages over HTTP 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 will prevent 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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ - -Value Name: DisableWebPnPDownload - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000160Windows Server 2019 printing over HTTP 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 will prevent 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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ - -Value Name: DisableHTTPPrinting - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000170Windows Server 2019 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 in to 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 2019DISADPMS TargetWindows 20193483CCI-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: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000200Windows Server 2019 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 will prevent 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\ - -Value Name: DisableInventory - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000300Windows Server 2019 Windows Defender SmartScreen must be enabled.<VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</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 2019DISADPMS TargetWindows 20193483CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Configure Windows Defender SmartScreen" to "Enabled" with either option "Warn" or "Warn and prevent bypass" selected. - -Windows 2019 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer.This is applicable to unclassified systems; for other systems, 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\Windows\System\ - -Value Name: EnableSmartScreen - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000400Windows Server 2019 must disable Basic authentication for RSS feeds over HTTP.<VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</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 2019DISADPMS TargetWindows 20193483CCI-000381The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> "Turn on Basic feed authentication over HTTP" to "Not Configured" or "Disabled".The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. - -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ - -Value Name: AllowBasicAuthInClear - -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000410Windows Server 2019 must prevent Indexing of encrypted files.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\ - -Value Name: AllowIndexingEncryptedStoresOrItems - -Value Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-DC-000130Windows Server 2019 domain controllers must run on a machine dedicated to that function.<VulnDiscussion>Executing application servers on the same host machine with a directory server may substantially weaken the security of the directory server. Web or database server applications usually require the addition of many programs and accounts, increasing the attack surface of the computer. - -Some applications require the addition of privileged accounts, providing potential sources of compromise. Some applications (such as Microsoft Exchange) may require the use of network ports or services conflicting with the directory server. In this case, non-standard ports might be selected, and this could interfere with intrusion detection or prevention 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 2019DISADPMS TargetWindows 20193483CCI-000381Remove additional roles or applications such as web, database, and email from the domain controller.This applies to domain controllers, it is NA for other systems. - -Review the installed roles the domain controller is supporting. - -Start "Server Manager". - -Select "AD DS" in the left pane and the server name under "Servers" to the right. - -Select "Add (or Remove) Roles and Features" from "Tasks" in the "Roles and Features" section. (Cancel before any changes are made.) - -Determine if any additional server roles are installed. A basic domain controller setup will include the following: - -- Active Directory Domain Services -- DNS Server -- File and Storage Services - -If any roles not requiring installation on a domain controller are installed, this is a finding. - -A Domain Name System (DNS) server integrated with the directory server (e.g., AD-integrated DNS) is an acceptable application. However, the DNS server must comply with the DNS STIG security requirements. - -Run "Programs and Features". - -Review installed applications. - -If any applications are installed that are not required for the domain controller, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-MS-000030Windows Server 2019 local users on domain-joined member servers 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> "Enumerate local users on domain-joined computers" to "Disabled".This applies to member servers. For domain controllers and standalone systems, 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\Windows\System\ - -Value Name: EnumerateLocalUsers - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>WN19-00-000330Windows Server 2019 must not have the Microsoft FTP service installed unless required by the organization.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</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 2019DISADPMS TargetWindows 20193483CCI-000382Uninstall the "FTP Server" role. - -Start "Server Manager". - -Select the server with the role. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "FTP Server" under "Web Server (IIS)" on the "Roles" page. - -Click "Next" and "Remove" as prompted.If the server has the role of an FTP server, this is NA. - -Open "PowerShell". - -Enter "Get-WindowsFeature | Where Name -eq Web-Ftp-Service". - -If "Installed State" is "Installed", this is a finding. - -An Installed State of "Available" or "Removed" is not a finding. - -If the system has the role of an FTP server, this must be documented with the ISSO.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>WN19-00-000360Windows Server 2019 must not have the Telnet Client installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 2019DISADPMS TargetWindows 20193483CCI-000382Uninstall the "Telnet Client" feature. - -Start "Server Manager". - -Select the server with the feature. - -Scroll down to "ROLES AND FEATURES" in the right pane. - -Select "Remove Roles and Features" from the drop-down "TASKS" list. - -Select the appropriate server on the "Server Selection" page and click "Next". - -Deselect "Telnet Client" on the "Features" page. - -Click "Next" and "Remove" as prompted.Open "PowerShell". - -Enter "Get-WindowsFeature | Where Name -eq Telnet-Client". - -If "Installed State" is "Installed", this is a finding. - -An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-CC-000340Windows Server 2019 must not save passwords 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ - -Value Name: DisablePasswordSaving - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-CC-000360Windows Server 2019 Remote 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ - -Value Name: fPromptForPassword - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-CC-000520Windows Server 2019 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ - -Value Name: DisableRunAs - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-SO-000380Windows Server 2019 User 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019DISADPMS TargetWindows 20193483CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: FilterAdministratorToken - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-SO-000410Windows Server 2019 User Account Control must automatically deny standard user requests for elevation.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019DISADPMS TargetWindows 20193483CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: ConsentPromptBehaviorUser - -Value Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-SO-000440Windows Server 2019 User 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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</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 2019DISADPMS TargetWindows 20193483CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: EnableLUA - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>WN19-00-000070Windows Server 2019 shared user accounts must not be permitted.<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 nonrepudiation or individual accountability for system access and resource usage.</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 2019DISADPMS TargetWindows 20193483CCI-000764Remove unapproved shared accounts from the system. - -Document required shared accounts with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity.Determine whether any shared accounts exist. If no shared accounts exist, this is NA. - -Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. - -If unapproved shared accounts exist, this is a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>WN19-00-000200Windows Server 2019 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. 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 2019DISADPMS TargetWindows 20193483CCI-000764Configure all enabled accounts to require passwords. - -The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account.Review the password required status for enabled user accounts. - -Open "PowerShell". - -Domain Controllers: - -Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". - -Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). - -If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. - -Member servers and standalone systems: - -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. - -Exclude disabled accounts (e.g., DefaultAccount, Guest). - -If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding.SRG-OS-000105-GPOS-00052<GroupDescription></GroupDescription>WN19-DC-000310Windows Server 2019 Active Directory user accounts, including administrators, must be configured to require the use of a Common Access Card (CAC), Personal Identity Verification (PIV)-compliant hardware token, or Alternate Logon Token (ALT) for user authentication.<VulnDiscussion>Smart cards such as the CAC support a two-factor authentication technique. This provides a higher level of trust in the asserted identity than use of the username and password for authentication. - -Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160</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 2019DISADPMS TargetWindows 20193483CCI-000765CCI-000766CCI-000767CCI-000768CCI-001948Configure all user accounts, including administrator accounts, in Active Directory to enable the option "Smart card is required for interactive logon". - -Run "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): - -Select the OU where the user accounts are located. (By default this is the Users node; however, accounts may be under other organization-defined OUs.) - -Right-click the user account and select "Properties". - -Select the "Account" tab. - -Check "Smart card is required for interactive logon" in the "Account Options" area.This applies to domain controllers. It is NA for other systems. - -Open "PowerShell". - -Enter the following: - -"Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name" -("DistinguishedName" may be substituted for "Name" for more detailed output.) - -If any user accounts, including administrators, are listed, this is a finding. - - -Alternately: - -To view sample accounts in "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): - -Select the Organizational Unit (OU) where the user accounts are located. (By default, this is the Users node; however, accounts may be under other organization-defined OUs.) - -Right-click the sample user account and select "Properties". - -Select the "Account" tab. - -If any user accounts, including administrators, do not have "Smart card is required for interactive logon" checked in the "Account Options" area, this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000020Windows Server 2019 Kerberos user logon restrictions must be enforced.<VulnDiscussion>This policy setting determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer. The policy is enabled by default, which is the most secure setting for validating that access to target resources is not circumvented. - -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</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 2019DISADPMS TargetWindows 20193483CCI-001941CCI-001942Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Enforce user logon restrictions" to "Enabled".This applies to domain controllers. It is NA for other systems. - -Verify the following is configured in the Default Domain Policy: - -Open "Group Policy Management". - -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). - -Right-click on the "Default Domain Policy". - -Select "Edit". - -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. - -If the "Enforce user logon restrictions" is not set to "Enabled", this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000030Windows Server 2019 Kerberos service ticket maximum lifetime must be limited to 600 minutes or less.<VulnDiscussion>This setting determines the maximum amount of time (in minutes) that a granted session ticket can be used to access a particular service. Session tickets are used only to authenticate new connections with servers. Ongoing operations are not interrupted if the session ticket used to authenticate the connection expires during the connection. - -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</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 2019DISADPMS TargetWindows 20193483CCI-001941CCI-001942Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for service ticket" to a maximum of "600" minutes, but not "0", which equates to "Ticket doesn't expire".This applies to domain controllers. It is NA for other systems. - -Verify the following is configured in the Default Domain Policy: - -Open "Group Policy Management". - -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). - -Right-click on the "Default Domain Policy". - -Select "Edit". - -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. - -If the value for "Maximum lifetime for service ticket" is "0" or greater than "600" minutes, this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000040Windows Server 2019 Kerberos user ticket lifetime must be limited to 10 hours or less.<VulnDiscussion>In Kerberos, there are two types of tickets: Ticket Granting Tickets (TGTs) and Service Tickets. Kerberos tickets have a limited lifetime so the time an attacker has to implement an attack is limited. This policy controls how long TGTs can be renewed. With Kerberos, the user's initial authentication to the domain controller results in a TGT, which is then used to request Service Tickets to resources. Upon startup, each computer gets a TGT before requesting a service ticket to the domain controller and any other computers it needs to access. For services that start up under a specified user account, users must always get a TGT first and then get Service Tickets to all computers and services accessed. - -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</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 2019DISADPMS TargetWindows 20193483CCI-001941CCI-001942Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for user ticket" to a maximum of "10" hours but not "0", which equates to "Ticket doesn't expire".This applies to domain controllers. It is NA for other systems. - -Verify the following is configured in the Default Domain Policy: - -Open "Group Policy Management". - -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). - -Right-click on the "Default Domain Policy". - -Select "Edit". - -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. - -If the value for "Maximum lifetime for user ticket" is "0" or greater than "10" hours, this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000050Windows Server 2019 Kerberos policy user ticket renewal maximum lifetime must be limited to seven days or less.<VulnDiscussion>This setting determines the period of time (in days) during which a user's Ticket Granting Ticket (TGT) may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access. - -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</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 2019DISADPMS TargetWindows 20193483CCI-001941CCI-001942Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for user ticket renewal" to a maximum of "7" days or less.This applies to domain controllers. It is NA for other systems. - -Verify the following is configured in the Default Domain Policy: - -Open "Group Policy Management". - -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). - -Right-click on the "Default Domain Policy". - -Select "Edit". - -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. - -If the "Maximum lifetime for user ticket renewal" is greater than "7" days, this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000060Windows Server 2019 computer clock synchronization tolerance must be limited to five minutes or less.<VulnDiscussion>This setting determines the maximum time difference (in minutes) that Kerberos will tolerate between the time on a client's clock and the time on a server's clock while still considering the two clocks synchronous. In order to prevent replay attacks, Kerberos uses timestamps as part of its protocol definition. For timestamps to work properly, the clocks of the client and the server need to be in sync as much as possible. - -Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</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 2019DISADPMS TargetWindows 20193483CCI-001941CCI-001942Configure the policy value in the Default Domain Policy for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum tolerance for computer clock synchronization" to a maximum of "5" minutes or less.This applies to domain controllers. It is NA for other systems. - -Verify the following is configured in the Default Domain Policy: - -Open "Group Policy Management". - -Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). - -Right-click on the "Default Domain Policy". - -Select "Edit". - -Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. - -If the "Maximum tolerance for computer clock synchronization" is greater than "5" minutes, this is a finding.SRG-OS-000379-GPOS-00164<GroupDescription></GroupDescription>WN19-MS-000040Windows Server 2019 must restrict unauthenticated Remote Procedure Call (RPC) clients from connecting to the RPC server on domain-joined member servers and standalone systems.<VulnDiscussion>Unauthenticated RPC clients may allow anonymous access to sensitive information. 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 2019DISADPMS TargetWindows 20193483CCI-001967Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Remote Procedure Call >> "Restrict Unauthenticated RPC clients" to "Enabled" with "Authenticated" selected.This applies to member servers and standalone systems, it is NA for domain controllers. - -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\Rpc\ - -Value Name: RestrictRemoteClients - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000379-GPOS-00164<GroupDescription></GroupDescription>WN19-SO-000090Windows Server 2019 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 the 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 2019DISADPMS TargetWindows 20193483CCI-001967Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain member: Disable machine account password changes" 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: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ - -Value Name: DisablePasswordChange - -Value Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000118-GPOS-00060<GroupDescription></GroupDescription>WN19-00-000190Windows Server 2019 outdated or unused accounts must be removed or disabled.<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, disabled 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 2019DISADPMS TargetWindows 20193483CCI-000795Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days.Open "Windows PowerShell". - -Domain Controllers: - -Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" - -This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. - -Member servers and standalone systems: - -Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) - -"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { - $user = ([ADSI]$_.Path) - $lastLogin = $user.Properties.LastLogin.Value - $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 - if ($lastLogin -eq $null) { - $lastLogin = 'Never' - } - Write-Host $user.Name $lastLogin $enabled -}" - -This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). -For example: User1 10/31/2015 5:49:56 AM True - -Review the list of accounts returned by the above queries to determine the finding validity for each account reported. - -Exclude the following accounts: - -- Built-in administrator account (Renamed, SID ending in 500) -- Built-in guest account (Renamed, Disabled, SID ending in 501) -- Application accounts - -If any enabled accounts have not been logged on to within the past 35 days, this is a finding. - -Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO.SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>WN19-AC-000080Windows Server 2019 must have the built-in Windows password complexity policy 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 three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. - -Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101</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 2019DISADPMS TargetWindows 20193483CCI-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".Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "PasswordComplexity" equals "0" in the file, this is a finding. - -Note: If an external password filter is in use that enforces all four character types and requires this setting to 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.SRG-OS-000078-GPOS-00046<GroupDescription></GroupDescription>WN19-00-000050Windows Server 2019 manually managed application 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000205Establish a policy that requires application/service account passwords that are manually managed to be at least 15 characters in length. Ensure the policy is enforced.Determine if manually managed application/service accounts exist. If none exist, this is NA. - -Verify the organization has 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.SRG-OS-000078-GPOS-00046<GroupDescription></GroupDescription>WN19-AC-000070Windows Server 2019 minimum password length must be configured to 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 2019DISADPMS TargetWindows 20193483CCI-000205Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password length" to "14" characters.Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for the "Minimum password length," is less than "14" characters, this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "MinimumPasswordLength" is less than "14" in the file, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>WN19-AC-000090Windows Server 2019 reversible password encryption must be disabled.<VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000196Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Store passwords using reversible encryption" to "Disabled".Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for "Store passwords using reversible encryption" is not set to "Disabled", this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "ClearTextPassword" equals "1" in the file, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>WN19-SO-000300Windows Server 2019 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 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".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\Lsa\ - -Value Name: NoLMHash - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000074-GPOS-00042<GroupDescription></GroupDescription>WN19-SO-000180Windows Server 2019 unencrypted passwords must not be sent to third-party Server Message Block (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 determine 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 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\LanmanWorkstation\Parameters\ - -Value Name: EnablePlainTextPassword - -Value Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000075-GPOS-00043<GroupDescription></GroupDescription>WN19-AC-000060Windows Server 2019 minimum password age must be configured to at least one day.<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 2019DISADPMS TargetWindows 20193483CCI-000198Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password age" to at least "1" day.Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for the "Minimum password age" is set to "0" days ("Password can be changed immediately"), this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "MinimumPasswordAge" equals "0" in the file, this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>WN19-00-000020Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days.<VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. - -Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</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 2019DISADPMS TargetWindows 20193483CCI-000199Change the built-in Administrator account password at least every "60" days. - -Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this.Review the password last set date for the built-in Administrator account. - -Domain controllers: - -Open "PowerShell". - -Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". - -If the "PasswordLastSet" date is greater than "60" days old, this is a finding. - -Member servers and standalone systems: - -Open "Command Prompt". - -Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. - -(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) - -If the "PasswordLastSet" date is greater than "60" days old, this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>WN19-00-000210Windows Server 2019 passwords must be configured to expire.<VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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 2019DISADPMS TargetWindows 20193483CCI-000199Configure all enabled user account passwords to expire. - -Uncheck "Password never expires" for all enabled user accounts in Active Directory Users and Computers for domain accounts and Users in Computer Management for member servers and standalone systems. Document any exceptions with the ISSO.Review the password never expires status for enabled user accounts. - -Open "PowerShell". - -Domain Controllers: - -Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". - -Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. - -If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. - -Member servers and standalone systems: - -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. - -Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). - -If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>WN19-AC-000050Windows Server 2019 maximum password age must be configured to 60 days or less.<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 2019DISADPMS TargetWindows 20193483CCI-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).Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "MaximumPasswordAge" is greater than "60" or equal to "0" in the file, this is a finding.SRG-OS-000077-GPOS-00045<GroupDescription></GroupDescription>WN19-AC-000040Windows Server 2019 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 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 2019DISADPMS TargetWindows 20193483CCI-000200Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Enforce password history" to "24" passwords remembered.Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "PasswordHistorySize" is less than "24" in the file, this is a finding.SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-DC-000280Windows Server 2019 domain controllers must have a PKI server certificate.<VulnDiscussion>Domain controllers are part of the chain of trust for PKI authentications. Without the appropriate certificate, the authenticity of the domain controller cannot be verified. Domain controllers must have a server certificate to establish authenticity as part of PKI authentications in 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 2019DISADPMS TargetWindows 20193483CCI-000185Obtain a server certificate for the domain controller.This applies to domain controllers. It is NA for other systems. - -Run "MMC". - -Select "Add/Remove Snap-in" from the "File" menu. - -Select "Certificates" in the left pane and click the "Add >" button. - -Select "Computer Account" and click "Next". - -Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". - -Click "OK". - -Select and expand the Certificates (Local Computer) entry in the left pane. - -Select and expand the Personal entry in the left pane. - -Select the Certificates entry in the left pane. - -If no certificate for the domain controller exists in the right pane, this is a finding.SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-DC-000290Windows Server 2019 domain Controller PKI certificates must be issued by the DoD PKI or an approved External Certificate Authority (ECA).<VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.</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 2019DISADPMS TargetWindows 20193483CCI-000185Obtain a server certificate for the domain controller issued by the DoD PKI or an approved ECA.This applies to domain controllers. It is NA for other systems. - -Run "MMC". - -Select "Add/Remove Snap-in" from the "File" menu. - -Select "Certificates" in the left pane and click the "Add >" button. - -Select "Computer Account" and click "Next". - -Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". - -Click "OK". - -Select and expand the Certificates (Local Computer) entry in the left pane. - -Select and expand the Personal entry in the left pane. - -Select the Certificates entry in the left pane. - -In the right pane, examine the "Issued By" field for the certificate to determine the issuing CA. - -If the "Issued By" field of the PKI certificate being used by the domain controller does not indicate the issuing CA is part of the DoD PKI or an approved ECA, this is a finding. - -If the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding. - -There are multiple sources from which lists of valid DoD CAs and approved ECAs can be obtained: - -The Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil. - -DoD Public Key Enablement (PKE) Engineering Support maintains the InstallRoot utility to manage DoD supported root certificates on Windows computers, which includes a list of authorized CAs. The utility package can be downloaded from the PKI and PKE Tools page on IASE: - -http://iase.disa.mil/pki-pke/function_pages/tools.htmlSRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-DC-000300Windows Server 2019 PKI certificates associated with user accounts must be issued by a DoD PKI or an approved External Certificate Authority (ECA).<VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions.</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 2019DISADPMS TargetWindows 20193483CCI-000185Map user accounts to PKI certificates using the appropriate User Principal Name (UPN) for the network. See PKE documentation for details.This applies to domain controllers. It is NA for other systems. - -Review user account mappings to PKI certificates. - -Open "Windows PowerShell". - -Enter "Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled". - -Exclude disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. - -If the User Principal Name (UPN) is not in the format of an individual's identifier for the certificate type and for the appropriate domain suffix, this is a finding. - -For standard NIPRNet certificates, the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI). - -Alt Tokens and other certificates may use a different UPN format than the EDI-PI which vary by organization. Verified these with the organization. - -NIPRNet Example: - -Name - User Principal Name -User1 - 1234567890@mil - -See PKE documentation for other network domain suffixes. - -If the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding.SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-PK-000010Windows Server 2019 must have the DoD Root Certificate Authority (CA) certificates 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 CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</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 2019DISADPMS TargetWindows 20193483CCI-000185CCI-002470Install the DoD Root CA certificates: - -DoD Root CA 2 -DoD Root CA 3 -DoD Root CA 4 -DoD Root CA 5 - -The InstallRoot tool is available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx.The certificates and thumbprints referenced below apply to unclassified systems; see PKE documentation for other networks. - -Open "Windows PowerShell" as an administrator. - -Execute the following command: - -Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint, NotAfter - -If the following certificate "Subject" and "Thumbprint" information is not displayed, this is a finding. - -If an expired certificate ("NotAfter" date) is not listed in the results, this is not a finding. - -Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 -NotAfter: 12/5/2029 - -Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB -NotAfter: 12/30/2029 - -Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 -NotAfter: 7/25/2032 - -Subject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B -NotAfter: 6/14/2041 - -Alternately, use the Certificates MMC snap-in: - -Run "MMC". - -Select "File", "Add/Remove Snap-in". - -Select "Certificates" and click "Add". - -Select "Computer account" and click "Next". - -Select "Local computer: (the computer this console is running on)" and click "Finish". - -Click "OK". - -Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates". - -For each of the DoD Root CA certificates noted below: - -Right-click on the certificate and select "Open". - -Select the "Details" Tab. - -Scroll to the bottom and select "Thumbprint". - -If the DoD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. - -If an expired certificate ("Valid to" date) is not listed in the results, this is not a finding. - -DoD Root CA 2 -Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 -Valid to: Wednesday, December 5, 2029 - -DoD Root CA 3 -Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB -Valid to: Sunday, December 30, 2029 - -DoD Root CA 4 -Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 -Valid to: Sunday, July 25, 2032 - -DoD Root CA 5 -Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B -Valid to: Friday, June 14, 2041SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-PK-000020Windows Server 2019 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates 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. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</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 2019DISADPMS TargetWindows 20193483CCI-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 are available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx.This is applicable to unclassified systems. It is NA for others. - -Open "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, NotAfter - -If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. - -If an expired certificate ("NotAfter" date) is not listed in the results, this is not a 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 -NotAfter: 9/6/2019 - -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 -NotAfter: 2/17/2019 - -Alternately, use the Certificates MMC snap-in: - -Run "MMC". - -Select "File", "Add/Remove Snap-in". - -Select "Certificates" and click "Add". - -Select "Computer account" and click "Next". - -Select "Local computer: (the computer this console is running on)" and 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. - -If an expired certificate ("Valid to" date) is not listed in the results, this is not a finding. - -Issued To: DoD Root CA 2 -Issued By: DoD Interoperability Root CA 1 -Thumbprint: 22BBE981F0694D246CC1472ED2B021DC8540A22F -Valid to: Friday, September 6, 2019 - -Issued To: DoD Root CA 3 -Issued By: DoD Interoperability Root CA 2 -Thumbprint: FFAD03329B9E527A43EEC66A56F9CBB5393E6E13 -Valid to: Sunday, September 23, 2018 - -Issued To: DoD Root CA 3 -Issued By: DoD Interoperability Root CA 2 -Thumbprint: FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4 -Valid to: Sunday, February 17, 2019SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-PK-000030Windows Server 2019 must have the US DoD CCEB Interoperability Root CA cross-certificates 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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</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 2019DISADPMS TargetWindows 20193483CCI-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 - -DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - 929BF3196896994C0A201DF4A5B71F603FEFBF2E - -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 are available on IASE at http://iase.disa.mil/pki-pke/Pages/tools.aspx.This is applicable to unclassified systems. It is NA for others. - -Open "PowerShell" as an administrator. - -Execute the following command: - -Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter - -If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. - -If an expired certificate ("NotAfter" date) is not listed in the results, this is not a 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 -NotAfter: 3/9/2019 - -Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US -Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US -Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E -NotAfter: 9/27/2019 - -Alternately, use the Certificates MMC snap-in: - -Run "MMC". - -Select "File", "Add/Remove Snap-in". - -Select "Certificates" and click "Add". - -Select "Computer account" and click "Next". - -Select "Local computer: (the computer this console is running on)" and 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. - -If an expired certificate ("Valid to" date) is not listed in the results, this is not a finding. - -Issued To: DoD Root CA 2 -Issued By: US DoD CCEB Interoperability Root CA 1 -Thumbprint: DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3 -Valid to: Saturday, March 9, 2019 - -Issued To: DoD Root CA 3 -Issuer by: US DoD CCEB Interoperability Root CA 2 -Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E -Valid: Friday, September 27, 2019SRG-OS-000067-GPOS-00035<GroupDescription></GroupDescription>WN19-SO-000350Windows Server 2019 users must be required to enter a password to access private keys stored on the computer.<VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. - -The cornerstone of the PKI is the private key used to encrypt or digitally sign information. - -If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. - -Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</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 2019DISADPMS TargetWindows 20193483CCI-000186Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "System cryptography: Force strong key protection for user keys stored on the computer" to "User must enter a password each time they use a key".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\Cryptography\ - -Value Name: ForceKeyProtection - -Type: REG_DWORD -Value: 0x00000002 (2)SRG-OS-000120-GPOS-00061<GroupDescription></GroupDescription>WN19-SO-000290Windows Server 2019 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites.<VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. - -Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</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 2019DISADPMS TargetWindows 20193483CCI-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: - -AES128_HMAC_SHA1 -AES256_HMAC_SHA1 -Future encryption types - -Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.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\Kerberos\Parameters\ - -Value Name: SupportedEncryptionTypes - -Value Type: REG_DWORD -Value: 0x7ffffff8 (2147483640)SRG-OS-000121-GPOS-00062<GroupDescription></GroupDescription>WN19-SO-000010Windows Server 2019 must have the built-in guest account disabled.<VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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 2019DISADPMS TargetWindows 20193483CCI-000804Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Guest account status" to "Disabled".Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. - -If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. - -For server core installations, run the following command: - -Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt - -If "EnableGuestAccount" equals "1" in the file, this is a finding.SRG-OS-000393-GPOS-00173<GroupDescription></GroupDescription>WN19-CC-000480Windows Server 2019 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. - -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ - -Value Name: AllowUnencryptedTraffic - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000393-GPOS-00173<GroupDescription></GroupDescription>WN19-CC-000510Windows Server 2019 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. - -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ - -Value Name: AllowUnencryptedTraffic - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000125-GPOS-00065<GroupDescription></GroupDescription>WN19-CC-000470Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ - -Value Name: AllowBasic - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000125-GPOS-00065<GroupDescription></GroupDescription>WN19-CC-000490Windows Server 2019 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. Disallowing Digest authentication will reduce this potential.</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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ - -Value Name: AllowDigest - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000125-GPOS-00065<GroupDescription></GroupDescription>WN19-CC-000500Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</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 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ - -Value Name: AllowBasic - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>WN19-DC-000160Windows Server 2019 directory service must be configured to terminate LDAP-based network connections to the directory server after five minutes of inactivity.<VulnDiscussion>The failure to terminate inactive network connections increases the risk of a successful attack on the directory server. The longer an established session is in progress, the more time an attacker has to hijack the session, implement a means to passively intercept data, or compromise any protections on client access. For example, if an attacker gains control of a client computer, an existing (already authenticated) session with the directory server could allow access to the directory. The lack of confidentiality protection in LDAP-based sessions increases exposure to this vulnerability.</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 2019DISADPMS TargetWindows 20193483CCI-001133Configure the directory service to terminate LDAP-based network connections to the directory server after 5 minutes of inactivity. - -Open an elevated "Command prompt" (run as administrator). - -Enter "ntdsutil". - -At the "ntdsutil:" prompt, enter "LDAP policies". - -At the "ldap policy:" prompt, enter "connections". - -At the "server connections:" prompt, enter "connect to server [host-name]" (where [host-name] is the computer name of the domain controller). - -At the "server connections:" prompt, enter "q". - -At the "ldap policy:" prompt, enter "Set MaxConnIdleTime to 300". - -Enter "Commit Changes" to save. - -Enter "Show values" to verify changes. - -Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit.This applies to domain controllers. It is NA for other systems. - -Open an elevated "Command Prompt" (run as administrator). - -Enter "ntdsutil". - -At the "ntdsutil:" prompt, enter "LDAP policies". - -At the "ldap policy:" prompt, enter "connections". - -At the "server connections:" prompt, enter "connect to server [host-name]" -(where [host-name] is the computer name of the domain controller). - -At the "server connections:" prompt, enter "q". - -At the "ldap policy:" prompt, enter "show values". - -If the value for MaxConnIdleTime is greater than "300" (5 minutes) or is not specified, this is a finding. - -Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit. - -Alternately, Dsquery can be used to display MaxConnIdleTime: - -Open "Command Prompt (Admin)". -Enter the following command (on a single line). - -dsquery * "cn=Default Query Policy,cn=Query-Policies,cn=Directory Service, cn=Windows NT,cn=Services,cn=Configuration,dc=[forest-name]" -attr LDAPAdminLimits - -The quotes are required and dc=[forest-name] is the fully qualified LDAP name of the domain being reviewed (e.g., dc=disaost,dc=mil). - -If the results do not specify a "MaxConnIdleTime" or it has a value greater than "300" (5 minutes), this is a finding.SRG-OS-000478-GPOS-00223<GroupDescription></GroupDescription>WN19-SO-000360Windows Server 2019 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.<VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".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\Lsa\FIPSAlgorithmPolicy\ - -Value Name: Enabled - -Value Type: REG_DWORD -Value: 0x00000001 (1) - -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; otherwise. the browser will not be able to connect to a secure site.SRG-OS-000396-GPOS-00176<GroupDescription></GroupDescription>WN19-DC-000140Windows Server 2019 must use separate, NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level when replication data traverses a network cleared to a lower level than the data.<VulnDiscussion>Directory data that is not appropriately encrypted is subject to compromise. Commercial-grade encryption does not provide adequate protection when the classification level of directory data in transit is higher than the level of 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 2019DISADPMS TargetWindows 20193483CCI-002450Configure NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level that transfer replication data through a network cleared to a lower level than the data.This applies to domain controllers. It is NA for other systems. - -Review the organization network diagram(s) or documentation to determine the level of classification for the network(s) over which replication data is transmitted. - -Determine the classification level of the Windows domain controller. - -If the classification level of the Windows domain controller is higher than the level of the networks, review the organization network diagram(s) and directory implementation documentation to determine if NSA-approved encryption is used to protect the replication network traffic. - -If the classification level of the Windows domain controller is higher than the level of the network traversed and NSA-approved encryption is not used, this is a finding.SRG-OS-000185-GPOS-00079<GroupDescription></GroupDescription>WN19-00-000250Windows Server 2019 systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.<VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. - -Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). - -Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</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 2019DISADPMS TargetWindows 20193483CCI-001199CCI-002475CCI-002476Configure systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data to employ encryption to protect the confidentiality and integrity of all information at rest.Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. - -If they do not, this is a finding.SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-CC-000240Windows Server 2019 administrator accounts must not be enumerated during elevation.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ - -Value Name: EnumerateAdministrators - -Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-MS-000020Windows Server 2019 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers.<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 local 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-001084Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Apply UAC restrictions to local accounts on network logons" to "Enabled". - -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.This applies to member servers. For domain controllers and standalone systems, 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: LocalAccountTokenFilterPolicy - -Type: REG_DWORD -Value: 0x00000000 (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.SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000390Windows Server 2019 UIAccess applications must not be allowed to prompt for elevation without using 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 prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</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 2019DISADPMS TargetWindows 20193483CCI-001084Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" to "Disabled".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: EnableUIADesktopToggle - -Value Type: REG_DWORD -Value: 0x00000000 (0)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000400Windows Server 2019 User Account Control must, at a 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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". - -The more secure option for this setting, "Prompt for credentials on the secure desktop", would also be acceptable.UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: ConsentPromptBehaviorAdmin - -Value Type: REG_DWORD -Value: 0x00000002 (2) (Prompt for consent on the secure desktop) -0x00000001 (1) (Prompt for credentials on the secure desktop)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000420Windows Server 2019 User 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: EnableInstallerDetection - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000430Windows Server 2019 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.<VulnDiscussion>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 2019DISADPMS TargetWindows 20193483CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: EnableSecureUIAPaths - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000450Windows Server 2019 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.<VulnDiscussion>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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: EnableVirtualization - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-00-000230Windows Server 2019 non-system-created file shares must limit access to groups that require it.<VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</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 2019DISADPMS TargetWindows 20193483CCI-001090If a non-system-created 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.If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) - -Run "Computer Management". - -Navigate to System Tools >> Shared Folders >> Shares. - -Right-click any non-system-created shares. - -Select "Properties". - -Select the "Share Permissions" tab. - -If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. - -Select the "Security" tab. - -If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding.SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-CC-000350Windows Server 2019 Remote Desktop Services must prevent drive redirection.<VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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 -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ - -Value Name: fDisableCdm - -Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-DC-000120Windows Server 2019 data files owned by users must be on a different logical partition from the directory server data files.<VulnDiscussion>When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. - -The directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit 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 2019DISADPMS TargetWindows 20193483CCI-001090Move shares used to store files owned by users to a different logical partition than the directory server data files.This applies to domain controllers. It is NA for other systems. - -Run "Regedit". - -Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". - -Note the directory locations in the values for "DSA Database file". - -Open "Command Prompt". - -Enter "net share". - -Note the logical drive(s) or file system partition for any organization-created data shares. - -Ignore system shares (e.g., NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) should not be ignored. - -If user shares are located on the same logical partition as the directory server data files, this is a finding.SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-SO-000230Windows Server 2019 must not allow anonymous enumeration of shares.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".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\Lsa\ - -Value Name: RestrictAnonymous - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-SO-000250Windows Server 2019 must restrict anonymous access to Named Pipes and Shares.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\LanManServer\Parameters\ - -Value Name: RestrictNullSessAccess - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000420-GPOS-00186<GroupDescription></GroupDescription>WN19-CC-000060Windows Server 2019 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 server's 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 2019DISADPMS TargetWindows 20193483CCI-002385Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" to "Enabled". - -This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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\Services\Netbt\Parameters\ - -Value Name: NoNameReleaseOnDemand - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000425-GPOS-00189<GroupDescription></GroupDescription>WN19-00-000260Windows Server 2019 must implement protection methods such as TLS, encrypted VPNs, or IPsec if the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process.<VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. - -Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. - -Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. - -Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</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 2019DISADPMS TargetWindows 20193483CCI-002420CCI-002422Configure protection methods such as TLS, encrypted VPNs, or IPsec when the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process.If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. - -If protection methods have not been implemented, this is a finding.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-DC-000320Windows Server 2019 domain controllers must require LDAP access signing.<VulnDiscussion>Unsigned network traffic is susceptible to man-in-the-middle attacks, where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. The risk of an attacker pulling this off can be decreased by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPsec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man-in-the-middle attacks extremely difficult. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019DISADPMS TargetWindows 20193483CCI-002418CCI-002421Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain controller: LDAP server signing requirements" to "Require signing".This applies to domain controllers. It is NA for other systems. - -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\Services\NTDS\Parameters\ - -Value Name: LDAPServerIntegrity - -Value Type: REG_DWORD -Value: 0x00000002 (2)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000060Windows Server 2019 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled.<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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\Netlogon\Parameters\ - -Value Name: RequireSignOrSeal - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000070Windows Server 2019 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to enabled.<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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\Netlogon\Parameters\ - -Value Name: SealSecureChannel - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000080Windows Server 2019 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled.<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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\Netlogon\Parameters\ - -Value Name: SignSecureChannel - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000110Windows Server 2019 must be configured to require a strong session key.<VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\Netlogon\Parameters\ - -Value Name: RequireStrongKey - -Value Type: REG_DWORD -Value: 0x00000001 (1) - -This setting may prevent a system from being joined to a domain if not configured consistently between systems.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000160Windows Server 2019 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled.<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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\LanmanWorkstation\Parameters\ - -Value Name: RequireSecuritySignature - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000170Windows Server 2019 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled.<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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\LanmanWorkstation\Parameters\ - -Value Name: EnableSecuritySignature - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000190Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.<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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\LanManServer\Parameters\ - -Value Name: RequireSecuritySignature - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000200Windows Server 2019 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled.<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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</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 2019DISADPMS TargetWindows 20193483CCI-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".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\Services\LanManServer\Parameters\ - -Value Name: EnableSecuritySignature - -Value Type: REG_DWORD -Value: 0x00000001 (1)SRG-OS-000433-GPOS-00192<GroupDescription></GroupDescription>WN19-CC-000310Windows Server 2019 Explorer Data Execution Prevention must be enabled.<VulnDiscussion>Data Execution Prevention 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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-002824The default behavior is for data execution prevention to be turned on for File Explorer. - -If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off Data Execution Prevention for Explorer" to "Not Configured" or "Disabled".The default behavior is for Data Execution Prevention to be turned on for File Explorer. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. - -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ - -Value Name: NoDataExecutionPrevention - -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000433-GPOS-00193<GroupDescription></GroupDescription>WN19-EP-000020Windows Server 2019 Exploit Protection system-level mitigation, Randomize memory allocations (Bottom-Up ASLR), must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</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 2019DISADPMS TargetWindows 20193483CCI-002824Ensure Exploit Protection system-level mitigation, "Randomize memory allocations (Bottom-Up ASLR)" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. - -Open "Windows Defender Security Center". - -Select "App & browser control". - -Select "Exploit protection settings". - -Under "System settings", configure "Randomize memory allocations (Bottom-Up ASLR)" to "On by default" or "Use default (<On>)". - -The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Bottom-Up ASLR on (other system level EP requirements can be combined under <SystemConfig>): - -<SystemConfig> - <ASLR BottomUp="true" HighEntropy="true"></ASLR> -</SystemConfig> - -The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. - -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". - -Run "Windows PowerShell" with elevated privileges (run as administrator). - -Enter "Get-ProcessMitigation -System". - -If the status of "ASLR: BottomUp" is "OFF", this is a finding. - -Values that would not be a finding include: - -ON -NOTSET (Default configuration)SRG-OS-000191-GPOS-00080<GroupDescription></GroupDescription>WN19-00-000290Windows Server 2019 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Host Based Security System (HBSS) is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).<VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools.</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 2019DISADPMS TargetWindows 20193483CCI-001233Install a DoD approved HBSS software and ensure it is operating continuously.Verify DoD approved HBSS software is installed, configured, and properly operating. Ask the operator to document the HBSS software installation and configuration. - -If the operator is not able to provide a documented configuration for an installed HBSS or if the HBSS software is not properly configured, maintained, or used, this is a finding.SRG-OS-000480-GPOS-00231<GroupDescription></GroupDescription>WN19-00-000280Windows Server 2019 must have a host-based firewall installed and enabled.<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></IAControls>DPMS Target Windows 2019DISADPMS TargetWindows 20193483CCI-000366CCI-002080Install 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.WN19-CC-000451<GroupDescription></GroupDescription>WN19-CC-000451The Windows Explorer Preview pane must be disabled for Windows Server 2019.<VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. - -Organizations must disable the Windows Preview pane and Windows Detail pane.</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 2019DISADPMS TargetWindows 20193483CCI-000366Ensure the following settings are configured for Windows Server 2019 locally or applied through group policy. - -Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn off Preview Pane" to "Enabled". - -Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn on or off details pane" to "Enabled" and "Configure details pane" to "Always hide". -If the following registry values do not exist or are not configured as specified, this is a finding: - -Registry Hive: HKEY_CURRENT_USER -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer - -Value Name: NoPreviewPane - -Value Type: REG_DWORD - -Value: 1 - -Registry Hive: HKEY_CURRENT_USER -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer - -Value Name: NoReadingPane - -Value Type: REG_DWORD - -Value: 1 - diff --git a/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_STIG_V2R2_Manual-xccdf.xml b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_STIG_V2R2_Manual-xccdf.xml new file mode 100644 index 000000000..1ed5a5b0b --- /dev/null +++ b/source/StigData/Archive/Windows.Server.2019/U_MS_Windows_Server_2019_STIG_V2R2_Manual-xccdf.xml @@ -0,0 +1,6643 @@ +acceptedMicrosoft Windows Server 2019 Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 2 Benchmark Date: 04 May 20213.2.2.360791.10.02I - 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>SRG-OS-000002-GPOS-00002<GroupDescription></GroupDescription>WN19-00-000300Windows Server 2019 must automatically remove or disable temporary user accounts after 72 hours.<VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. + +Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. + +If temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours. + +To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103063V-92975CCI-000016Configure temporary user accounts to automatically expire within 72 hours. + +Domain accounts can be configured with an account expiration date, under "Account" properties. + +Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account. + +Delete any temporary user accounts that are no longer necessary.Review temporary user accounts for expiration dates. + +Determine if temporary user accounts are used and identify any that exist. If none exist, this is NA. + +Domain Controllers: + +Open "PowerShell". + +Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". + +If "AccountExpirationDate" has not been defined within 72 hours for any temporary user account, this is a finding. + +Member servers and standalone systems: + +Open "Command Prompt". + +Run "Net user [username]", where [username] is the name of the temporary user account. + +If "Account expires" has not been defined within 72 hours for any temporary user account, this is a finding.SRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>WN19-AU-000100Windows Server 2019 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 security groups, including changes in group members. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103067V-92979CCI-000018CCI-001403CCI-001405CCI-001404CCI-002130CCI-000172Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>WN19-AU-000110Windows Server 2019 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. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103069V-92981CCI-002130CCI-001405CCI-001404CCI-001403CCI-000018CCI-000172Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>WN19-AU-000120Windows Server 2019 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. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103071V-92983CCI-000172CCI-000018CCI-001403CCI-001404CCI-001405CCI-002130Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - FailureSRG-OS-000004-GPOS-00004<GroupDescription></GroupDescription>WN19-DC-000230Windows Server 2019 must be configured to audit Account Management - Computer 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. + +Computer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts. + +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103073V-92985CCI-002130CCI-001405CCI-001403CCI-001404CCI-000018CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Account Management >> "Audit Computer Account Management" with "Success" selected.This applies to domain controllers. It is NA for other systems. + +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Computer Account Management - SuccessSRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>WN19-AC-000020Windows Server 2019 must have the number of allowed bad logon attempts configured to three or less.<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 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93141SV-103229CCI-000044Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout threshold" to "3" or fewer invalid logon attempts (excluding "0", which is unacceptable).Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. + +If the "Account lockout threshold" is "0" or more than "3" attempts, this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "LockoutBadCount" equals "0" or is greater than "3" in the file, this is a finding.SRG-OS-000021-GPOS-00005<GroupDescription></GroupDescription>WN19-AC-000030Windows Server 2019 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.<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. + +Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103231V-93143CCI-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 "15" minutes.Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. + +If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "ResetLockoutCount" is less than "15" in the file, this is a finding.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>WN19-SO-000130Windows Server 2019 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. + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103235V-93147CCI-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.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: LegalNoticeText + +Value Type: REG_SZ +Value: See message text below + +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.SRG-OS-000023-GPOS-00006<GroupDescription></GroupDescription>WN19-SO-000140Windows Server 2019 title for legal banner dialog box must be configured with the appropriate text.<VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103237V-93149CCI-001388CCI-001386CCI-001387CCI-001384CCI-001385CCI-000048Configure 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 an organization-defined equivalent. + +If an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN19-SO-000150.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: LegalNoticeCaption + +Value Type: REG_SZ +Value: See message title options below + +"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. + +If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. + +Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required.SRG-OS-000028-GPOS-00009<GroupDescription></GroupDescription>WN19-SO-000120Windows Server 2019 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver.<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. + +Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-92961SV-103049CCI-000056CCI-000057CCI-000060Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Interactive logon: Machine inactivity limit" to "900" seconds or less, excluding "0" which is effectively 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\Microsoft\Windows\CurrentVersion\Policies\System\ + +Value Name: InactivityTimeoutSecs + +Value Type: REG_DWORD +Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled)SRG-OS-000032-GPOS-00013<GroupDescription></GroupDescription>WN19-AU-000190Windows Server 2019 must be configured to audit 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. + +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-92967SV-103055CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000032-GPOS-00013<GroupDescription></GroupDescription>WN19-AU-000200Windows Server 2019 must be configured to audit 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. + +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-92969SV-103057CCI-000172CCI-000067Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - FailureSRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>WN19-CC-000370Windows Server 2019 Remote Desktop Services must require secure Remote Procedure Call (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. + +Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-92971SV-103059CCI-000068CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: fEncryptRPCTraffic + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000033-GPOS-00014<GroupDescription></GroupDescription>WN19-CC-000380Windows Server 2019 Remote Desktop Services must be configured with the client connection encryption set to High 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. + +Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-92973SV-103061CCI-001453CCI-000068Configure 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" with "High Level" 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 NT\Terminal Services\ + +Value Name: MinEncryptionLevel + +Type: REG_DWORD +Value: 0x00000003 (3)SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>WN19-CC-000090Windows Server 2019 command 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93173SV-103261CCI-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: 0x00000001 (1)SRG-OS-000042-GPOS-00020<GroupDescription></GroupDescription>WN19-CC-000460Windows Server 2019 PowerShell script block logging 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. + +Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103263V-93175CCI-000135Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> "Turn on PowerShell Script Block 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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ + +Value Name: EnableScriptBlockLogging + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>WN19-AU-000030Windows Server 2019 permissions 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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93189SV-103277CCI-000162CCI-000163CCI-000164Configure the permissions on the Application event log file (Application.evtx) to prevent access by non-privileged accounts. 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" folder. + +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".Navigate to the Application event log file. + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. + +If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full ControlSRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>WN19-AU-000040Windows Server 2019 permissions 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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93191SV-103279CCI-000164CCI-000163CCI-000162Configure the permissions on the Security event log file (Security.evtx) to prevent access by non-privileged accounts. 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" folder. + +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".Navigate to the Security event log file. + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. + +If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full ControlSRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>WN19-AU-000050Windows Server 2019 permissions 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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93193SV-103281CCI-000162CCI-000164CCI-000163Configure the permissions on the System event log file (System.evtx) to prevent access by non-privileged accounts. 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" folder. + +If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".Navigate to the System event log file. + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. + +If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full ControlSRG-OS-000057-GPOS-00027<GroupDescription></GroupDescription>WN19-UR-000170Windows Server 2019 Manage auditing and security log user right must only be assigned to the Administrators group.<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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93197SV-103285CCI-000171CCI-000164CCI-000162CCI-000163CCI-001914Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Manage auditing and security log" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeSecurityPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators) + +If the organization has an Auditors group, the assignment of this group to the user right would not be a finding. + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000062-GPOS-00031<GroupDescription></GroupDescription>WN19-SO-000050Windows Server 2019 must force audit policy subcategory settings to override audit policy category settings.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93151SV-103239CCI-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".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\Lsa\ + +Value Name: SCENoApplyLegacyAuditPolicy + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-DC-000280Windows Server 2019 domain controllers must have a PKI server certificate.<VulnDiscussion>Domain controllers are part of the chain of trust for PKI authentications. Without the appropriate certificate, the authenticity of the domain controller cannot be verified. Domain controllers must have a server certificate to establish authenticity as part of PKI authentications in 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93481SV-103567CCI-000185Obtain a server certificate for the domain controller.This applies to domain controllers. It is NA for other systems. + +Run "MMC". + +Select "Add/Remove Snap-in" from the "File" menu. + +Select "Certificates" in the left pane and click the "Add >" button. + +Select "Computer Account" and click "Next". + +Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". + +Click "OK". + +Select and expand the Certificates (Local Computer) entry in the left pane. + +Select and expand the Personal entry in the left pane. + +Select the Certificates entry in the left pane. + +If no certificate for the domain controller exists in the right pane, this is a finding.SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-DC-000290Windows Server 2019 domain Controller PKI certificates must be issued by the DoD PKI or an approved External Certificate Authority (ECA).<VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103569V-93483CCI-000185Obtain a server certificate for the domain controller issued by the DoD PKI or an approved ECA.This applies to domain controllers. It is NA for other systems. + +Run "MMC". + +Select "Add/Remove Snap-in" from the "File" menu. + +Select "Certificates" in the left pane and click the "Add >" button. + +Select "Computer Account" and click "Next". + +Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". + +Click "OK". + +Select and expand the Certificates (Local Computer) entry in the left pane. + +Select and expand the Personal entry in the left pane. + +Select the Certificates entry in the left pane. + +In the right pane, examine the "Issued By" field for the certificate to determine the issuing CA. + +If the "Issued By" field of the PKI certificate being used by the domain controller does not indicate the issuing CA is part of the DoD PKI or an approved ECA, this is a finding. + +If the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding. + +There are multiple sources from which lists of valid DoD CAs and approved ECAs can be obtained: + +The Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil. + +DoD Public Key Enablement (PKE) Engineering Support maintains the InstallRoot utility to manage DoD supported root certificates on Windows computers, which includes a list of authorized CAs. The utility package can be downloaded from the PKI and PKE Tools page on IASE: + +http://iase.disa.mil/pki-pke/function_pages/tools.htmlSRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-DC-000300Windows Server 2019 PKI certificates associated with user accounts must be issued by a DoD PKI or an approved External Certificate Authority (ECA).<VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93485SV-103571CCI-000185Map user accounts to PKI certificates using the appropriate User Principal Name (UPN) for the network. See PKE documentation for details.This applies to domain controllers. It is NA for other systems. + +Review user account mappings to PKI certificates. + +Open "Windows PowerShell". + +Enter "Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled". + +Exclude disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. + +If the User Principal Name (UPN) is not in the format of an individual's identifier for the certificate type and for the appropriate domain suffix, this is a finding. + +For standard NIPRNet certificates, the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI). + +Alt Tokens and other certificates may use a different UPN format than the EDI-PI which vary by organization. Verified these with the organization. + +NIPRNet Example: + +Name - User Principal Name +User1 - 1234567890@mil + +See PKE documentation for other network domain suffixes. + +If the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding.SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-PK-000010Windows Server 2019 must have the DoD Root Certificate Authority (CA) certificates 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 CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. + +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103573V-93487CCI-000185CCI-002470Install the DoD Root CA certificates: + +DoD Root CA 2 +DoD Root CA 3 +DoD Root CA 4 +DoD Root CA 5 + +The InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.The certificates and thumbprints referenced below apply to unclassified systems; see PKE documentation for other networks. + +Open "Windows PowerShell" as an administrator. + +Execute the following command: + +Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint, NotAfter + +If the following certificate "Subject" and "Thumbprint" information is not displayed, this is a finding. + +Subject: CN=DoD Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 +NotAfter: 12/5/2029 + +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB +NotAfter: 12/30/2029 + +Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 +NotAfter: 7/25/2032 + +Subject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B +NotAfter: 6/14/2041 + +Alternately, use the Certificates MMC snap-in: + +Run "MMC". + +Select "File", "Add/Remove Snap-in". + +Select "Certificates" and click "Add". + +Select "Computer account" and click "Next". + +Select "Local computer: (the computer this console is running on)" and click "Finish". + +Click "OK". + +Expand "Certificates" and navigate to "Trusted Root Certification Authorities >> Certificates". + +For each of the DoD Root CA certificates noted below: + +Right-click on the certificate and select "Open". + +Select the "Details" Tab. + +Scroll to the bottom and select "Thumbprint". + +If the DoD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding. + +DoD Root CA 2 +Thumbprint: 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 +Valid to: Wednesday, December 5, 2029 + +DoD Root CA 3 +Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB +Valid to: Sunday, December 30, 2029 + +DoD Root CA 4 +Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026 +Valid to: Sunday, July 25, 2032 + +DoD Root CA 5 +Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B +Valid to: Friday, June 14, 2041SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-PK-000020Windows Server 2019 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates 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. + +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93489SV-103575CCI-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 - A8C27332CCB4CA49554CE55D34062A7DD2850C02 + +DoD Root CA 3 - DoD Interoperability Root CA 2 - AC06108CA348CC03B53795C64BF84403C1DBD341 + +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 are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.This is applicable to unclassified systems. It is NA for others. + +Open "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, NotAfter + +If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. + +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: AC06108CA348CC03B53795C64BF84403C1DBD341 +NotAfter: 1/22/2022 10:22:56 AM + +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: A8C27332CCB4CA49554CE55D34062A7DD2850C02 +NotAfter: 8/26/2022 9:25:51 AM + +Alternately, use the Certificates MMC snap-in: + +Run "MMC". + +Select "File", "Add/Remove Snap-in". + +Select "Certificates" and click "Add". + +Select "Computer account" and click "Next". + +Select "Local computer: (the computer this console is running on)" and 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: DoD Root CA 2 +Issued By: DoD Interoperability Root CA 1 +Thumbprint: A8C27332CCB4CA49554CE55D34062A7DD2850C02 +Valid to: Friday, August 26, 2022 + +Issued To: DoD Root CA 3 +Issued By: DoD Interoperability Root CA 2 +Thumbprint: AC06108CA348CC03B53795C64BF84403C1DBD341 +Valid to: Saturday, January 22, 2022SRG-OS-000066-GPOS-00034<GroupDescription></GroupDescription>WN19-PK-000030Windows Server 2019 must have the US DoD CCEB Interoperability Root CA cross-certificates 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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. + +Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93491SV-103577CCI-000185CCI-002470Install the US DoD CCEB Interoperability Root CA cross-certificate on unclassified systems. + +Issued To - Issued By - Thumbprint + +DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 + +DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - 929BF3196896994C0A201DF4A5B71F603FEFBF2E + +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 are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.This is applicable to unclassified systems. It is NA for others. + +Open "PowerShell" as an administrator. + +Execute the following command: + +Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter + +If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. + +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 +NotAfter: 8/26/2022 9:07:50 AM + +Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US +Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US +Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E +NotAfter: 9/27/2019 + +Alternately, use the Certificates MMC snap-in: + +Run "MMC". + +Select "File", "Add/Remove Snap-in". + +Select "Certificates" and click "Add". + +Select "Computer account" and click "Next". + +Select "Local computer: (the computer this console is running on)" and 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: DoD Root CA 3 +Issued By: US DoD CCEB Interoperability Root CA 2 +Thumbprint: AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 +Valid to: Friday, August 26, 2022 + +Issued To: DoD Root CA 3 +Issued By: US DoD CCEB Interoperability Root CA 2 +Thumbprint: 929BF3196896994C0A201DF4A5B71F603FEFBF2E +Valid: Friday, September 27, 2019SRG-OS-000067-GPOS-00035<GroupDescription></GroupDescription>WN19-SO-000350Windows Server 2019 users must be required to enter a password to access private keys stored on the computer.<VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. + +The cornerstone of the PKI is the private key used to encrypt or digitally sign information. + +If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. + +Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93493SV-103579CCI-000186Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "System cryptography: Force strong key protection for user keys stored on the computer" to "User must enter a password each time they use a key".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\Cryptography\ + +Value Name: ForceKeyProtection + +Type: REG_DWORD +Value: 0x00000002 (2)SRG-OS-000069-GPOS-00037<GroupDescription></GroupDescription>WN19-AC-000080Windows Server 2019 must have the built-in Windows password complexity policy 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 three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. + +Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93459SV-103545CCI-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".Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "PasswordComplexity" equals "0" in the file, this is a finding. + +Note: If an external password filter is in use that enforces all four character types and requires this setting to 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.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>WN19-AC-000090Windows Server 2019 reversible password encryption must be disabled.<VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103551V-93465CCI-000196Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Store passwords using reversible encryption" to "Disabled".Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for "Store passwords using reversible encryption" is not set to "Disabled", this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "ClearTextPassword" equals "1" in the file, this is a finding.SRG-OS-000073-GPOS-00041<GroupDescription></GroupDescription>WN19-SO-000300Windows Server 2019 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 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93467SV-103553CCI-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".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\Lsa\ + +Value Name: NoLMHash + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000074-GPOS-00042<GroupDescription></GroupDescription>WN19-SO-000180Windows Server 2019 unencrypted passwords must not be sent to third-party Server Message Block (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 determine 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93469SV-103555CCI-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".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\Services\LanmanWorkstation\Parameters\ + +Value Name: EnablePlainTextPassword + +Value Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000075-GPOS-00043<GroupDescription></GroupDescription>WN19-AC-000060Windows Server 2019 minimum password age must be configured to at least one day.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103557V-93471CCI-000198Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password age" to at least "1" day.Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for the "Minimum password age" is set to "0" days ("Password can be changed immediately"), this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "MinimumPasswordAge" equals "0" in the file, this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>WN19-00-000020Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days.<VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. + +Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93473SV-103559CCI-000199Change the built-in Administrator account password at least every "60" days. + +Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this.Review the password last set date for the built-in Administrator account. + +Domain controllers: + +Open "PowerShell". + +Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". + +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. + +Member servers and standalone systems: + +Open "Command Prompt". + +Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. + +(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) + +If the "PasswordLastSet" date is greater than "60" days old, this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>WN19-00-000210Windows Server 2019 passwords must be configured to expire.<VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93475SV-103561CCI-000199Configure all enabled user account passwords to expire. + +Uncheck "Password never expires" for all enabled user accounts in Active Directory Users and Computers for domain accounts and Users in Computer Management for member servers and standalone systems. Document any exceptions with the ISSO.Review the password never expires status for enabled user accounts. + +Open "PowerShell". + +Domain Controllers: + +Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". + +Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. + +If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. + +Member servers and standalone systems: + +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. + +Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). + +If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding.SRG-OS-000076-GPOS-00044<GroupDescription></GroupDescription>WN19-AC-000050Windows Server 2019 maximum password age must be configured to 60 days or less.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93477SV-103563CCI-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).Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "MaximumPasswordAge" is greater than "60" or equal to "0" in the file, this is a finding.SRG-OS-000077-GPOS-00045<GroupDescription></GroupDescription>WN19-AC-000040Windows Server 2019 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 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93479SV-103565CCI-000200Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Enforce password history" to "24" passwords remembered.Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "PasswordHistorySize" is less than "24" in the file, this is a finding.SRG-OS-000078-GPOS-00046<GroupDescription></GroupDescription>WN19-00-000050Windows Server 2019 manually managed application 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103547V-93461CCI-000205Establish a policy that requires application/service account passwords that are manually managed to be at least 15 characters in length. Ensure the policy is enforced.Determine if manually managed application/service accounts exist. If none exist, this is NA. + +Verify the organization has 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.SRG-OS-000078-GPOS-00046<GroupDescription></GroupDescription>WN19-AC-000070Windows Server 2019 minimum password length must be configured to 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93463SV-103549CCI-000205Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> "Minimum password length" to "14" characters.Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for the "Minimum password length," is less than "14" characters, this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "MinimumPasswordLength" is less than "14" in the file, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-00-000130Windows Server 2019 local volumes must use a format that supports NTFS attributes.<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 a file system that supports NTFS attributes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-92991SV-103079CCI-000213Format volumes to use NTFS or ReFS.Open "Computer Management". + +Select "Disk Management" under "Storage". + +For each local volume, if the file system does not indicate "NTFS", this is a finding. + +"ReFS" (resilient file system) is also acceptable and would not be a finding. + +This does not apply to system partitions such the Recovery and EFI System Partition.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-00-000180Windows Server 2019 non-administrative accounts or groups must only have print permissions on printer shares.<VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103081V-92993CCI-000213Configure the permissions on shared printers to restrict standard users to only have Print permissions.Open "Printers & scanners" in "Settings". + +If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) + +For each printer: + +Select the printer and "Manage". + +Select "Printer Properties". + +Select the "Sharing" tab. + +If "Share this printer" is checked, select the "Security" tab. + +If any standard user accounts or groups have permissions other than "Print", this is a finding. + +The default is for the "Everyone" group to be given "Print" permission. + +"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000340Windows Server 2019 Access this computer from the network user right must only be assigned to the Administrators, Authenticated Users, and +Enterprise Domain Controllers groups on domain controllers.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Access this computer from the network" right may access resources on the system, and this right must be limited to those requiring it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103083V-92995CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Access this computer from the network" to include only the following accounts or groups: + +- Administrators +- Authenticated Users +- Enterprise Domain ControllersThis applies to domain controllers. It is NA for other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Access this computer from the network" right, this is a finding. + +- Administrators +- Authenticated Users +- Enterprise Domain Controllers + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeNetworkLogonRight" user right, this is a finding. + +S-1-5-32-544 (Administrators) +S-1-5-11 (Authenticated Users) +S-1-5-9 (Enterprise Domain Controllers) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000360Windows Server 2019 Allow log on through Remote Desktop Services user right must only be assigned to the Administrators group on domain controllers.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-92997SV-103085CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on through Remote Desktop Services" to include only the following accounts or groups: + +- AdministratorsThis applies to domain controllers, it is NA for other systems. + +Verify the effective setting in Local Group Policy Editor. +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Allow log on through Remote Desktop Services" user right, this is a finding. + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeRemoteInteractiveLogonRight" user right, this is a finding. + +S-1-5-32-544 (Administrators)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000370Windows Server 2019 Deny access to this computer from the network user right on domain controllers must be configured to prevent unauthenticated access.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny access to this computer from the network" user right defines the accounts that are prevented from logging on from the network. + +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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103087V-92999CCI-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: + +- Guests GroupThis applies to domain controllers. A separate version applies to other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding: + +- Guests Group + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If the following SIDs are not defined for the "SeDenyNetworkLogonRight" user right, this is a finding. + +S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000380Windows Server 2019 Deny log on as a batch job user right on domain controllers must be configured to prevent unauthenticated access.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on as a batch job" user right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler. + +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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103089V-93001CCI-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: + +- Guests GroupThis applies to domain controllers. A separate version applies to other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding: + +- Guests Group + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If the following SID(s) are not defined for the "SeDenyBatchLogonRight" user right, this is a finding: + +S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000390Windows Server 2019 Deny log on as a service user right must be configured to include no accounts or groups (blank) on domain controllers.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on as a service" user right defines accounts that are denied logon as a service. + +Incorrect configurations could prevent services from starting and result in a denial of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93003SV-103091CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on as a service" to include no entries (blank).This applies to domain controllers. A separate version applies to other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups are defined for the "Deny log on as a service" user right, this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs are granted the "SeDenyServiceLogonRight" user right, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-DC-000400Windows Server 2019 Deny log on locally user right on domain controllers must be configured to prevent unauthenticated access.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on locally" user right defines accounts that are prevented from logging on interactively. + +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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103093V-93005CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on locally" to include the following: + +- Guests GroupThis applies to domain controllers. A separate version applies to other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: + +- Guests Group + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If the following SID(s) are not defined for the "SeDenyInteractiveLogonRight" user right, this is a finding: + +S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000070Windows Server 2019 Access this computer from the network user right must only be assigned to the Administrators and Authenticated Users groups on domain-joined member servers and standalone systems.<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 this right must be limited to those requiring it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93007SV-103095CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Access this computer from the network" to include only the following accounts or groups: + +- Administrators +- Authenticated UsersThis applies to member servers and standalone systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators +- Authenticated Users + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeNetworkLogonRight" user right, this is a finding: + +S-1-5-32-544 (Administrators) +S-1-5-11 (Authenticated Users) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000080Windows Server 2019 Deny access to this computer from the network user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and local accounts and from 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" user 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93009SV-103097CCI-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 and member of Administrators group" or "Local account" (see Note below) + +All Systems: +- Guests group + +Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering.This applies to member servers and standalone systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding: + +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- "Local account and member of Administrators group" or "Local account" (see Note below) + +All Systems: +- Guests group + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If the following SIDs are not defined for the "SeDenyNetworkLogonRight" user right, this is a finding. + +Domain Systems Only: +S-1-5-root domain-519 (Enterprise Admins) +S-1-5-domain-512 (Domain Admins) +S-1-5-114 ("Local account and member of Administrators group") or S-1-5-113 ("Local account") + +All Systems: +S-1-5-32-546 (Guests) + +Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000090Windows Server 2019 Deny log on as a batch job user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from 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" user 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93011SV-103099CCI-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 Admins Group +- Domain Admins Group + +All Systems: +- Guests GroupThis applies to member servers and standalone systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding: + +Domain Systems Only: +- Enterprise Admins Group +- Domain Admins Group + +All Systems: +- Guests Group + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If the following SIDs are not defined for the "SeDenyBatchLogonRight" user right, this is a finding. + +Domain Systems Only: +S-1-5-root domain-519 (Enterprise Admins) +S-1-5-domain-512 (Domain Admins) + +All Systems: +S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000100Windows Server 2019 Deny log on as a service user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts. No other groups or accounts must be assigned this right.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on as a service" user right defines accounts that are denied logon 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 denial of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103101V-93013CCI-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: + +Domain systems: +- Enterprise Admins Group +- Domain Admins GroupThis applies to member servers and standalone systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on as a service" user right on domain-joined systems, this is a finding: + +- Enterprise Admins Group +- Domain Admins Group + +If any accounts or groups are defined for the "Deny log on as a service" user right on non-domain-joined systems, this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If the following SIDs are not defined for the "SeDenyServiceLogonRight" user right on domain-joined systems, this is a finding: + +S-1-5-root domain-519 (Enterprise Admins) +S-1-5-domain-512 (Domain Admins) + +If any SIDs are defined for the user right on non-domain-joined systems, this is a finding.SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-MS-000110Windows Server 2019 Deny log on locally user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from 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" user 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103103V-93015CCI-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 + +All Systems: +- Guests GroupThis applies to member servers and standalone systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding: + +Domain Systems Only: +- Enterprise Admins Group +- Domain Admins Group + +All Systems: +- Guests Group + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If the following SIDs are not defined for the "SeDenyInteractiveLogonRight" user right, this is a finding: + +Domain Systems Only: +S-1-5-root domain-519 (Enterprise Admins) +S-1-5-domain-512 (Domain Admins) + +All Systems: +S-1-5-32-546 (Guests)SRG-OS-000080-GPOS-00048<GroupDescription></GroupDescription>WN19-UR-000030Windows Server 2019 Allow log on locally user right must only be assigned to the Administrators group.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93017SV-103105CCI-000213Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Allow log on locally" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeInteractiveLogonRight" user right, this is a finding: + +S-1-5-32-544 (Administrators) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000270Windows Server 2019 must have the roles and features required by the system documented.<VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103467V-93381CCI-000381Document the roles and features required for the system to operate. Uninstall any that are not required.Required roles and features will vary based on the function of the individual system. + +Roles and features specifically required to be disabled per the STIG are identified in separate requirements. + +If the organization has not documented the roles and features required for the system(s), this is a finding. + +The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State".SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000320Windows Server 2019 must not have the Fax Server role installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93383SV-103469CCI-000381Uninstall the "Fax Server" role. + +Start "Server Manager". + +Select the server with the role. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Fax Server" on the "Roles" page. + +Click "Next" and "Remove" as prompted.Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Fax". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000340Windows Server 2019 must not have the Peer Name Resolution Protocol installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103471V-93385CCI-000381Uninstall the "Peer Name Resolution Protocol" feature. + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Peer Name Resolution Protocol" on the "Features" page. + +Click "Next" and "Remove" as prompted.Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq PNRP". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000350Windows Server 2019 must not have Simple TCP/IP Services installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93387SV-103473CCI-000381Uninstall the "Simple TCP/IP Services" feature. + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Simple TCP/IP Services" on the "Features" page. + +Click "Next" and "Remove" as prompted.Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Simple-TCPIP". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000370Windows Server 2019 must not have the TFTP Client installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103475V-93389CCI-000381Uninstall the "TFTP Client" feature. + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "TFTP Client" on the "Features" page. + +Click "Next" and "Remove" as prompted.Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq TFTP-Client". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000380Windows Server 2019 must not the Server Message Block (SMB) v1 protocol installed.<VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93391SV-103477CCI-000381Uninstall the SMBv1 protocol. + +Open "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Uninstall-WindowsFeature -Name FS-SMB1 -Restart". +(Omit the Restart parameter if an immediate restart of the system cannot be done.) + +Alternately: + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "SMB 1.0/CIFS File Sharing Support" on the "Features" page. + +Click "Next" and "Remove" as prompted.Different methods are available to disable SMBv1 on Windows Server 2019. This is the preferred method, however if WN19-00-000390 and WN19-00-000400 are configured, this is NA. + +Open "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-WindowsFeature -Name FS-SMB1". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000390Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server.<VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103479V-93393CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 Server" to "Disabled". + +The system must be restarted for the change to take effect. + +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.Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, 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: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ + +Value Name: SMB1 + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000400Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client.<VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93395SV-103481CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Configure SMBv1 client driver" to "Enabled" with "Disable driver (recommended)" selected for "Configure MrxSmb10 driver". + +The system must be restarted for the changes to take effect. + +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.Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. + +If the following registry value is not configured as specified, this is a finding: + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ + +Value Name: Start + +Type: REG_DWORD +Value: 0x00000004 (4)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-00-000410Windows Server 2019 must not have Windows PowerShell 2.0 installed.<VulnDiscussion>Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93397SV-103483CCI-000381Uninstall the "Windows PowerShell 2.0 Engine". + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell" on the "Features" page. + +Click "Next" and "Remove" as prompted.Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq PowerShell-v2". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000010Windows Server 2019 must prevent the display of slide shows on the lock screen.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93399SV-103485CCI-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: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000020Windows Server 2019 must have WDigest Authentication 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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103487V-93401CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "WDigest Authentication (disabling may require KB2871997)" to "Disabled". + +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)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000150Windows Server 2019 downloading print driver packages over HTTP 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 will prevent 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103489V-93403CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ + +Value Name: DisableWebPnPDownload + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000160Windows Server 2019 printing over HTTP 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 will prevent 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103491V-93405CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ + +Value Name: DisableHTTPPrinting + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000170Windows Server 2019 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 in to 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103493V-93407CCI-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: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000200Windows Server 2019 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 will prevent 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93409SV-103495CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\ + +Value Name: DisableInventory + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000300Windows Server 2019 Windows Defender SmartScreen must be enabled.<VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93411SV-103497CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Configure Windows Defender SmartScreen" to "Enabled" with either option "Warn" or "Warn and prevent bypass" selected. + +Windows 2019 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer.This is applicable to unclassified systems; for other systems, 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\Windows\System\ + +Value Name: EnableSmartScreen + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000400Windows Server 2019 must disable Basic authentication for RSS feeds over HTTP.<VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93413SV-103499CCI-000381The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> "Turn on Basic feed authentication over HTTP" to "Not Configured" or "Disabled".The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ + +Value Name: AllowBasicAuthInClear + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000410Windows Server 2019 must prevent Indexing of encrypted files.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93415SV-103501CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\ + +Value Name: AllowIndexingEncryptedStoresOrItems + +Value Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-DC-000130Windows Server 2019 domain controllers must run on a machine dedicated to that function.<VulnDiscussion>Executing application servers on the same host machine with a directory server may substantially weaken the security of the directory server. Web or database server applications usually require the addition of many programs and accounts, increasing the attack surface of the computer. + +Some applications require the addition of privileged accounts, providing potential sources of compromise. Some applications (such as Microsoft Exchange) may require the use of network ports or services conflicting with the directory server. In this case, non-standard ports might be selected, and this could interfere with intrusion detection or prevention 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103503V-93417CCI-000381Remove additional roles or applications such as web, database, and email from the domain controller.This applies to domain controllers, it is NA for other systems. + +Review the installed roles the domain controller is supporting. + +Start "Server Manager". + +Select "AD DS" in the left pane and the server name under "Servers" to the right. + +Select "Add (or Remove) Roles and Features" from "Tasks" in the "Roles and Features" section. (Cancel before any changes are made.) + +Determine if any additional server roles are installed. A basic domain controller setup will include the following: + +- Active Directory Domain Services +- DNS Server +- File and Storage Services + +If any roles not requiring installation on a domain controller are installed, this is a finding. + +A Domain Name System (DNS) server integrated with the directory server (e.g., AD-integrated DNS) is an acceptable application. However, the DNS server must comply with the DNS STIG security requirements. + +Run "Programs and Features". + +Review installed applications. + +If any applications are installed that are not required for the domain controller, this is a finding.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-MS-000030Windows Server 2019 local users on domain-joined member servers 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103505V-93419CCI-000381Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> "Enumerate local users on domain-joined computers" to "Disabled".This applies to member servers. For domain controllers and standalone systems, 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\Windows\System\ + +Value Name: EnumerateLocalUsers + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>WN19-00-000330Windows Server 2019 must not have the Microsoft FTP service installed unless required by the organization.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103507V-93421CCI-000382Uninstall the "FTP Server" role. + +Start "Server Manager". + +Select the server with the role. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "FTP Server" under "Web Server (IIS)" on the "Roles" page. + +Click "Next" and "Remove" as prompted.If the server has the role of an FTP server, this is NA. + +Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Web-Ftp-Service". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding. + +If the system has the role of an FTP server, this must be documented with the ISSO.SRG-OS-000096-GPOS-00050<GroupDescription></GroupDescription>WN19-00-000360Windows Server 2019 must not have the Telnet Client installed.<VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93423SV-103509CCI-000382Uninstall the "Telnet Client" feature. + +Start "Server Manager". + +Select the server with the feature. + +Scroll down to "ROLES AND FEATURES" in the right pane. + +Select "Remove Roles and Features" from the drop-down "TASKS" list. + +Select the appropriate server on the "Server Selection" page and click "Next". + +Deselect "Telnet Client" on the "Features" page. + +Click "Next" and "Remove" as prompted.Open "PowerShell". + +Enter "Get-WindowsFeature | Where Name -eq Telnet-Client". + +If "Installed State" is "Installed", this is a finding. + +An Installed State of "Available" or "Removed" is not a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>WN19-00-000070Windows Server 2019 shared user accounts must not be permitted.<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 nonrepudiation or individual accountability for system access and resource usage.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103523V-93437CCI-000764Remove unapproved shared accounts from the system. + +Document required shared accounts with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity.Determine whether any shared accounts exist. If no shared accounts exist, this is NA. + +Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. + +If unapproved shared accounts exist, this is a finding.SRG-OS-000104-GPOS-00051<GroupDescription></GroupDescription>WN19-00-000200Windows Server 2019 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. 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103525V-93439CCI-000764Configure all enabled accounts to require passwords. + +The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account.Review the password required status for enabled user accounts. + +Open "PowerShell". + +Domain Controllers: + +Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". + +Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). + +If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. + +Member servers and standalone systems: + +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. + +Exclude disabled accounts (e.g., DefaultAccount, Guest). + +If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding.SRG-OS-000105-GPOS-00052<GroupDescription></GroupDescription>WN19-DC-000310Windows Server 2019 Active Directory user accounts, including administrators, must be configured to require the use of a Common Access Card (CAC), Personal Identity Verification (PIV)-compliant hardware token, or Alternate Logon Token (ALT) for user authentication.<VulnDiscussion>Smart cards such as the CAC support a two-factor authentication technique. This provides a higher level of trust in the asserted identity than use of the username and password for authentication. + +Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103527V-93441CCI-000765CCI-000766CCI-000767CCI-000768CCI-001948Configure all user accounts, including administrator accounts, in Active Directory to enable the option "Smart card is required for interactive logon". + +Run "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): + +Select the OU where the user accounts are located. (By default this is the Users node; however, accounts may be under other organization-defined OUs.) + +Right-click the user account and select "Properties". + +Select the "Account" tab. + +Check "Smart card is required for interactive logon" in the "Account Options" area.This applies to domain controllers. It is NA for other systems. + +Open "PowerShell". + +Enter the following: + +"Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name" +("DistinguishedName" may be substituted for "Name" for more detailed output.) + +If any user accounts, including administrators, are listed, this is a finding. + + +Alternately: + +To view sample accounts in "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): + +Select the Organizational Unit (OU) where the user accounts are located. (By default, this is the Users node; however, accounts may be under other organization-defined OUs.) + +Right-click the sample user account and select "Properties". + +Select the "Account" tab. + +If any user accounts, including administrators, do not have "Smart card is required for interactive logon" checked in the "Account Options" area, this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000020Windows Server 2019 Kerberos user logon restrictions must be enforced.<VulnDiscussion>This policy setting determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer. The policy is enabled by default, which is the most secure setting for validating that access to target resources is not circumvented. + +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93443SV-103529CCI-001941CCI-001942Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Enforce user logon restrictions" to "Enabled".This applies to domain controllers. It is NA for other systems. + +Verify the following is configured in the Default Domain Policy: + +Open "Group Policy Management". + +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). + +Right-click on the "Default Domain Policy". + +Select "Edit". + +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. + +If the "Enforce user logon restrictions" is not set to "Enabled", this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000030Windows Server 2019 Kerberos service ticket maximum lifetime must be limited to 600 minutes or less.<VulnDiscussion>This setting determines the maximum amount of time (in minutes) that a granted session ticket can be used to access a particular service. Session tickets are used only to authenticate new connections with servers. Ongoing operations are not interrupted if the session ticket used to authenticate the connection expires during the connection. + +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103531V-93445CCI-001942CCI-001941Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for service ticket" to a maximum of "600" minutes, but not "0", which equates to "Ticket doesn't expire".This applies to domain controllers. It is NA for other systems. + +Verify the following is configured in the Default Domain Policy: + +Open "Group Policy Management". + +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). + +Right-click on the "Default Domain Policy". + +Select "Edit". + +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. + +If the value for "Maximum lifetime for service ticket" is "0" or greater than "600" minutes, this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000040Windows Server 2019 Kerberos user ticket lifetime must be limited to 10 hours or less.<VulnDiscussion>In Kerberos, there are two types of tickets: Ticket Granting Tickets (TGTs) and Service Tickets. Kerberos tickets have a limited lifetime so the time an attacker has to implement an attack is limited. This policy controls how long TGTs can be renewed. With Kerberos, the user's initial authentication to the domain controller results in a TGT, which is then used to request Service Tickets to resources. Upon startup, each computer gets a TGT before requesting a service ticket to the domain controller and any other computers it needs to access. For services that start up under a specified user account, users must always get a TGT first and then get Service Tickets to all computers and services accessed. + +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93447SV-103533CCI-001941CCI-001942Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for user ticket" to a maximum of "10" hours but not "0", which equates to "Ticket doesn't expire".This applies to domain controllers. It is NA for other systems. + +Verify the following is configured in the Default Domain Policy: + +Open "Group Policy Management". + +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). + +Right-click on the "Default Domain Policy". + +Select "Edit". + +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. + +If the value for "Maximum lifetime for user ticket" is "0" or greater than "10" hours, this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000050Windows Server 2019 Kerberos policy user ticket renewal maximum lifetime must be limited to seven days or less.<VulnDiscussion>This setting determines the period of time (in days) during which a user's Ticket Granting Ticket (TGT) may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access. + +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103535V-93449CCI-001942CCI-001941Configure the policy value in the Default Domain Policy for Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum lifetime for user ticket renewal" to a maximum of "7" days or less.This applies to domain controllers. It is NA for other systems. + +Verify the following is configured in the Default Domain Policy: + +Open "Group Policy Management". + +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). + +Right-click on the "Default Domain Policy". + +Select "Edit". + +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. + +If the "Maximum lifetime for user ticket renewal" is greater than "7" days, this is a finding.SRG-OS-000112-GPOS-00057<GroupDescription></GroupDescription>WN19-DC-000060Windows Server 2019 computer clock synchronization tolerance must be limited to five minutes or less.<VulnDiscussion>This setting determines the maximum time difference (in minutes) that Kerberos will tolerate between the time on a client's clock and the time on a server's clock while still considering the two clocks synchronous. In order to prevent replay attacks, Kerberos uses timestamps as part of its protocol definition. For timestamps to work properly, the clocks of the client and the server need to be in sync as much as possible. + +Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93451SV-103537CCI-001941CCI-001942Configure the policy value in the Default Domain Policy for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy >> "Maximum tolerance for computer clock synchronization" to a maximum of "5" minutes or less.This applies to domain controllers. It is NA for other systems. + +Verify the following is configured in the Default Domain Policy: + +Open "Group Policy Management". + +Navigate to "Group Policy Objects" in the Domain being reviewed (Forest >> Domains >> Domain). + +Right-click on the "Default Domain Policy". + +Select "Edit". + +Navigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy. + +If the "Maximum tolerance for computer clock synchronization" is greater than "5" minutes, this is a finding.SRG-OS-000118-GPOS-00060<GroupDescription></GroupDescription>WN19-00-000190Windows Server 2019 outdated or unused accounts must be removed or disabled.<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, disabled 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93457SV-103543CCI-000795Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days.Open "Windows PowerShell". + +Domain Controllers: + +Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" + +This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. + +Member servers and standalone systems: + +Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) + +"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { + $user = ([ADSI]$_.Path) + $lastLogin = $user.Properties.LastLogin.Value + $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 + if ($lastLogin -eq $null) { + $lastLogin = 'Never' + } + Write-Host $user.Name $lastLogin $enabled +}" + +This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). +For example: User1 10/31/2015 5:49:56 AM True + +Review the list of accounts returned by the above queries to determine the finding validity for each account reported. + +Exclude the following accounts: + +- Built-in administrator account (Renamed, SID ending in 500) +- Built-in guest account (Renamed, Disabled, SID ending in 501) +- Application accounts + +If any enabled accounts have not been logged on to within the past 35 days, this is a finding. + +Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO.SRG-OS-000120-GPOS-00061<GroupDescription></GroupDescription>WN19-SO-000290Windows Server 2019 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites.<VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. + +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93495SV-103581CCI-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: + +AES128_HMAC_SHA1 +AES256_HMAC_SHA1 +Future encryption types + +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.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\Kerberos\Parameters\ + +Value Name: SupportedEncryptionTypes + +Value Type: REG_DWORD +Value: 0x7ffffff8 (2147483640)SRG-OS-000121-GPOS-00062<GroupDescription></GroupDescription>WN19-SO-000010Windows Server 2019 must have the built-in guest account disabled.<VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93497SV-103583CCI-000804Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Accounts: Guest account status" to "Disabled".Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. + +If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "EnableGuestAccount" equals "1" in the file, this is a finding.SRG-OS-000123-GPOS-00064<GroupDescription></GroupDescription>WN19-00-000310Windows Server 2019 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours.<VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. + +Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. + +To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-92977SV-103065CCI-001682Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours. + +Domain accounts can be configured with an account expiration date, under "Account" properties. + +Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where username is the name of the temporary user account.Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. + +If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. + +If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. + +Domain Controllers: + +Open "PowerShell". + +Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". + +If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. + +Member servers and standalone systems: + +Open "Command Prompt". + +Run "Net user [username]", where [username] is the name of the emergency account. + +If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding.SRG-OS-000125-GPOS-00065<GroupDescription></GroupDescription>WN19-CC-000470Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93503SV-103589CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ + +Value Name: AllowBasic + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000125-GPOS-00065<GroupDescription></GroupDescription>WN19-CC-000490Windows Server 2019 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. Disallowing Digest authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103591V-93505CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ + +Value Name: AllowDigest + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000125-GPOS-00065<GroupDescription></GroupDescription>WN19-CC-000500Windows Server 2019 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. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93507SV-103593CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ + +Value Name: AllowBasic + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-CC-000240Windows Server 2019 administrator accounts must not be enumerated during elevation.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93517SV-103603CCI-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 +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ + +Value Name: EnumerateAdministrators + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-MS-000020Windows Server 2019 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers.<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 local 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93519SV-103605CCI-001084Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> "Apply UAC restrictions to local accounts on network logons" to "Enabled". + +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.This applies to member servers. For domain controllers and standalone systems, 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: LocalAccountTokenFilterPolicy + +Type: REG_DWORD +Value: 0x00000000 (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.SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000390Windows Server 2019 UIAccess applications must not be allowed to prompt for elevation without using 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 prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93521SV-103607CCI-001084Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop" to "Disabled".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: EnableUIADesktopToggle + +Value Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000400Windows Server 2019 User Account Control must, at a 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103609V-93523CCI-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". + +The more secure option for this setting, "Prompt for credentials on the secure desktop", would also be acceptable.UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: ConsentPromptBehaviorAdmin + +Value Type: REG_DWORD +Value: 0x00000002 (2) (Prompt for consent on the secure desktop) +0x00000001 (1) (Prompt for credentials on the secure desktop)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000420Windows Server 2019 User 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103611V-93525CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: EnableInstallerDetection + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000430Windows Server 2019 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.<VulnDiscussion>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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93527SV-103613CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: EnableSecureUIAPaths + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000134-GPOS-00068<GroupDescription></GroupDescription>WN19-SO-000450Windows Server 2019 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.<VulnDiscussion>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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93529SV-103615CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: EnableVirtualization + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-00-000230Windows Server 2019 non-system-created file shares must limit access to groups that require it.<VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103617V-93531CCI-001090If a non-system-created 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.If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) + +Run "Computer Management". + +Navigate to System Tools >> Shared Folders >> Shares. + +Right-click any non-system-created shares. + +Select "Properties". + +Select the "Share Permissions" tab. + +If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. + +Select the "Security" tab. + +If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding.SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-CC-000350Windows Server 2019 Remote Desktop Services must prevent drive redirection.<VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103619V-93533CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: fDisableCdm + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-DC-000120Windows Server 2019 data files owned by users must be on a different logical partition from the directory server data files.<VulnDiscussion>When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. + +The directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93535SV-103621CCI-001090Move shares used to store files owned by users to a different logical partition than the directory server data files.This applies to domain controllers. It is NA for other systems. + +Run "Regedit". + +Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". + +Note the directory locations in the values for "DSA Database file". + +Open "Command Prompt". + +Enter "net share". + +Note the logical drive(s) or file system partition for any organization-created data shares. + +Ignore system shares (e.g., NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) should not be ignored. + +If user shares are located on the same logical partition as the directory server data files, this is a finding.SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-SO-000230Windows Server 2019 must not allow anonymous enumeration of shares.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93537SV-103623CCI-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".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\Lsa\ + +Value Name: RestrictAnonymous + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000138-GPOS-00069<GroupDescription></GroupDescription>WN19-SO-000250Windows Server 2019 must restrict anonymous access to Named Pipes and Shares.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93539SV-103625CCI-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".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\Services\LanManServer\Parameters\ + +Value Name: RestrictNullSessAccess + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000163-GPOS-00072<GroupDescription></GroupDescription>WN19-DC-000160Windows Server 2019 directory service must be configured to terminate LDAP-based network connections to the directory server after five minutes of inactivity.<VulnDiscussion>The failure to terminate inactive network connections increases the risk of a successful attack on the directory server. The longer an established session is in progress, the more time an attacker has to hijack the session, implement a means to passively intercept data, or compromise any protections on client access. For example, if an attacker gains control of a client computer, an existing (already authenticated) session with the directory server could allow access to the directory. The lack of confidentiality protection in LDAP-based sessions increases exposure to this vulnerability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103595V-93509CCI-001133Configure the directory service to terminate LDAP-based network connections to the directory server after 5 minutes of inactivity. + +Open an elevated "Command prompt" (run as administrator). + +Enter "ntdsutil". + +At the "ntdsutil:" prompt, enter "LDAP policies". + +At the "ldap policy:" prompt, enter "connections". + +At the "server connections:" prompt, enter "connect to server [host-name]" (where [host-name] is the computer name of the domain controller). + +At the "server connections:" prompt, enter "q". + +At the "ldap policy:" prompt, enter "Set MaxConnIdleTime to 300". + +Enter "Commit Changes" to save. + +Enter "Show values" to verify changes. + +Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit.This applies to domain controllers. It is NA for other systems. + +Open an elevated "Command Prompt" (run as administrator). + +Enter "ntdsutil". + +At the "ntdsutil:" prompt, enter "LDAP policies". + +At the "ldap policy:" prompt, enter "connections". + +At the "server connections:" prompt, enter "connect to server [host-name]" +(where [host-name] is the computer name of the domain controller). + +At the "server connections:" prompt, enter "q". + +At the "ldap policy:" prompt, enter "show values". + +If the value for MaxConnIdleTime is greater than "300" (5 minutes) or is not specified, this is a finding. + +Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit. + +Alternately, Dsquery can be used to display MaxConnIdleTime: + +Open "Command Prompt (Admin)". +Enter the following command (on a single line). + +dsquery * "cn=Default Query Policy,cn=Query-Policies,cn=Directory Service, cn=Windows NT,cn=Services,cn=Configuration,dc=[forest-name]" -attr LDAPAdminLimits + +The quotes are required and dc=[forest-name] is the fully qualified LDAP name of the domain being reviewed (e.g., dc=disaost,dc=mil). + +If the results do not specify a "MaxConnIdleTime" or it has a value greater than "300" (5 minutes), this is a finding.SRG-OS-000185-GPOS-00079<GroupDescription></GroupDescription>WN19-00-000250Windows Server 2019 systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.<VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. + +Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). + +Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93515SV-103601CCI-001199CCI-002475CCI-002476Configure systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data to employ encryption to protect the confidentiality and integrity of all information at rest.Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. + +If they do not, this is a finding.SRG-OS-000191-GPOS-00080<GroupDescription></GroupDescription>WN19-00-000290Windows Server 2019 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Host Based Security System (HBSS) is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).<VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103653V-93567CCI-001233Install a DoD-approved ESS software and ensure it is operating continuously.Verify DoD-approved ESS software is installed and properly operating. Ask the site ISSM for documentation of the ESS software installation and configuration. + +If the ISSM is not able to provide a documented configuration for an installed ESS or if the ESS software is not properly maintained or used, this is a finding. + +Note: Example of documentation can be a copy of the site's CCB approved Software Baseline with version of software noted or a memo from the ISSM stating current ESS software and version.SRG-OS-000240-GPOS-00090<GroupDescription></GroupDescription>WN19-AU-000150Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. + +Account Lockout events can be used to identify potentially malicious logon attempts. + +Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103075V-92987CCI-001404CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Account Lockout - SuccessSRG-OS-000240-GPOS-00090<GroupDescription></GroupDescription>WN19-AU-000160Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout 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. + +Account Lockout events can be used to identify potentially malicious logon attempts. + +Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-92989SV-103077CCI-000172CCI-001404Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Account Lockout - FailureSRG-OS-000257-GPOS-00098<GroupDescription></GroupDescription>WN19-AU-000060Windows Server 2019 Event Viewer must be protected from unauthorized modification and deletion.<VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. + +Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. + +Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103283V-93195CCI-001494CCI-001495Configure the permissions on the "Eventvwr.exe" file to prevent modification by any groups or accounts other than TrustedInstaller. The default permissions listed below satisfy this requirement: + +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute + +The default location is the "%SystemRoot%\System32" folder.Navigate to "%SystemRoot%\System32". + +View the permissions on "Eventvwr.exe". + +If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. + +The default permissions below satisfy this requirement: + +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & ExecuteSRG-OS-000297-GPOS-00115<GroupDescription></GroupDescription>WN19-DC-000410Windows Server 2019 Deny log on through Remote Desktop Services user right on domain controllers must be configured to prevent unauthenticated access.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. + +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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103051V-92963CCI-002314Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on through Remote Desktop Services" to include the following: + +- Guests GroupThis applies to domain controllers. A separate version applies to other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: + +- Guests Group + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If the following SID(s) are not defined for the "SeDenyRemoteInteractiveLogonRight" user right, this is a finding. + +S-1-5-32-546 (Guests)SRG-OS-000297-GPOS-00115<GroupDescription></GroupDescription>WN19-MS-000120Windows Server 2019 Deny log on through Remote Desktop Services user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and all local accounts and from 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" user right defines the accounts that are prevented from logging on using Remote Desktop Services. + +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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103053V-92965CCI-002314Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Deny log on through Remote Desktop Services" to include the following: + +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- Local account (see Note below) + +All Systems: +- Guests group + +Note: "Local account" is referring to the Windows built-in security group.This applies to member servers and standalone systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: + +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- Local account (see Note below) + +All Systems: +- Guests group + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If the following SIDs are not defined for the "SeDenyRemoteInteractiveLogonRight" user right, this is a finding. + +Domain Systems Only: +S-1-5-root domain-519 (Enterprise Admins) +S-1-5-domain-512 (Domain Admins) +S-1-5-113 ("Local account") + +All Systems: +S-1-5-32-546 (Guests) + +Note: "Local account" is referring to the Windows built-in security group.SRG-OS-000312-GPOS-00122<GroupDescription></GroupDescription>WN19-00-000140Windows Server 2019 permissions for the system drive root directory (usually C:\) 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. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93019SV-103107CCI-002165Maintain the default permissions for the system drive's root directory and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). + +Default Permissions +C:\ +Type - "Allow" for all +Inherited from - "None" for all + +Principal - Access - Applies to + +SYSTEM - Full control - This folder, subfolders, and files +Administrators - Full control - This folder, subfolders, and files +Users - Read & execute - This folder, subfolders, and files +Users - Create folders/append data - This folder and subfolders +Users - Create files/write data - Subfolders only +CREATOR OWNER - Full Control - Subfolders and files onlyThe default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Review the permissions for the system drive's root directory (usually C:\). 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. + +If permissions are not as restrictive as the default permissions listed below, this is a finding. + +Viewing in File Explorer: + +View the Properties of the system drive's root directory. + +Select the "Security" tab, and the "Advanced" button. + +Default permissions: +C:\ +Type - "Allow" for all +Inherited from - "None" for all + +Principal - Access - Applies to + +SYSTEM - Full control - This folder, subfolders, and files +Administrators - Full control - This folder, subfolders, and files +Users - Read & execute - This folder, subfolders, and files +Users - Create folders/append data - This folder and subfolders +Users - Create files/write data - Subfolders only +CREATOR OWNER - Full Control - Subfolders and files only + +Alternately, use icacls: + +Open "Command Prompt (Admin)". + +Enter "icacls" followed by the directory: + +"icacls c:\" + +The following results should be displayed: + +c:\ +NT AUTHORITY\SYSTEM:(OI)(CI)(F) +BUILTIN\Administrators:(OI)(CI)(F) +BUILTIN\Users:(OI)(CI)(RX) +BUILTIN\Users:(CI)(AD) +BUILTIN\Users:(CI)(IO)(WD) +CREATOR OWNER:(OI)(CI)(IO)(F) +Successfully processed 1 files; Failed processing 0 filesSRG-OS-000312-GPOS-00122<GroupDescription></GroupDescription>WN19-00-000150Windows Server 2019 permissions for program file 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. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93021SV-103109CCI-002165Maintain the default permissions for the program file directories and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). + +Default permissions: +\Program Files and \Program Files (x86) +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and filesThe default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Review the permissions for the program file directories (Program Files and Program Files [x86]). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. + +If permissions are not as restrictive as the default permissions listed below, this is a finding. + +Viewing in File Explorer: + +For each folder, view the Properties. + +Select the "Security" tab, and the "Advanced" button. + +Default permissions: +\Program Files and \Program Files (x86) +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + +Alternately, use icacls: + +Open a Command prompt (admin). + +Enter "icacls" followed by the directory: + +'icacls "c:\program files"' +'icacls "c:\program files (x86)"' + +The following results should be displayed for each when entered: + +c:\program files (c:\program files (x86)) +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) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +Successfully processed 1 files; Failed processing 0 filesSRG-OS-000312-GPOS-00122<GroupDescription></GroupDescription>WN19-00-000160Windows Server 2019 permissions for the Windows installation directory 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. + +The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103111V-93023CCI-002165Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN19-SO-000240). + +Default permissions: +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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and filesThe default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN19-SO-000240). + +Review the permissions for the Windows installation directory (usually C:\Windows). Non-privileged groups such as Users or Authenticated Users must not have greater than "Read & execute" permissions. Individual accounts must not be used to assign permissions. + +If permissions are not as restrictive as the default permissions listed below, this is a finding: + +Viewing in File Explorer: + +For each folder, view the Properties. + +Select the "Security" tab and the "Advanced" button. + +Default permissions: +\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 +ALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files + +Alternately, use icacls: + +Open a Command prompt (admin). + +Enter "icacls" followed by the directory: + +"icacls c:\windows" + +The following results should be displayed for each when entered: + +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) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) +APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) +Successfully processed 1 files; Failed processing 0 filesSRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-00-000170Windows Server 2019 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained.<VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103113V-93025CCI-002235Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive. + +The default permissions of the higher-level keys are noted below. + +HKEY_LOCAL_MACHINE\SECURITY + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +SYSTEM - Full Control - This key and subkeys +Administrators - Special - This key and subkeys + +HKEY_LOCAL_MACHINE\SOFTWARE + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - This key and subkeys +ALL APPLICATION PACKAGES - Read - This key and subkeys + +HKEY_LOCAL_MACHINE\SYSTEM + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - Subkeys only +ALL APPLICATION PACKAGES - Read - This key and subkeys + +Microsoft has also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID. +S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. + +If any non-privileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. + +If permissions are not as restrictive as the default permissions listed below, this is a finding: + +Run "Regedit". + +Right-click on the registry areas noted below. + +Select "Permissions" and the "Advanced" button. + +HKEY_LOCAL_MACHINE\SECURITY + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +SYSTEM - Full Control - This key and subkeys +Administrators - Special - This key and subkeys + +HKEY_LOCAL_MACHINE\SOFTWARE + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - This key and subkeys +ALL APPLICATION PACKAGES - Read - This key and subkeys + +HKEY_LOCAL_MACHINE\SYSTEM + +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - Subkeys only +ALL APPLICATION PACKAGES - Read - This key and subkeys + +Other examples under the noted keys may also be sampled. There may be some instances where non-privileged groups have greater than Read permission. + +Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID, this is currently not a finding. +S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 + +If the defaults have not been changed, these are not a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000010Windows Server 2019 must only allow administrators responsible for the domain controller to 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 using only accounts with the minimum level of authority necessary. + +Standard user accounts must not be members of the built-in 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103115V-93027CCI-002235Configure the Administrators group to include only administrator groups or accounts that are responsible for the system. + +Remove any standard user accounts.This applies to domain controllers. A separate version applies to other systems. + +Review the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group. + +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. + +If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000070Windows Server 2019 permissions on the Active Directory data files must only allow System and Administrators access.<VulnDiscussion>Improper access permissions for directory data-related files could allow unauthorized users to read, modify, or delete directory data or audit trails.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103117V-93029CCI-002235Maintain the permissions on NTDS database and log files as follows: + +NT AUTHORITY\SYSTEM:(I)(F) +BUILTIN\Administrators:(I)(F) + +(I) - permission inherited from parent container +(F) - full accessThis applies to domain controllers. It is NA for other systems. + +Run "Regedit". + +Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". + +Note the directory locations in the values for: + +Database log files path +DSA Database file + +By default, they will be \Windows\NTDS. + +If the locations are different, the following will need to be run for each. + +Open "Command Prompt (Admin)". + +Navigate to the NTDS directory (\Windows\NTDS by default). + +Run "icacls *.*". + +If the permissions on each file are not as restrictive as the following, this is a finding: + +NT AUTHORITY\SYSTEM:(I)(F) +BUILTIN\Administrators:(I)(F) + +(I) - permission inherited from parent container +(F) - full accessSRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000080Windows Server 2019 Active Directory SYSVOL directory must have the proper access control permissions.<VulnDiscussion>Improper access permissions for directory data files could allow unauthorized users to read, modify, or delete directory data. + +The SYSVOL directory contains public files (to the domain) such as policies and logon scripts. Data in shared subdirectories are replicated to all domain controllers in a 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93031SV-103119CCI-002235Maintain the permissions on the SYSVOL directory. Do not allow greater than "Read & execute" permissions for standard user accounts or groups. The defaults below meet this requirement: + +C:\Windows\SYSVOL +Type - "Allow" for all +Inherited from - "None" for all + +Principal - Access - Applies to + +Authenticated Users - Read & execute - This folder, subfolder, and files +Server Operators - Read & execute- This folder, subfolder, and files +Administrators - Special - This folder only (Special = Basic Permissions: all selected except Full control) +CREATOR OWNER - Full control - Subfolders and files only +Administrators - Full control - Subfolders and files only +SYSTEM - Full control - This folder, subfolders, and filesThis applies to domain controllers. It is NA for other systems. + +Open a command prompt. + +Run "net share". + +Make note of the directory location of the SYSVOL share. + +By default, this will be \Windows\SYSVOL\sysvol. For this requirement, permissions will be verified at the first SYSVOL directory level. + +If any standard user accounts or groups have greater than "Read & execute" permissions, this is a finding. + +The default permissions noted below meet this requirement: + +Open "Command Prompt". + +Run "icacls c:\Windows\SYSVOL". + +The following results should be displayed: + +NT AUTHORITY\Authenticated Users:(RX) +NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(GR,GE) +BUILTIN\Server Operators:(RX) +BUILTIN\Server Operators:(OI)(CI)(IO)(GR,GE) +BUILTIN\Administrators:(M,WDAC,WO) +BUILTIN\Administrators:(OI)(CI)(IO)(F) +NT AUTHORITY\SYSTEM:(F) +NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) +CREATOR OWNER:(OI)(CI)(IO)(F) + +(RX) - Read & execute + +Run "icacls /help" to view definitions of other permission codes.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000090Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions.<VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems relying on the directory service. + +For Active Directory (AD), the Group Policy objects require special attention. In a distributed administration model (i.e., help desk), Group Policy objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for Group Policy objects, this could allow an intruder to change the security policy applied to all domain client computers (workstations and servers).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93033SV-103121CCI-002235Maintain the permissions on Group Policy objects to not allow greater than "Read" and "Apply group policy" for standard user accounts or groups. The default permissions below meet this requirement: + +Authenticated Users - Read, Apply group policy, Special permissions + +The special permissions for Authenticated Users are for Read-type Properties. + +CREATOR OWNER - Special permissions +SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions +Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions + +Document any other access permissions that allow the objects to be updated with the ISSO. + +The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on created Group Policy objects.This applies to domain controllers. It is NA for other systems. + +Review the permissions on Group Policy objects. + +Open "Group Policy Management" (available from various menus or run "gpmc.msc"). + +Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). + +For each Group Policy object: + +Select the Group Policy object item in the left pane. + +Select the "Delegation" tab in the right pane. + +Select the "Advanced" button. + +Select each Group or user name. + +View the permissions. + +If any standard user accounts or groups have "Allow" permissions greater than "Read" and "Apply group policy", this is a finding. + +Other access permissions that allow the objects to be updated are considered findings unless specifically documented by the ISSO. + +The default permissions noted below satisfy this requirement. + +The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next "Advanced" button, the desired Permission entry, and the "Edit" button. + +Authenticated Users - Read, Apply group policy, Special permissions + +The special permissions for Authenticated Users are for Read-type Properties. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +The special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties: + +CREATOR OWNER - Special permissions +SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions +Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions + +The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on organization created Group Policy objects.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000100Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions.<VulnDiscussion>When Active Directory objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. + +The Domain Controllers OU object requires special attention as the Domain Controllers are central to the configuration and management of the domain. Inappropriate access permissions defined for the Domain Controllers OU could allow an intruder or unauthorized personnel to make changes that could lead to the compromise of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93035SV-103123CCI-002235Limit the permissions on the Domain Controllers OU to restrict changes to System, Domain Admins, Enterprise Admins and Administrators. + +The default permissions listed below satisfy this requirement. + +Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions. + +CREATOR OWNER - Special permissions + +SELF - Special permissions + +Authenticated Users - Read, Special permissions + +The special permissions for Authenticated Users are Read types. + +SYSTEM - Full Control + +Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Enterprise Admins - Full Control + +Key Admins - Special permissions + +Enterprise Key Admins - Special permissions + +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Pre-Windows 2000 Compatible Access - Special permissions + +The special permissions for Pre-Windows 2000 Compatible Access are Read types. + +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissionsThis applies to domain controllers. It is NA for other systems. + +Review the permissions on the Domain Controllers OU. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Select "Advanced Features" in the "View" menu if not previously selected. + +Select the "Domain Controllers" OU (folder in folder icon). + +Right-click and select "Properties". + +Select the "Security" tab. + +If the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding. + +The default permissions listed below satisfy this requirement. + +Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions and are not a finding. + +The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "View" or "Edit" button. + +Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. + +CREATOR OWNER - Special permissions + +SELF - Special permissions + +Authenticated Users - Read, Special permissions + +The special permissions for Authenticated Users are Read types. + +If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +SYSTEM - Full Control + +Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Enterprise Admins - Full Control + +Key Admins - Special permissions + +Enterprise Key Admins - Special permissions + +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Pre-Windows 2000 Compatible Access - Special permissions + +The Special permissions for Pre-Windows 2000 Compatible Access are Read types. + +If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissionsSRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000110Windows Server 2019 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions.<VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. + +For Active Directory, the OU objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a denial of service (DoS) to authorized users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103125V-93037CCI-002235Maintain the Allow type permissions on domain-defined OUs to be at least as restrictive as the defaults below. + +Document any additional permissions above Read with the ISSO if an approved distributed administration model (help desk or other user support staff) is implemented. + +CREATOR OWNER - Special permissions + +Self - Special permissions + +Authenticated Users - Read, Special permissions + +The special permissions for Authenticated Users are Read type. + +SYSTEM - Full Control + +Domain Admins - Full Control + +Enterprise Admins - Full Control + +Key Admins - Special permissions + +Enterprise Key Admins - Special permissions + +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Pre-Windows 2000 Compatible Access - Special permissions + +The special permissions for Pre-Windows 2000 Compatible Access are for Read types. + +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissionsThis applies to domain controllers. It is NA for other systems. + +Review the permissions on domain-defined OUs. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +For each OU that is defined (folder in folder icon) excluding the Domain Controllers OU: + +Right-click the OU and select "Properties". + +Select the "Security" tab. + +If the Allow type permissions on the OU are not at least as restrictive as those below, this is a finding. + +The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "Edit" or "View" button. + +Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. + +CREATOR OWNER - Special permissions + +Self - Special permissions + +Authenticated Users - Read, Special permissions + +The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +SYSTEM - Full Control + +Domain Admins - Full Control + +Enterprise Admins - Full Control + +Key Admins - Special permissions + +Enterprise Key Admins - Special permissions + +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Pre-Windows 2000 Compatible Access - Special permissions + +The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions + +If an ISSO-approved distributed administration model (help desk or other user support staff) is implemented, permissions above Read may be allowed for groups documented by the ISSO. + +If any OU with improper permissions includes identification or authentication data (e.g., accounts, passwords, or password hash data) used by systems to determine access control, the severity is CAT I (e.g., OUs that include user accounts, including service/application accounts). + +If an OU with improper permissions does not include identification and authentication data used by systems to determine access control, the severity is CAT II (e.g., Workstation, Printer OUs).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000350Windows Server 2019 Add workstations to domain user right must only be assigned to the Administrators group on domain controllers.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +Accounts with the "Add workstations to domain" right may add computers to a domain. This could result in unapproved or incorrectly configured systems being added to a 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93039SV-103127CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Add workstations to domain" to include only the following accounts or groups: + +- AdministratorsThis applies to domain controllers. It is NA for other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Add workstations to domain" right, this is a finding. + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeMachineAccountPrivilege" user right, this is a finding. + +S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-DC-000420Windows Server 2019 Enable computer and user accounts to be trusted for delegation user right must only be assigned to the Administrators group on domain controllers.<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 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103129V-93041CCI-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 include only the following accounts or groups: + +- AdministratorsThis applies to domain controllers. A separate version applies to other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups other than the following are granted the "Enable computer and user accounts to be trusted for delegation" user right, this is a finding. + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeEnableDelegationPrivilege" user right, this is a finding. + +S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-MS-000010Windows Server 2019 must only allow administrators responsible for the member server or standalone system to 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 using only accounts with the minimum level of authority necessary. + +For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group (see V-36433 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. + +Standard user accounts must not be members of the built-in 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93043SV-103131CCI-002235Configure the local "Administrators" group to include only administrator groups or accounts responsible for administration of the system. + +For domain-joined member servers, replace the Domain Admins group with a domain member server administrator group. + +Remove any standard user accounts.This applies to member servers and standalone systems. A separate version applies to domain controllers. + +Open "Computer Management". + +Navigate to "Groups" under "Local Users and Groups". + +Review the local "Administrators" group. + +Only administrator groups or accounts responsible for administration of the system may be members of the group. + +For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group. + +Standard user accounts must not be members of the local Administrator group. + +If accounts that do not have responsibility for administration of the system are members of the local Administrators group, this is a finding. + +If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-MS-000060Windows Server 2019 must restrict remote calls to the Security Account Manager (SAM) to Administrators on domain-joined member servers and standalone systems.<VulnDiscussion>The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103133V-93045CCI-002235Navigate to the policy Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Restrict clients allowed to make remote calls to SAM". +Select "Edit Security" to configure the "Security descriptor:". + +Add "Administrators" in "Group or user names:" if it is not already listed (this is the default). + +Select "Administrators" in "Group or user names:". + +Select "Allow" for "Remote Access" in "Permissions for "Administrators". + +Click "OK". + +The "Security descriptor:" must be populated with "O:BAG:BAD:(A;;RC;;;BA) for the policy to be enforced.This applies to member servers and standalone systems; it is NA for domain controllers. + +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\Lsa\ + +Value Name: RestrictRemoteSAM + +Value Type: REG_SZ +Value: O:BAG:BAD:(A;;RC;;;BA)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-MS-000130Windows Server 2019 Enable computer and user accounts to be trusted for delegation user right must not be assigned to any groups or accounts on domain-joined member servers and standalone systems.<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 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103135V-93047CCI-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).This applies to member servers and standalone systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs are granted the "SeEnableDelegationPrivilege" user right, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000010Windows Server 2019 Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93049SV-103137CCI-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).Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs are granted the "SeTrustedCredManAccessPrivilege" user right, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000020Windows Server 2019 Act as part of the operating system user right must not be assigned to any groups or accounts.<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 the 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103139V-93051CCI-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).Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs are granted the "SeTcbPrivilege" user right, this is a finding. + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060). + +Passwords for accounts with this user right must be protected as highly privileged accounts.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000040Windows Server 2019 Back up files and directories user right must only be assigned to the Administrators group.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93053SV-103141CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Back up files and directories" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeBackupPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000050Windows Server 2019 Create a pagefile user right must only be assigned to the Administrators group.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103143V-93055CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create a pagefile" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeCreatePagefilePrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000060Windows Server 2019 Create a token object user right must not be assigned to any groups or accounts.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93057SV-103145CCI-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).Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups are granted the "Create a token object" user right, this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs are granted the "SeCreateTokenPrivilege" user right, this is a finding. + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060). + +Passwords for application accounts with this user right must be protected as highly privileged accounts.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000070Windows Server 2019 Create global objects user right must only be assigned to Administrators, Service, Local Service, and Network Service.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93059SV-103147CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create global objects" to include only the following accounts or groups: + +- Administrators +- Service +- Local Service +- Network ServiceVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 Service + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeCreateGlobalPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators) +S-1-5-6 (Service) +S-1-5-19 (Local Service) +S-1-5-20 (Network Service) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000080Windows Server 2019 Create permanent shared objects user right must not be assigned to any groups or accounts.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103149V-93061CCI-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).Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups are granted the "Create permanent shared objects" user right, this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs are granted the "SeCreatePermanentPrivilege" user right, this is a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000090Windows Server 2019 Create symbolic links user right must only be assigned to the Administrators group.<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 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103151V-93063CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create symbolic links" to include only the following accounts or groups: + +- Administrators + +Systems that have the Hyper-V role will also have "Virtual Machines" given this user right. If this needs to be added manually, enter it as "NT Virtual Machine\Virtual Machines".Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeCreateSymbolicLinkPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators) + +Systems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines", SID S-1-5-83-0). This is not a finding.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000100Windows Server 2019 Debug programs: user right must only be assigned to the Administrators group.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93065SV-103153CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Debug programs" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeDebugPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060). + +Passwords for application accounts with this user right must be protected as highly privileged accounts.SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000110Windows Server 2019 Force shutdown from a remote system user right must only be assigned to the Administrators group.<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 denial of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93067SV-103155CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Force shutdown from a remote system" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeRemoteShutdownPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000120Windows Server 2019 Generate security audits user right must only be assigned to Local Service and Network Service.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93069SV-103157CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Generate security audits" to include only the following accounts or groups: + +- Local Service +- Network ServiceVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 Service + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeAuditPrivilege" user right, this is a finding: + +S-1-5-19 (Local Service) +S-1-5-20 (Network Service) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000130Windows Server 2019 Impersonate a client after authentication user right must only be assigned to Administrators, Service, Local Service, and Network Service.<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 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103159V-93071CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Impersonate a client after authentication" to include only the following accounts or groups: + +- Administrators +- Service +- Local Service +- Network ServiceVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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 Service + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeImpersonatePrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators) +S-1-5-6 (Service) +S-1-5-19 (Local Service) +S-1-5-20 (Network Service) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000140Windows Server 2019 Increase scheduling priority: user right must only be assigned to the Administrators group.<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 denial of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103161V-93073CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Increase scheduling priority" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeIncreaseBasePriorityPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000150Windows Server 2019 Load and unload device drivers user right must only be assigned to the Administrators group.<VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Load and unload device drivers" user right allows a user to load device drivers dynamically on a system. This could be used by an attacker to install malicious code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103163V-93075CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Load and unload device drivers" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeLoadDriverPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000160Windows Server 2019 Lock pages in memory user right must not be assigned to any groups or accounts.<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 denial of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93077SV-103165CCI-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).Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If any accounts or groups are granted the "Lock pages in memory" user right, this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs are granted the "SeLockMemoryPrivilege" user right, this is a finding. + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000180Windows Server 2019 Modify firmware environment values user right must only be assigned to the Administrators group.<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 denial of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93079SV-103167CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Modify firmware environment values" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeSystemEnvironmentPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000190Windows Server 2019 Perform volume maintenance tasks user right must only be assigned to the Administrators group.<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. This could be used to delete volumes, resulting in data loss or a denial of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93081SV-103169CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Perform volume maintenance tasks" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeManageVolumePrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000200Windows Server 2019 Profile single process user right must only be assigned to the Administrators group.<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 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93083SV-103171CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Profile single process" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeProfileSingleProcessPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators)SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000210Windows Server 2019 Restore files and directories user right must only be assigned to the Administrators group.<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 overwrite more current 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93085SV-103173CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Restore files and directories" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeRestorePrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000324-GPOS-00125<GroupDescription></GroupDescription>WN19-UR-000220Windows Server 2019 Take ownership of files or other objects user right must only be assigned to the Administrators group.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93087SV-103175CCI-002235Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Take ownership of files or other objects" to include only the following accounts or groups: + +- AdministratorsVerify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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: + +- Administrators + +For server core installations, run the following command: + +Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt + +Review the text file. + +If any SIDs other than the following are granted the "SeTakeOwnershipPrivilege" user right, this is a finding: + +S-1-5-32-544 (Administrators) + +If an application requires this user right, this would not be a finding. + +Vendor documentation must support the requirement for having the user right. + +The requirement must be documented with the ISSO. + +The application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000090Windows Server 2019 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 Events records events such as the access of a password hash or the Password Policy Checking API being called. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93089SV-103177CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000140Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93091SV-103179CCI-002234CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000260Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103181V-93093CCI-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 "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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000270Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103183V-93095CCI-002234CCI-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 "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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000280Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93097SV-103185CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000290Windows Server 2019 must be configured to audit Policy Change - Authorization 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. + +Authorization Policy Change records events related to changes in user rights, such as "Create a token object". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93099SV-103187CCI-002234CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Policy Change >> "Audit Authorization 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Authorization Policy Change - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000300Windows Server 2019 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". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93101SV-103189CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000310Windows Server 2019 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". + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93103SV-103191CCI-002234CCI-000172Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000320Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93105SV-103193CCI-000172CCI-002234Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000330Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93107SV-103195CCI-002234CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000340Windows Server 2019 must be configured to audit System - Other System 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. + +Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103197V-93109CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Other System Events - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000350Windows Server 2019 must be configured to audit System - Other System 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. + +Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93111SV-103199CCI-002234CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> System >> "Audit Other System 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Other System Events - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000360Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103201V-93113CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000370Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93115SV-103203CCI-002234CCI-000172Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000380Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93117SV-103205CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-AU-000390Windows Server 2019 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. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93119SV-103207CCI-002234CCI-000172Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000170Windows Server 2019 Active Directory Group Policy objects must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93121SV-103209CCI-000172CCI-002234Configure the audit settings for Group Policy objects to include the following: + +This can be done at the Policy level in Active Directory to apply to all group policies. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Select "Advanced Features" from the "View" Menu. + +Navigate to [Domain] >> System >> Policies in the left panel. + +Right click "Policies", select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button. + +Select the "Auditing" tab. + +Type - Fail +Principal - Everyone +Access - Full Control +Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects + +The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. + +Type - Success +Principal - Everyone +Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) +Inherited from - Parent Object +Applies to - Descendant groupPolicyContainer objects + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) +Inherited from - Parent Object +Applies to - Descendant Organization Unit ObjectsThis applies to domain controllers. It is NA for other systems. + +Review the auditing configuration for all Group Policy objects. + +Open "Group Policy Management" (available from various menus or run "gpmc.msc"). + +Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). + +For each Group Policy object: + +Select the Group Policy object item in the left pane. + +Select the "Delegation" tab in the right pane. + +Select the "Advanced" button. + +Select the "Advanced" button again and then the "Auditing" tab. + +If the audit settings for any Group Policy object are not at least as inclusive as those below, this is a finding: + +Type - Fail +Principal - Everyone +Access - Full Control +Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects + +The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. + +Type - Success +Principal - Everyone +Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) +Inherited from - Parent Object +Applies to - Descendant groupPolicyContainer objects + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) +Inherited from - Parent Object +Applies to - Descendant Organization Unit ObjectsSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000180Windows Server 2019 Active Directory Domain object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103211V-93123CCI-002234CCI-000172Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select the domain being reviewed in the left pane. + +Right-click the domain name and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +Configure the audit settings for Domain object to include the following: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - None +Applies to - Special + +Type - Success +Principal - Domain Users +Access - All extended rights +Inherited from - None +Applies to - This object only + +Type - Success +Principal - Administrators +Access - All extended rights +Inherited from - None +Applies to - This object only + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner.)This applies to domain controllers. It is NA for other systems. + +Review the auditing configuration for the Domain object. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select the domain being reviewed in the left pane. + +Right-click the domain name and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +If the audit settings on the Domain object are not at least as inclusive as those below, this is a finding: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - None +Applies to - Special + +Type - Success +Principal - Domain Users +Access - All extended rights +Inherited from - None +Applies to - This object only + +Type - Success +Principal - Administrators +Access - All extended rights +Inherited from - None +Applies to - This object only + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner)SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000190Windows Server 2019 Active Directory Infrastructure object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103213V-93125CCI-000172CCI-002234Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select the domain being reviewed in the left pane. + +Right-click the "Infrastructure" object in the right pane and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +Configure the audit settings for Infrastructure object to include the following: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain)This applies to domain controllers. It is NA for other systems. + +Review the auditing configuration for Infrastructure object. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select the domain being reviewed in the left pane. + +Right-click the "Infrastructure" object in the right pane and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +If the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain)SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000200Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103215V-93127CCI-002234CCI-000172Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select the "Domain Controllers OU" under the domain being reviewed in the left pane. + +Right-click the "Domain Controllers OU" object and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +Configure the audit settings for Domain Controllers OU object to include the following: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: all create, delete and modify permissions) + +Type - Success +Principal - Everyone +Access - Write all properties +Inherited from - None +Applies to - This object and all descendant objects + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objectsThis applies to domain controllers. It is NA for other systems. + +Review the auditing configuration for the Domain Controller OU object. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select the "Domain Controllers OU" under the domain being reviewed in the left pane. + +Right-click the "Domain Controllers OU" object and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +If the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object and all descendant objects + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: all create, delete and modify permissions) + +Type - Success +Principal - Everyone +Access - Write all properties +Inherited from - None +Applies to - This object and all descendant objects + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objectsSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000210Windows Server 2019 Active Directory AdminSDHolder object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103217V-93129CCI-000172CCI-002234Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select "System" under the domain being reviewed in the left pane. + +Right-click the "AdminSDHolder" object in the right pane and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +Configure the audit settings for AdminSDHolder object to include the following: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Write all properties, Modify permissions, Modify owner) + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objectsThis applies to domain controllers. It is NA for other systems. + +Review the auditing configuration for the "AdminSDHolder" object. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select "System" under the domain being reviewed in the left pane. + +Right-click the "AdminSDHolder" object in the right pane and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +If the audit settings on the "AdminSDHolder" object are not at least as inclusive as those below, this is a finding: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Write all properties, Modify permissions, Modify owner) + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objectsSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000220Windows Server 2019 Active Directory RID Manager$ object must be configured with proper audit settings.<VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93131SV-103219CCI-002234CCI-000172Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select "System" under the domain being reviewed in the left pane. + +Right-click the "RID Manager$" object in the right pane and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +Configure the audit settings for RID Manager$ object to include the following: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None + (Access - Special = Write all properties, All extended rights, Change RID master) + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain)This applies to domain controllers. It is NA for other systems. + +Review the auditing configuration for the "RID Manager$" object. + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Ensure "Advanced Features" is selected in the "View" menu. + +Select "System" under the domain being reviewed in the left pane. + +Right-click the "RID Manager$" object in the right pane and select "Properties". + +Select the "Security" tab. + +Select the "Advanced" button and then the "Auditing" tab. + +If the audit settings on the "RID Manager$" object are not at least as inclusive as those below, this is a finding: + +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None + +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. + +Type - Success +Principal - Everyone +Access - Special +Inherited from - None + (Access - Special = Write all properties, All extended rights, Change RID master) + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain)SRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000240Windows Server 2019 must be configured to audit DS Access - Directory Service Access 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 Directory Service Access records events related to users accessing an Active Directory object. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103221V-93133CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Access" with "Success" selected.This applies to domain controllers. It is NA for other systems. + +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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. + +DS Access >> Directory Service Access - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000250Windows Server 2019 must be configured to audit DS Access - Directory Service Access 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 Directory Service Access records events related to users accessing an Active Directory object. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103223V-93135CCI-002234CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Access" with "Failure" selected.This applies to domain controllers. It is NA for other systems. + +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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. + +DS Access >> Directory Service Access - FailureSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000260Windows Server 2019 must be configured to audit DS Access - Directory Service Changes 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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93137SV-103225CCI-000172CCI-002234Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Changes" with "Success" selected.This applies to domain controllers. It is NA for other systems. + +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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. + +DS Access >> Directory Service Changes - SuccessSRG-OS-000327-GPOS-00127<GroupDescription></GroupDescription>WN19-DC-000270Windows Server 2019 must be configured to audit DS Access - Directory Service Changes 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 Directory Service Changes records events related to changes made to objects in Active Directory Domain Services. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93139SV-103227CCI-002234CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> DS Access >> "Directory Service Changes" with "Failure" selected.This applies to domain controllers. It is NA for other systems. + +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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. + +DS Access >> Directory Service Changes - FailureSRG-OS-000329-GPOS-00128<GroupDescription></GroupDescription>WN19-AC-000010Windows Server 2019 account lockout duration must be configured to 15 minutes or greater.<VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93145SV-103233CCI-002238Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> "Account lockout duration" to "15" minutes or greater. + +A value of "0" is also acceptable, requiring an administrator to unlock the account.Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. + +If the "Account lockout duration" is less than "15" minutes (excluding "0"), this is a finding. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "LockoutDuration" is less than "15" (excluding "0") in the file, this is a finding. + +Configuring this to "0", requiring an administrator to unlock the account, is more restrictive and is not a finding.SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>WN19-CC-000270Windows Server 2019 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103265V-93177CCI-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 write events directly to an audit server, 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\Windows\EventLog\Application\ + +Value Name: MaxSize + +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater)SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>WN19-CC-000280Windows Server 2019 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103267V-93179CCI-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 write events directly to an audit server, 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\Windows\EventLog\Security\ + +Value Name: MaxSize + +Type: REG_DWORD +Value: 0x00030000 (196608) (or greater)SRG-OS-000341-GPOS-00132<GroupDescription></GroupDescription>WN19-CC-000290Windows Server 2019 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103269V-93181CCI-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 write events directly to an audit server, 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\Windows\EventLog\System\ + +Value Name: MaxSize + +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater)SRG-OS-000342-GPOS-00133<GroupDescription></GroupDescription>WN19-AU-000010Windows Server 2019 audit records must be backed up to a different system or media than the system being audited.<VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93183SV-103271CCI-001851Establish and implement a process for backing up log data to another system or media other than the system being audited.Determine if a process to back up log data to a different system or media than the system being audited has been implemented. + +If it has not, this is a finding.SRG-OS-000355-GPOS-00143<GroupDescription></GroupDescription>WN19-00-000440The Windows Server 2019 time service must synchronize with an appropriate DoD time source.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93187SV-103275CCI-001891Configure the system to synchronize time with an appropriate DoD time source. + +Domain-joined systems use NT5DS to synchronize time from other systems in the domain by default. + +If 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 appropriate DoD time server. + +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.Review the Windows time service configuration. + +Open an elevated "Command Prompt" (run as administrator). + +Enter "W32tm /query /configuration". + +Domain-joined systems (excluding the domain controller with the PDC emulator role): + +If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. + +Other systems: + +If systems are configured with a "Type" of "NTP", including standalone systems and the domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. + +To determine the domain controller with the PDC Emulator role: + +Open "PowerShell". + +Enter "Get-ADDomain | FT PDCEmulator".SRG-OS-000362-GPOS-00149<GroupDescription></GroupDescription>WN19-CC-000420Windows Server 2019 must prevent users 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93199SV-103287CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ + +Value Name: EnableUserControl + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000362-GPOS-00149<GroupDescription></GroupDescription>WN19-CC-000430Windows Server 2019 must disable the Windows Installer Always install with elevated privileges option.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93201SV-103289CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ + +Value Name: AlwaysInstallElevated + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000363-GPOS-00150<GroupDescription></GroupDescription>WN19-00-000220Windows Server 2019 system files must be monitored for unauthorized changes.<VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93203SV-103291CCI-001744Monitor the system for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools.Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. + +If system files are not monitored for unauthorized changes, this is a finding. + +A properly configured and approved DoD HBSS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>WN19-CC-000210Windows Server 2019 Autoplay 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 media is inserted into 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93373SV-103459CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ + +Value Name: NoAutoplayfornonVolume + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>WN19-CC-000220Windows Server 2019 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93375SV-103461CCI-001764Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Set the default behavior for AutoRun" to "Enabled" with "Do not execute any autorun commands" 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\Microsoft\Windows\CurrentVersion\Policies\Explorer\ + +Value Name: NoAutorun + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000368-GPOS-00154<GroupDescription></GroupDescription>WN19-CC-000230Windows Server 2019 AutoPlay 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 media is inserted into 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. Enabling this policy disables 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93377SV-103463CCI-001764Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> "Turn off AutoPlay" to "Enabled" with "All Drives" 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\Microsoft\Windows\CurrentVersion\policies\Explorer\ + +Value Name: NoDriveTypeAutoRun + +Type: REG_DWORD +Value: 0x000000ff (255)SRG-OS-000370-GPOS-00155<GroupDescription></GroupDescription>WN19-00-000080Windows Server 2019 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.<VulnDiscussion>Using a whitelist provides a configuration management method to allow 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93379SV-103465CCI-001774Configure 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 Server. + +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" at the following link: + +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfmThis 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. + +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 Server. 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 imported previously, 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" at the following link: + +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfmSRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-CC-000340Windows Server 2019 must not save passwords 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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93425SV-103511CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: DisablePasswordSaving + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-CC-000360Windows Server 2019 Remote 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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93427SV-103513CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ + +Value Name: fPromptForPassword + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-CC-000520Windows Server 2019 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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103515V-93429CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ + +Value Name: DisableRunAs + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-SO-000380Windows Server 2019 User 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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103517V-93431CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: FilterAdministratorToken + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-SO-000410Windows Server 2019 User Account Control must automatically deny standard user requests for elevation.<VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93433SV-103519CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: ConsentPromptBehaviorUser + +Value Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000373-GPOS-00157<GroupDescription></GroupDescription>WN19-SO-000440Windows Server 2019 User 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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93435SV-103521CCI-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".UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: EnableLUA + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000379-GPOS-00164<GroupDescription></GroupDescription>WN19-MS-000040Windows Server 2019 must restrict unauthenticated Remote Procedure Call (RPC) clients from connecting to the RPC server on domain-joined member servers and standalone systems.<VulnDiscussion>Unauthenticated RPC clients may allow anonymous access to sensitive information. 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93453SV-103539CCI-001967Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Remote Procedure Call >> "Restrict Unauthenticated RPC clients" to "Enabled" with "Authenticated" selected.This applies to member servers and standalone systems, it is NA for domain controllers. + +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\Rpc\ + +Value Name: RestrictRemoteClients + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000379-GPOS-00164<GroupDescription></GroupDescription>WN19-SO-000090Windows Server 2019 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 the 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93455SV-103541CCI-001967Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain member: Disable machine account password changes" 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: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ + +Value Name: DisablePasswordChange + +Value Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000393-GPOS-00173<GroupDescription></GroupDescription>WN19-CC-000480Windows Server 2019 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. + +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103585V-93499CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ + +Value Name: AllowUnencryptedTraffic + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000393-GPOS-00173<GroupDescription></GroupDescription>WN19-CC-000510Windows Server 2019 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. + +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103587V-93501CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ + +Value Name: AllowUnencryptedTraffic + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000396-GPOS-00176<GroupDescription></GroupDescription>WN19-DC-000140Windows Server 2019 must use separate, NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level when replication data traverses a network cleared to a lower level than the data.<VulnDiscussion>Directory data that is not appropriately encrypted is subject to compromise. Commercial-grade encryption does not provide adequate protection when the classification level of directory data in transit is higher than the level of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93513SV-103599CCI-002450Configure NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level that transfer replication data through a network cleared to a lower level than the data.This applies to domain controllers. It is NA for other systems. + +Review the organization network diagram(s) or documentation to determine the level of classification for the network(s) over which replication data is transmitted. + +Determine the classification level of the Windows domain controller. + +If the classification level of the Windows domain controller is higher than the level of the networks, review the organization network diagram(s) and directory implementation documentation to determine if NSA-approved encryption is used to protect the replication network traffic. + +If the classification level of the Windows domain controller is higher than the level of the network traversed and NSA-approved encryption is not used, this is a finding.SRG-OS-000420-GPOS-00186<GroupDescription></GroupDescription>WN19-CC-000060Windows Server 2019 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 server's 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103627V-93541CCI-002385Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers" to "Enabled". + +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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\Services\Netbt\Parameters\ + +Value Name: NoNameReleaseOnDemand + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-DC-000320Windows Server 2019 domain controllers must require LDAP access signing.<VulnDiscussion>Unsigned network traffic is susceptible to man-in-the-middle attacks, where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. The risk of an attacker pulling this off can be decreased by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPsec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man-in-the-middle attacks extremely difficult. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93545SV-103631CCI-002418CCI-002421Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain controller: LDAP server signing requirements" to "Require signing".This applies to domain controllers. It is NA for other systems. + +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\Services\NTDS\Parameters\ + +Value Name: LDAPServerIntegrity + +Value Type: REG_DWORD +Value: 0x00000002 (2)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000060Windows Server 2019 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled.<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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93547SV-103633CCI-002421CCI-002418Configure 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".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\Services\Netlogon\Parameters\ + +Value Name: RequireSignOrSeal + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000070Windows Server 2019 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to enabled.<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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93549SV-103635CCI-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".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\Services\Netlogon\Parameters\ + +Value Name: SealSecureChannel + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000080Windows Server 2019 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled.<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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93551SV-103637CCI-002421CCI-002418Configure 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".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\Services\Netlogon\Parameters\ + +Value Name: SignSecureChannel + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000110Windows Server 2019 must be configured to require a strong session key.<VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103639V-93553CCI-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".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\Services\Netlogon\Parameters\ + +Value Name: RequireStrongKey + +Value Type: REG_DWORD +Value: 0x00000001 (1) + +This setting may prevent a system from being joined to a domain if not configured consistently between systems.SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000160Windows Server 2019 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled.<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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93555SV-103641CCI-002421CCI-002418Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network client: Digitally sign communications (always)" 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: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ + +Value Name: RequireSecuritySignature + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000170Windows Server 2019 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled.<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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93557SV-103643CCI-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".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\Services\LanmanWorkstation\Parameters\ + +Value Name: EnableSecuritySignature + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000190Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.<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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103645V-93559CCI-002421CCI-002418Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Microsoft network server: Digitally sign communications (always)" 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: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ + +Value Name: RequireSecuritySignature + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000423-GPOS-00187<GroupDescription></GroupDescription>WN19-SO-000200Windows Server 2019 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled.<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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93561SV-103647CCI-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".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\Services\LanManServer\Parameters\ + +Value Name: EnableSecuritySignature + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000425-GPOS-00189<GroupDescription></GroupDescription>WN19-00-000260Windows Server 2019 must implement protection methods such as TLS, encrypted VPNs, or IPsec if the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process.<VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. + +Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. + +Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. + +Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93543SV-103629CCI-002422CCI-002420Configure protection methods such as TLS, encrypted VPNs, or IPsec when the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process.If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. + +If protection methods have not been implemented, this is a finding.SRG-OS-000433-GPOS-00192<GroupDescription></GroupDescription>WN19-CC-000310Windows Server 2019 Explorer Data Execution Prevention must be enabled.<VulnDiscussion>Data Execution Prevention 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103649V-93563CCI-002824The default behavior is for data execution prevention to be turned on for File Explorer. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off Data Execution Prevention for Explorer" to "Not Configured" or "Disabled".The default behavior is for Data Execution Prevention to be turned on for File Explorer. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ + +Value Name: NoDataExecutionPrevention + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000433-GPOS-00193<GroupDescription></GroupDescription>WN19-EP-000020Windows Server 2019 Exploit Protection system-level mitigation, Randomize memory allocations (Bottom-Up ASLR), must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93565SV-103651CCI-002824Ensure Exploit Protection system-level mitigation, "Randomize memory allocations (Bottom-Up ASLR)" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. + +Open "Windows Defender Security Center". + +Select "App & browser control". + +Select "Exploit protection settings". + +Under "System settings", configure "Randomize memory allocations (Bottom-Up ASLR)" to "On by default" or "Use default (<On>)". + +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Bottom-Up ASLR on (other system level EP requirements can be combined under <SystemConfig>): + +<SystemConfig> + <ASLR BottomUp="true" HighEntropy="true"></ASLR> +</SystemConfig> + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. + +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -System". + +If the status of "ASLR: BottomUp" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration)SRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000070Windows Server 2019 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103241V-93153CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000080Windows Server 2019 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103243V-93155CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - FailureSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000170Windows Server 2019 must be configured to audit Logon/Logoff - Group Membership 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 Group Membership records information related to the group membership of a user's logon token.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93159SV-103247CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Group Membership" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Group Membership - SuccessSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000210Windows Server 2019 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 that have administrative privileges and can be used to elevate processes. + +Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93161SV-103249CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000220Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. + +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103251V-93163CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Other Object Access Events - SuccessSRG-OS-000470-GPOS-00214<GroupDescription></GroupDescription>WN19-AU-000230Windows Server 2019 must be configured to audit Object Access - Other Object Access 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. + +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103253V-93165CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Other Object Access 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Other Object Access Events - FailureSRG-OS-000472-GPOS-00217<GroupDescription></GroupDescription>WN19-AU-000180Windows Server 2019 must be configured to audit 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. + +Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93171SV-103259CCI-000172CCI-000366Configure 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - SuccessSRG-OS-000474-GPOS-00219<GroupDescription></GroupDescription>WN19-AU-000130Windows Server 2019 must be configured to audit Detailed Tracking - Plug and Play 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. + +Plug and Play activity records events related to the successful connection of external devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93157SV-103245CCI-000172Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> "Audit PNP Activity" 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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 >> Plug and Play Events - SuccessSRG-OS-000474-GPOS-00219<GroupDescription></GroupDescription>WN19-AU-000240Windows Server 2019 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. + +Removable Storage auditing under Object Access 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103255V-93167CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - Success + +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding.SRG-OS-000474-GPOS-00219<GroupDescription></GroupDescription>WN19-AU-000250Windows Server 2019 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. + +Removable Storage auditing under Object Access 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103257V-93169CCI-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" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + +Use the "AuditPol" tool to review the current Audit Policy configuration: + +Open "PowerShell" or 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 - Failure + +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding.SRG-OS-000478-GPOS-00223<GroupDescription></GroupDescription>WN19-SO-000360Windows Server 2019 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.<VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103597V-93511CCI-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".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\Lsa\FIPSAlgorithmPolicy\ + +Value Name: Enabled + +Value Type: REG_DWORD +Value: 0x00000001 (1) + +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; otherwise. the browser will not be able to connect to a secure site.SRG-OS-000479-GPOS-00224<GroupDescription></GroupDescription>WN19-AU-000020Windows Server 2019 must, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly.<VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103273V-93185CCI-001851Configure the system to, at a minimum, off-load audit records of interconnected systems in real time and off-load standalone systems weekly.Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. + +If they are not, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000010Windows Server 2019 users with Administrative privileges 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93369SV-103457CCI-000366Ensure each user with administrative privileges 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. + +If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000030Windows Server 2019 administrative accounts must 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 account. + +Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to 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. + +Whitelisting can be used to enforce the policy to ensure compliance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93205SV-103293CCI-000366Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. Ensure the policy is enforced. + +The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. + +If it does not, this is a finding. + +The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000040Windows Server 2019 members 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93207SV-103295CCI-000366Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions.If no accounts are members of the Backup Operators group, this is NA. + +Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. + +If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000060Windows Server 2019 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization.<VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103297V-93209CCI-000366Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization. + +It is recommended that system-managed service accounts be used whenever possible.Determine if manually managed application/service accounts exist. If none exist, this is NA. + +If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. + +Identify manually managed application/service accounts. + +To determine the date a password was last changed: + +Domain controllers: + +Open "PowerShell". + +Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. + +If the "PasswordLastSet" date is more than one year old, this is a finding. + + +Member servers and standalone systems: + +Open "Command Prompt". + +Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. + +If the "Password Last Set" date is more than one year old, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000090Windows Server 2019 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use.<VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93213SV-103301CCI-000366Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.) + +The TPM must be enabled in the firmware. + +Run "tpm.msc" for configuration options in Windows.For standalone systems, this is NA. + +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. + +Verify the system has a TPM and it is ready for use. + +Run "tpm.msc". + +Review the sections in the center pane. + +"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". + +TPM Manufacturer Information - Specific Version = 2.0 or 1.2 + +If a TPM is not found or is not ready for use, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000100Windows Server 2019 must be maintained at a supported servicing level.<VulnDiscussion>Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103303V-93215CCI-000366Update the system to a Version 1809 (Build 17763.xxx) or greater.Open "Command Prompt". + +Enter "winver.exe". + +If the "About Windows" dialog box does not display "Microsoft Windows Server Version 1809 (Build 17763.xxx)" or greater, this is a finding. + +Preview versions must not be used in a production environment.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000110Windows Server 2019 must use an anti-virus program.<VulnDiscussion>Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103305V-93217CCI-000366If no anti-virus software is in use, install Windows Defender or third-party anti-virus. + +Open "PowerShell". + +Enter "Install-WindowsFeature -Name Windows-Defender”. + +For third-party anti-virus, install per anti-virus instructions and disable Windows Defender. + +Open "PowerShell". + +Enter "Uninstall-WindowsFeature -Name Windows-Defender”. +Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution. + +If there is no anti-virus solution installed on the system, this is a finding. + +Verify if Windows Defender is in use or enabled: + +Open "PowerShell". + +Enter “get-service | where {$_.DisplayName -Like "*Defender*"} | Select Status,DisplayName” + +Verify if third-party anti-virus is in use or enabled: + +Open "PowerShell". + +Enter "get-service | where {$_.DisplayName -Like "*mcafee*"} | Select Status,DisplayName” + +Enter "get-service | where {$_.DisplayName -Like "*symantec*"} | Select Status,DisplayName” +SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000120Windows Server 2019 must have a host-based intrusion detection or prevention system.<VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103307V-93219CCI-000366Install a HIDS or HIPS on each server.Determine whether there is a HIDS or HIPS on each server. + +If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. + +A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. + +If a HIDS is not installed on the system, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000240Windows Server 2019 must have software certificate installation files removed.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93221SV-103309CCI-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 or Adobe PreFlight certificate files.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 or Adobe PreFlight certificate files. 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.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000420Windows Server 2019 FTP servers must be configured to prevent anonymous logons.<VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. + +Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93223SV-103311CCI-000366Configure the FTP service to prevent anonymous logons. + +Open "Internet Information Services (IIS) Manager". + +Select the server. + +Double-click "FTP Authentication". + +Select "Anonymous Authentication". + +Select "Disabled" under "Actions".If FTP is not installed on the system, this is NA. + +Open "Internet Information Services (IIS) Manager". + +Select the server. + +Double-click "FTP Authentication". + +If the "Anonymous Authentication" status is "Enabled", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000430Windows Server 2019 FTP servers must be configured to prevent access to the system drive.<VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93225SV-103313CCI-000366Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system.If FTP is not installed on the system, this is NA. + +Open "Internet Information Services (IIS) Manager". + +Select "Sites" under the server name. + +For any sites with a Binding that lists FTP, right-click the site and select "Explore". + +If the site is not defined to a specific folder for shared FTP resources, this is a finding. + +If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000450Windows Server 2019 must have orphaned security identifiers (SIDs) removed from user rights.<VulnDiscussion>Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be established for some reason.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93227SV-103315CCI-000366Remove any unresolved SIDs found in User Rights assignments and determined to not be for currently valid accounts or groups by removing the accounts or groups from the appropriate group policy.Review the effective User Rights setting in Local Group Policy Editor. +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +Review each User Right listed for any unresolved SIDs to determine whether they are valid, such as due to being temporarily disconnected from the domain. (Unresolved SIDs have the format that begins with "*S-1-".) + +If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding. + +For server core installations, run the following command: + +Secedit /export /areas USER_RIGHTS /cfg c:\path\UserRights.txt + +The results in the file identify user right assignments by SID instead of group name. Review the SIDs for unidentified ones. A list of typical SIDs \ Groups is below, search Microsoft for articles on well-known SIDs for others. + +If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding. + +SID - Group +S-1-5-11 - Authenticated Users +S-1-5-113 - Local account +S-1-5-114 - Local account and member of Administrators group +S-1-5-19 - Local Service +S-1-5-20 - Network Service +S-1-5-32-544 - Administrators +S-1-5-32-546 - Guests +S-1-5-6 - Service +S-1-5-9 - Enterprise Domain Controllers +S-1-5-domain-512 - Domain Admins +S-1-5-root domain-519 - Enterprise Admins +S-1-5-80-3139157870-2983391045-3678747466-658725712-1809340420 - NT Service\WdiServiceHostSRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000460Windows Server 2019 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS.<VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93229SV-103317CCI-000366Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode.Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must run in "UEFI" mode. + +Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". + +Run "System Information". + +Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000470Windows Server 2019 must have Secure Boot enabled.<VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103319V-93231CCI-000366Enable Secure Boot in the system firmware.Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must have Secure Boot enabled. + +Run "System Information". + +Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. + +On server core installations, run the following PowerShell command: + +Confirm-SecureBootUEFI + +If a value of "True" is not returned, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000030Windows Server 2019 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103321V-93233CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. + +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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\Services\Tcpip6\Parameters\ + +Value Name: DisableIPSourceRouting + +Type: REG_DWORD +Value: 0x00000002 (2)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000040Windows Server 2019 source routing must be configured to the highest protection level to prevent Internet Protocol (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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103323V-93235CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing)" to "Enabled" with "Highest protection, source routing is completely disabled" selected. + +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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\Services\Tcpip\Parameters\ + +Value Name: DisableIPSourceRouting + +Value Type: REG_DWORD +Value: 0x00000002 (2)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000050Windows Server 2019 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 the 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103325V-93237CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> "MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes" to "Disabled". + +This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.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\Services\Tcpip\Parameters\ + +Value Name: EnableICMPRedirect + +Value Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000070Windows Server 2019 insecure logons to an SMB server must be disabled.<VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103327V-93239CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Lanman Workstation >> "Enable insecure guest logons" 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\LanmanWorkstation\ + +Value Name: AllowInsecureGuestAuth + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000080Windows Server 2019 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares.<VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103329V-93241CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Network Provider >> "Hardened UNC Paths" to "Enabled" with at least the following configured in "Hardened UNC Paths" (click the "Show" button to display): + +Value Name: \\*\SYSVOL +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Value Name: \\*\NETLOGON +Value: RequireMutualAuthentication=1, RequireIntegrity=1This requirement is applicable to domain-joined systems. For standalone systems, 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\Windows\NetworkProvider\HardenedPaths\ + +Value Name: \\*\NETLOGON +Value Type: REG_SZ +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Value Name: \\*\SYSVOL +Value Type: REG_SZ +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + +Additional entries would not be a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000100Windows Server 2019 must be configured to enable Remote host allows delegation of non-exportable credentials.<VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93243SV-103331CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> "Remote host allows delegation of non-exportable 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 +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ + +Value Name: AllowProtectedCreds + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000110Windows Server 2019 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection.<VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93245SV-103333CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Secure Boot" or "Secure Boot and DMA Protection" selected. + +A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: + +https://technet.microsoft.com/itpro/windows/keep-secure/credential-guardFor standalone systems, this is NA. + +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. + +Open "PowerShell" with elevated privileges (run as administrator). + +Enter the following: + +"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" + +If "RequiredSecurityProperties" does not include a value of "2" indicating "Secure Boot" (e.g., "{1, 2}"), this is a finding. + +If "Secure Boot and DMA Protection" is configured, "3" will also be displayed in the results (e.g., "{1, 2, 3}"). + +If "VirtualizationBasedSecurityStatus" is not a value of "2" indicating "Running", this is a finding. + +Alternately: + +Run "System Information". + +Under "System Summary", verify the following: + +If "Device Guard Virtualization based security" does not display "Running", this is a finding. + +If "Device Guard Required Security Properties" does not display "Base Virtualization Support, Secure Boot", this is a finding. + +If "Secure Boot and DMA Protection" is configured, "DMA Protection" will also be displayed (e.g., "Base Virtualization Support, Secure Boot, DMA Protection"). + +The policy settings referenced in the Fix section will configure the following registry values. However, due to hardware requirements, the registry values alone do not ensure proper function. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ + +Value Name: EnableVirtualizationBasedSecurity +Value Type: REG_DWORD +Value: 0x00000001 (1) + +Value Name: RequirePlatformSecurityFeatures +Value Type: REG_DWORD +Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) + +A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link: + +https://technet.microsoft.com/itpro/windows/keep-secure/credential-guardSRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000130Windows Server 2019 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad.<VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93249SV-103337CCI-000366The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). + +If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> "Boot-Start Driver Initialization Policy" to "Not Configured" or "Enabled" with any option other than "All" selected.The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000007 (7)", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ + +Value Name: DriverLoadPolicy + +Value Type: REG_DWORD +Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) + +Possible values for this setting are: +8 - Good only +1 - Good and unknown +3 - Good, unknown and bad but critical +7 - All (which includes "bad" and would be a finding)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000140Windows Server 2019 group policy objects must be reprocessed even if they have not changed.<VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93251SV-103339CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Group Policy >> "Configure registry policy processing" to "Enabled" with the option "Process even if the Group Policy objects have not changed" 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\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ + +Value Name: NoGPOListChanges + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000180Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (on battery).<VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93253SV-103341CCI-000366Configure 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 +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ + +Value Name: DCSettingIndex + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000190Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (plugged in).<VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93255SV-103343CCI-000366Configure 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 +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ + +Value Name: ACSettingIndex + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000250Windows Server 2019 Telemetry must be configured to Security or Basic.<VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103345V-93257CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Data Collection and Preview Builds>> "Allow Telemetry" to "Enabled" with "0 - Security [Enterprise Only]" or "1 - Basic" selected in "Options".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\DataCollection\ + +Value Name: AllowTelemetry + +Type: REG_DWORD +Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000260Windows Server 2019 Windows Update must not obtain updates from other PCs on the Internet.<VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103347V-93259CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Delivery Optimization >> "Download Mode" to "Enabled" with any option except "Internet" selected. + +Acceptable selections include: + +Bypass (100) +Group (2) +HTTP only (0) +LAN (1) +Simple (99)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\DeliveryOptimization\ + +Value Name: DODownloadMode + +Value Type: REG_DWORD +Value: 0x00000000 (0) - No peering (HTTP Only) +0x00000001 (1) - Peers on same NAT only (LAN) +0x00000002 (2) - Local Network / Private group peering (Group) +0x00000063 (99) - Simple download mode, no peering (Simple) +0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) + +A value of 0x00000003 (3), Internet, is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000320Windows Server 2019 Turning 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93261SV-103349CCI-000366The default behavior is for File Explorer heap termination on corruption to be disabled. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off heap termination on corruption" to "Not Configured" or "Disabled".The default behavior is for File Explorer heap termination on corruption to be enabled. + +If the registry Value Name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ + +Value Name: NoHeapTerminationOnCorruption + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000330Windows Server 2019 File Explorer shell protocol must run in protected mode.<VulnDiscussion>The shell protocol will limit the set of folders that 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93263SV-103351CCI-000366The default behavior is for shell protected mode to be turned on for File Explorer. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> File Explorer >> "Turn off shell protocol protected mode" to "Not Configured" or "Disabled".The default behavior is for shell protected mode to be turned on for File Explorer. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ + +Value Name: PreXPSP2ShellProtocolBehavior + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000390Windows Server 2019 must prevent attachments 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93265SV-103353CCI-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 +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ + +Value Name: DisableEnclosureDownload + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-CC-000440Windows Server 2019 users must be notified if a web-based program attempts to install software.<VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103355V-93267CCI-000366The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. + +If this needs to be corrected, configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> "Prevent Internet Explorer security prompt for Windows Installer scripts" to "Not Configured" or "Disabled".The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ + +Value Name: SafeForScripting + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-DC-000150Windows Server 2019 directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access.<VulnDiscussion>To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103359V-93271CCI-000366Configure directory data (outside the root DSE) of a non-public directory to prevent anonymous access. + +For AD, there are multiple configuration items that could enable anonymous access. + +Changing the access permissions on the domain naming context object (from the secure defaults) could enable anonymous access. If the check procedures indicate this is the cause, the process that was used to change the permissions should be reversed. This could have been through the Windows Support Tools ADSI Edit console (adsiedit.msc). + +The dsHeuristics option is used. This is addressed in check V-8555 in the AD Forest STIG.This applies to domain controllers. It is NA for other systems. + +Open "Command Prompt" (not elevated). + +Run "ldp.exe". + +From the "Connection menu", select "Bind". + +Clear the User, Password, and Domain fields. + +Select "Simple bind" for the Bind type and click "OK". + +Confirmation of anonymous access will be displayed at the end: + +res = ldap_simple_bind_s +Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON' + +From the "Browse" menu, select "Search". + +In the Search dialog, enter the DN of the domain naming context (generally something like "dc=disaost,dc=mil") in the Base DN field. + +Clear the Attributes field and select "Run". + +Error messages should display related to Bind and user not authenticated. + +If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding. + +The following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access. + +Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. + +Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-DC-000330Windows Server 2019 domain controllers must be configured to allow reset of machine account passwords.<VulnDiscussion>Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93273SV-103361CCI-000366Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Domain controller: Refuse machine account password changes" to "Disabled".This applies to domain controllers. It is NA for other systems. + +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\Services\Netlogon\Parameters\ + +Value Name: RefusePasswordChange + +Value Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-DC-000430The password for the krbtgt account on a domain must be reset at least every 180 days.<VulnDiscussion>The krbtgt account acts as a service account for the Kerberos Key Distribution Center (KDC) service. The account and password are created when a domain is created and the password is typically not changed. If the krbtgt account is compromised, attackers can create valid Kerberos Ticket Granting Tickets (TGT). + +The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and the amount of time equal to or greater than the maximum Kerberos ticket lifetime, and changing again reduces the risk of 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93211SV-103299CCI-000366Reset the password for the krbtgt account a least every 180 days. The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and changing again reduces the risk of issues. Changing twice in rapid succession forces clients to re-authenticate (including application services) but is desired if a compromise is suspected. + +PowerShell scripts are available to accomplish this such as at the following link: + +https://gallery.technet.microsoft.com/Reset-the-krbtgt-account-581a9e51 + +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). + +Select "Advanced Features" in the "View" menu if not previously selected. + +Select the "Users" node. + +Right click on the krbtgt account and select "Reset password" + +Enter a password that meets password complexity requirements. + +Clear the "User must change password at next logon" check box. + +The system will automatically change this to a system-generated complex password.This requirement is applicable to domain controllers; it is NA for other systems. + +Open "Windows PowerShell". + +Enter "Get-ADUser krbtgt -Property PasswordLastSet". + +If the "PasswordLastSet" date is more than 180 days old, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000010Windows Server 2019 Exploit Protection system-level mitigation, Data Execution Prevention (DEP), must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Data Execution Prevention (DEP)", are enabled by default at the system level. DEP prevents code from being run from data-only memory pages. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93313SV-103401CCI-000366Ensure Exploit Protection system-level mitigation, "Data Execution Prevention (DEP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. + +Open "Windows Defender Security Center". + +Select "App & browser control". + +Select "Exploit protection settings". + +Under "System settings", configure "Data Execution Prevention (DEP)" to "On by default" or "Use default (<On>)". + +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn DEP on (other system level EP requirements can be combined under <SystemConfig>): + +<SystemConfig> + <DEP Enable="true"></DEP> +</SystemConfig> + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. + +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -System". + +If the status of "DEP: Enable" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000030Windows Server 2019 Exploit Protection system-level mitigation, Control flow guard (CFG), must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Control flow guard (CFG)", are enabled by default at the system level. CFG ensures flow integrity for indirect calls. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93315SV-103403CCI-000366Ensure Exploit Protection system-level mitigation, "Control flow guard (CFG)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. + +Open "Windows Defender Security Center". + +Select "App & browser control". + +Select "Exploit protection settings". + +Under "System settings", configure "Control flow guard (CFG)" to "On by default" or "Use default (<On>)". + +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn CFG on (other system level EP requirements can be combined under <SystemConfig>): + +<SystemConfig> + <ControlFlowGuard Enable="true"></ControlFlowGuard> +</SystemConfig> + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. + +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -System". + +If the status of "CFG: Enable" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000040Windows Server 2019 Exploit Protection system-level mitigation, Validate exception chains (SEHOP), must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate exception chains (SEHOP)", are enabled by default at the system level. SEHOP (structured exception handling overwrite protection) ensures the integrity of an exception chain during exception dispatch. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103405V-93317CCI-000366Ensure Exploit Protection system-level mitigation, "Validate exception chains (SEHOP)", is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. + +Open "Windows Defender Security Center". + +Select "App & browser control". + +Select "Exploit protection settings". + +Under "System settings", configure "Validate exception chains (SEHOP)" to "On by default" or "Use default (<On>)". + +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn SEHOP on (other system level EP requirements can be combined under <SystemConfig>): + +<SystemConfig> + <SEHOP Enable="true"></SEHOP> +</SystemConfig> + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. + +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -System". + +If the status of "SEHOP: Enable" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000050Windows Server 2019 Exploit Protection system-level mitigation, Validate heap integrity, must be on.<VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate heap integrity", are enabled by default at the system level. "Validate heap integrity" terminates a process when heap corruption is detected. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103407V-93319CCI-000366Ensure Exploit Protection system-level mitigation, "Validate heap integrity" is turned on. The default configuration in Exploit Protection is "On by default" which meets this requirement. + +Open "Windows Defender Security Center". + +Select "App & browser control". + +Select "Exploit protection settings". + +Under "System settings", configure "Validate heap integrity" to "On by default" or "Use default (<On>)". + +The STIG package includes a DoD EP XML file in the "Supporting Files" folder for configuring application mitigations defined in the STIG. This can also be modified to explicitly enforce the system level requirements. Adding the following to the XML file will explicitly turn Validate heap integrity on (other system level EP requirements can be combined under <SystemConfig>): + +<SystemConfig> + <Heap TerminateOnError="true"></Heap> +</SystemConfig> + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.This is applicable to unclassified systems, for other systems this is NA. + +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -System". + +If the status of "Heap: TerminateOnError" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000060Windows Server 2019 Exploit Protection mitigations must be configured for Acrobat.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93321SV-103409CCI-000366Ensure the following mitigations are turned "ON" for Acrobat.exe: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name Acrobat.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000070Windows Server 2019 Exploit Protection mitigations must be configured for AcroRd32.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93323SV-103411CCI-000366Ensure the following mitigations are turned "ON" for AcroRd32.exe: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name AcroRd32.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000080Windows Server 2019 Exploit Protection mitigations must be configured for chrome.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103413V-93325CCI-000366Ensure the following mitigations are turned "ON" for chrome.exe: + +DEP: +Enable: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name chrome.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000090Windows Server 2019 Exploit Protection mitigations must be configured for EXCEL.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103415V-93327CCI-000366Ensure the following mitigations are turned "ON" for EXCEL.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name EXCEL.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000100Windows Server 2019 Exploit Protection mitigations must be configured for firefox.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103417V-93329CCI-000366Ensure the following mitigations are turned "ON" for firefox.exe: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name firefox.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000110Windows Server 2019 Exploit Protection mitigations must be configured for FLTLDR.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93331SV-103419CCI-000366Ensure the following mitigations are turned "ON" for FLTLDR.EXE: + +DEP: +Enable: ON + +ImageLoad: +BlockRemoteImageLoads: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Child Process: +DisallowChildProcessCreation: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name FLTLDR.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ImageLoad: +BlockRemoteImageLoads: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Child Process: +DisallowChildProcessCreation: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000120Windows Server 2019 Exploit Protection mitigations must be configured for GROOVE.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103421V-93333CCI-000366Ensure the following mitigations are turned "ON" for GROOVE.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +ImageLoad: +BlockRemoteImageLoads: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Child Process: +DisallowChildProcessCreation: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name GROOVE.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +ImageLoad: +BlockRemoteImageLoads: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Child Process: +DisallowChildProcessCreation: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000130Windows Server 2019 Exploit Protection mitigations must be configured for iexplore.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103423V-93335CCI-000366Ensure the following mitigations are turned "ON" for iexplore.exe: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name iexplore.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +BottomUp: ON +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000140Windows Server 2019 Exploit Protection mitigations must be configured for INFOPATH.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103425V-93337CCI-000366Ensure the following mitigations are turned "ON" for INFOPATH.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name INFOPATH.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000150Windows Server 2019 Exploit Protection mitigations must be configured for java.exe, javaw.exe, and javaws.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103427V-93339CCI-000366Ensure the following mitigations are turned "ON" for java.exe, javaw.exe, and javaws.exe: + +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name [application name]" with each of the following substituted for [application name]: +java.exe, javaw.exe, and javaws.exe +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON" for each, this is a finding: + +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000160Windows Server 2019 Exploit Protection mitigations must be configured for lync.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103429V-93341CCI-000366Ensure the following mitigations are turned "ON" for lync.exe: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name lync.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000170Windows Server 2019 Exploit Protection mitigations must be configured for MSACCESS.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103431V-93343CCI-000366Ensure the following mitigations are turned "ON" for MSACCESS.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name MSACCESS.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000180Windows Server 2019 Exploit Protection mitigations must be configured for MSPUB.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103433V-93345CCI-000366Ensure the following mitigations are turned "ON" for MSPUB.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name MSPUB.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000190Windows Server 2019 Exploit Protection mitigations must be configured for OIS.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93347SV-103435CCI-000366Ensure the following mitigations are turned "ON" for OIS.EXE: + +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name OIS.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000200Windows Server 2019 Exploit Protection mitigations must be configured for OneDrive.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93349SV-103437CCI-000366Ensure the following mitigations are turned "ON" for OneDrive.exe: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +ImageLoad: +BlockRemoteImageLoads: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name OneDrive.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +ImageLoad: +BlockRemoteImageLoads: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000210Windows Server 2019 Exploit Protection mitigations must be configured for OUTLOOK.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93351SV-103439CCI-000366Ensure the following mitigations are turned "ON" for OUTLOOK.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name OUTLOOK.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000220Windows Server 2019 Exploit Protection mitigations must be configured for plugin-container.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93353SV-103441CCI-000366Ensure the following mitigations are turned "ON" for plugin-container.exe: + +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name plugin-container.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000230Windows Server 2019 Exploit Protection mitigations must be configured for POWERPNT.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93355SV-103443CCI-000366Ensure the following mitigations are turned "ON" for POWERPNT.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name POWERPNT.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000240Windows Server 2019 Exploit Protection mitigations must be configured for PPTVIEW.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93357SV-103445CCI-000366Ensure the following mitigations are turned "ON" for PPTVIEW.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name PPTVIEW.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000250Windows Server 2019 Exploit Protection mitigations must be configured for VISIO.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103447V-93359CCI-000366Ensure the following mitigations are turned "ON" for VISIO.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name VISIO.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000260Windows Server 2019 Exploit Protection mitigations must be configured for VPREVIEW.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103449V-93361CCI-000366Ensure the following mitigations are turned "ON" for VPREVIEW.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name VPREVIEW.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000270Windows Server 2019 Exploit Protection mitigations must be configured for WINWORD.EXE.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93363SV-103451CCI-000366Ensure the following mitigations are turned "ON" for WINWORD.EXE: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name WINWORD.EXE". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +ASLR: +ForceRelocateImages: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000280Windows Server 2019 Exploit Protection mitigations must be configured for wmplayer.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93365SV-103453CCI-000366Ensure the following mitigations are turned "ON" for wmplayer.exe: + +DEP: +Enable: ON + +Payload: +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name wmplayer.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +Payload: +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-EP-000290Windows Server 2019 Exploit Protection mitigations must be configured for wordpad.exe.<VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103455V-93367CCI-000366Ensure the following mitigations are turned "ON" for wordpad.exe: + +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +Application mitigations defined in the STIG are configured by a DoD EP XML file included with the STIG package in the "Supporting Files" folder. + +The XML file is applied with the group policy setting Computer Configuration >> Administrative Settings >> Windows Components >> Windows Defender Exploit Guard >> Exploit Protection >> "Use a common set of exploit protection settings" configured to "Enabled" with file name and location defined under "Options:". It is recommended the file be in a read-only network location.If the referenced application is not installed on the system, this is NA. + +This is applicable to unclassified systems, for other systems this is NA. + +Run "Windows PowerShell" with elevated privileges (run as administrator). + +Enter "Get-ProcessMitigation -Name wordpad.exe". +(Get-ProcessMitigation can be run without the -Name parameter to get a list of all application mitigations configured.) + +If the following mitigations do not have a status of "ON", this is a finding: + +DEP: +Enable: ON + +Payload: +EnableExportAddressFilter: ON +EnableExportAddressFilterPlus: ON +EnableImportAddressFilter: ON +EnableRopStackPivot: ON +EnableRopCallerCheck: ON +EnableRopSimExec: ON + +The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-MS-000050Windows Server 2019 must limit the caching of logon credentials to four or less on domain-joined member servers.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103363V-93275CCI-000366Configure 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.This applies to member servers. For domain controllers and standalone systems, 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 NT\CurrentVersion\Winlogon\ + +Value Name: CachedLogonsCount + +Value Type: REG_SZ +Value: 4 (or less)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-MS-000140Windows Server 2019 must be running Credential Guard on domain-joined member servers.<VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. This authentication information, which was stored in the Local Security Authority (LSA) in previous versions of Windows, is isolated from the rest of operating system and can only be accessed by privileged system 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93277SV-103365CCI-000366Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Device Guard >> "Turn On Virtualization Based Security" to "Enabled" with "Enabled with UEFI lock" selected for "Credential Guard Configuration". + +A Microsoft article on Credential Guard system requirement can be found at the following link: + +https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements + +Severity Override Guidance: The AO can allow the severity override if they have reviewed the overall protection provided to the affected servers that are not capable of complying with the Credential Guard requirement. Items that should be reviewed/considered for compliance or mitigation for non-Credential Guard compliance are: + +The use of Microsoft Local Administrator Password Solution (LAPS) or similar products to control different local administrative passwords for all affected affected servers. This is to include a strict password change requirement (60 days or less). +…. +Strict separation of roles and duties. Server administrator credentials cannot be used on Windows 10 desktop to administer it. Documentation of all exceptions should be supplied. +…. +Use of a Privileged Access Workstation (PAW) and adherence to the Clean Source principle for administering affected affected servers. +…. +Boundary Protection that is currently in place to protect from vulnerabilities in the network/servers. +…. +Windows Defender rule block credential stealing from LSASS.exe is applied. This rule can only be applied if Windows Defender is in use. +…. +The overall number of vulnerabilities that are unmitigated on the network/servers. +For domain controllers and standalone systems, this is NA. + +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. + +Open "PowerShell" with elevated privileges (run as administrator). + +Enter the following: + +"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" + +If "SecurityServicesRunning" does not include a value of "1" (e.g., "{1, 2}"), this is a finding. + +Alternately: + +Run "System Information". + +Under "System Summary", verify the following: + +If "Device Guard Security Services Running" does not list "Credential Guard", this is a finding. + +The policy settings referenced in the Fix section will configure the following registry value. However, due to hardware requirements, the registry value alone does not ensure proper function. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ + +Value Name: LsaCfgFlags +Value Type: REG_DWORD +Value: 0x00000001 (1) (Enabled with UEFI lock) + +A Microsoft article on Credential Guard system requirement can be found at the following link: + +https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirementsSRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000020Windows Server 2019 must prevent local accounts with blank passwords from being used 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 does 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93279SV-103367CCI-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".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\Lsa\ + +Value Name: LimitBlankPasswordUse + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000030Windows Server 2019 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93281SV-103369CCI-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".Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "NewAdministratorName" is not something other than "Administrator" in the file, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000040Windows Server 2019 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103371V-93283CCI-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".Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. + +For server core installations, run the following command: + +Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt + +If "NewGuestName" is not something other than "Guest" in the file, this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000100Windows Server 2019 maximum age for machine account passwords must be configured to 30 days or less.<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 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103373V-93285CCI-000366This is the default configuration for this setting (30 days). + +Configure 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).This is the default configuration for this setting (30 days). + +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\Services\Netlogon\Parameters\ + +Value Name: MaximumPasswordAge + +Value Type: REG_DWORD +Value: 0x0000001e (30) (or less, but not 0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000150Windows Server 2019 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93287SV-103375CCI-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".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 NT\CurrentVersion\Winlogon\ + +Value Name: scremoveoption + +Value Type: REG_SZ +Value: 1 (Lock Workstation) or 2 (Force Logoff) + +If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000210Windows Server 2019 must not allow anonymous SID/Name translation.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103377V-93289CCI-000366Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network access: Allow anonymous SID/Name translation" to "Disabled".Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. + +If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding.SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000220Windows Server 2019 must not allow anonymous enumeration of Security Account Manager (SAM) accounts.<VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93291SV-103379CCI-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".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\Lsa\ + +Value Name: RestrictAnonymousSAM + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000240Windows Server 2019 must be configured to prevent anonymous users from having the same permissions as the Everyone group.<VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93293SV-103381CCI-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".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\Lsa\ + +Value Name: EveryoneIncludesAnonymous + +Value Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000260Windows Server 2019 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously.<VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103383V-93295CCI-000366Configure 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".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\LSA\ + +Value Name: UseMachineId + +Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000270Windows Server 2019 must prevent NTLM 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93297SV-103385CCI-000366Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> "Network security: Allow LocalSystem NULL session fallback" 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: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ + +Value Name: allownullsessionfallback + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000280Windows Server 2019 must prevent PKU2U authentication using online identities.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103387V-93299CCI-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".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\LSA\pku2u\ + +Value Name: AllowOnlineID + +Type: REG_DWORD +Value: 0x00000000 (0)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000310Windows Server 2019 LAN Manager authentication level must be configured 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 standalone 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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103389V-93301CCI-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".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\Lsa\ + +Value Name: LmCompatibilityLevel + +Value Type: REG_DWORD +Value: 0x00000005 (5)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000320Windows Server 2019 must be configured to at least negotiate signing for LDAP client signing.<VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103391V-93303CCI-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.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\Services\LDAP\ + +Value Name: LDAPClientIntegrity + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000330Windows Server 2019 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption.<VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103393V-93305CCI-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).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\Lsa\MSV1_0\ + +Value Name: NTLMMinClientSec + +Value Type: REG_DWORD +Value: 0x20080000 (537395200)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000340Windows Server 2019 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption.<VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103395V-93307CCI-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).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\Lsa\MSV1_0\ + +Value Name: NTLMMinServerSec + +Value Type: REG_DWORD +Value: 0x20080000 (537395200)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-SO-000370Windows Server 2019 default permissions of global system objects must be strengthened.<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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93309SV-103397CCI-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".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\ + +Value Name: ProtectionMode + +Value Type: REG_DWORD +Value: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-UC-000010Windows Server 2019 must preserve zone information when saving attachments.<VulnDiscussion>Attachments from outside sources may contain malicious code. 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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103399V-93311CCI-000366The default behavior is for Windows to mark file attachments with their zone information. + +If this needs to be corrected, configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager >> "Do not preserve zone information in file attachments" to "Not Configured" or "Disabled".The default behavior is for Windows to mark file attachments with their zone information. + +If the registry Value Name below does not exist, this is not a finding. + +If it exists and is configured with a value of "2", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ + +Value Name: SaveZoneInformation + +Value Type: REG_DWORD +Value: 0x00000002 (2) (or if the Value Name does not exist)SRG-OS-000480-GPOS-00229<GroupDescription></GroupDescription>WN19-CC-000450Windows Server 2019 must disable automatically signing in the last interactive user after a system-initiated restart.<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 MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907SV-103357V-93269CCI-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: 0x00000001 (1)SRG-OS-000480-GPOS-00227<GroupDescription></GroupDescription>WN19-00-000280Windows Server 2019 must have a host-based firewall installed and enabled.<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></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-93571SV-103657CCI-002080CCI-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.SRG-OS-000095-GPOS-00049<GroupDescription></GroupDescription>WN19-CC-000451The Windows Explorer Preview pane must be disabled for Windows Server 2019.<VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. + +Organizations must disable the Windows Preview pane and Windows Detail pane.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS Windows Server 2019DISADPMS TargetMS Windows Server 20192907V-102625SV-111575CCI-000366Ensure the following settings are configured for Windows Server 2019 locally or applied through group policy. + +Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn off Preview Pane" to "Enabled". + +Configure the policy value for User Configuration >> Administrative Templates >> Windows Components >> File Explorer >> Explorer Frame Pane "Turn on or off details pane" to "Enabled" and "Configure details pane" to "Always hide".If the following registry values do not exist or are not configured as specified, this is a finding: + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + +Value Name: NoPreviewPane + +Value Type: REG_DWORD + +Value: 1 + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + +Value Name: NoReadingPane + +Value Type: REG_DWORD + +Value: 1 diff --git a/source/StigData/Processed/WindowsServer-2019-DC-1.5.org.default.xml b/source/StigData/Processed/WindowsServer-2019-DC-1.5.org.default.xml deleted file mode 100644 index 8a58f31a6..000000000 --- a/source/StigData/Processed/WindowsServer-2019-DC-1.5.org.default.xml +++ /dev/null @@ -1,83 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/source/StigData/Processed/WindowsServer-2019-DC-2.2.org.default.xml b/source/StigData/Processed/WindowsServer-2019-DC-2.2.org.default.xml new file mode 100644 index 000000000..f0ee64955 --- /dev/null +++ b/source/StigData/Processed/WindowsServer-2019-DC-2.2.org.default.xml @@ -0,0 +1,81 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/source/StigData/Processed/WindowsServer-2019-DC-1.5.xml b/source/StigData/Processed/WindowsServer-2019-DC-2.2.xml similarity index 90% rename from source/StigData/Processed/WindowsServer-2019-DC-1.5.xml rename to source/StigData/Processed/WindowsServer-2019-DC-2.2.xml index dde48054a..9b5aeb6d1 100644 --- a/source/StigData/Processed/WindowsServer-2019-DC-1.5.xml +++ b/source/StigData/Processed/WindowsServer-2019-DC-2.2.xml @@ -1,11 +1,12 @@ - + - + <VulnDiscussion>This policy setting determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer. The policy is enabled by default, which is the most secure setting for validating that access to target resources is not circumvented. Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93443 False Enforce user logon restrictions @@ -26,12 +27,13 @@ Navigate to Computer Configuration >> Policies >> Windows Settings & If the "Enforce user logon restrictions" is not set to "Enabled", this is a finding. - + <VulnDiscussion>This setting determines the maximum amount of time (in minutes) that a granted session ticket can be used to access a particular service. Session tickets are used only to authenticate new connections with servers. Ongoing operations are not interrupted if the session ticket used to authenticate the connection expires during the connection. Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93445 True '{0}' -le '600' -and '{0}' -ne '0' Maximum lifetime for service ticket @@ -52,12 +54,13 @@ Navigate to Computer Configuration >> Policies >> Windows Settings & If the value for "Maximum lifetime for service ticket" is "0" or greater than "600" minutes, this is a finding. - + <VulnDiscussion>In Kerberos, there are two types of tickets: Ticket Granting Tickets (TGTs) and Service Tickets. Kerberos tickets have a limited lifetime so the time an attacker has to implement an attack is limited. This policy controls how long TGTs can be renewed. With Kerberos, the user's initial authentication to the domain controller results in a TGT, which is then used to request Service Tickets to resources. Upon startup, each computer gets a TGT before requesting a service ticket to the domain controller and any other computers it needs to access. For services that start up under a specified user account, users must always get a TGT first and then get Service Tickets to all computers and services accessed. Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93447 True '{0}' -le '10' -and '{0}' -ne '0' Maximum lifetime for user ticket @@ -78,12 +81,13 @@ Navigate to Computer Configuration >> Policies >> Windows Settings & If the value for "Maximum lifetime for user ticket" is "0" or greater than "10" hours, this is a finding. - + <VulnDiscussion>This setting determines the period of time (in days) during which a user's Ticket Granting Ticket (TGT) may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access. Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93449 True '{0}' -le '7' Maximum lifetime for user ticket renewal @@ -104,12 +108,13 @@ Navigate to Computer Configuration >> Policies >> Windows Settings & If the "Maximum lifetime for user ticket renewal" is greater than "7" days, this is a finding. - + <VulnDiscussion>This setting determines the maximum time difference (in minutes) that Kerberos will tolerate between the time on a client's clock and the time on a server's clock while still considering the two clocks synchronous. In order to prevent replay attacks, Kerberos uses timestamps as part of its protocol definition. For timestamps to work properly, the clocks of the client and the server need to be in sync as much as possible. Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93451 True '{0}' -le '5' Maximum tolerance for computer clock synchronization @@ -130,10 +135,11 @@ Navigate to Computer Configuration >> Policies >> Windows Settings & If the "Maximum tolerance for computer clock synchronization" is greater than "5" minutes, this is a finding. - + <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 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> False + V-93141 True '{0}' -le '3' -and '{0}' -ne '0' Account lockout threshold @@ -148,12 +154,13 @@ If the "Account lockout threshold" is "0" or more than "3" attempts, this is a f - + <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. Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93143 True '{0}' -ge '15' Reset account lockout counter after @@ -168,30 +175,13 @@ If the "Reset account lockout counter after" value is less than "15" minutes, th - - <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - True - '{0}' -ge '15' -or '{0}' -eq '0' - Account lockout duration - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. - -If the "Account lockout duration" is less than "15" minutes (excluding "0"), this is a finding. - - - - + <VulnDiscussion>The use of complex passwords increases their strength against attack. The built-in Windows password complexity policy requires passwords to contain at least three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93459 False Password must meet complexity requirements @@ -206,29 +196,11 @@ If the value for "Password must meet complexity requirements" is not set to "Ena - - <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> - - False - True - '{0}' -ge '14' - Minimum password length - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for the "Minimum password length," is less than "14" characters, this is a finding. - - - - + <VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. 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></IAControls> False + V-93465 False Store passwords using reversible encryption @@ -243,10 +215,11 @@ If the value for "Store passwords using reversible encryption" is not set to "Di - + <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> False + V-93471 True '{0}' -ne '0' Minimum password age @@ -261,10 +234,11 @@ If the value for the "Minimum password age" is set to "0" days ("Password can be - + <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> False + V-93477 True '{0}' -le '60' -and '{0}' -ne '0' Maximum password age @@ -281,10 +255,11 @@ If the value is set to "0" (never expires), this is a finding. - + <VulnDiscussion>A system is more vulnerable to unauthorized access when system users recycle the same password several times without being required to change 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> False + V-93479 True '{0}' -ge '24' Enforce password history @@ -297,20 +272,60 @@ Navigate to Local Computer Policy >> Computer Configuration >> Windo If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding. + + + + <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> + + False + V-93463 + True + '{0}' -ge '14' + Minimum password length + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for the "Minimum password length," is less than "14" characters, this is a finding. + + + + + <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93145 + True + '{0}' -ge '15' -or '{0}' -eq '0' + Account lockout duration + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. + +If the "Account lockout duration" is less than "15" minutes (excluding "0"), this is a finding. + - + Success <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. +Security Group Management records events such as creating, deleting, or changing security groups, including changes in group members. -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92979 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -325,19 +340,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Logon - Success - Logon +Account Management >> Security Group Management - Success + Security Group Management - - Failure + + Success <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. +User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92981 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -352,19 +368,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Logon - Failure - Logon +Account Management >> User Account Management - Success + User Account Management - - Success + + Failure <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 security groups, including changes in group members. +User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92983 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -379,22 +396,25 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Account Management >> Security Group Management - Success - Security Group Management +Account Management >> User Account Management - Failure + User Account Management - + Success <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. +Computer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts. Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92985 False - Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + This applies to domain controllers. It is NA for other systems. + +Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -406,19 +426,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Account Management >> User Account Management - Success - User Account Management +Account Management >> Computer Account Management - Success + Computer Account Management - - Failure + + Success <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. +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. -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92967 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -433,24 +454,23 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Account Management >> User Account Management - Failure - User Account Management +Logon/Logoff >> Logon - Success + Logon - - Success + + Failure <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. -Computer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts. +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. -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92969 False - This applies to domain controllers. It is NA for other systems. - -Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. + Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. Use the "AuditPol" tool to review the current Audit Policy configuration: @@ -462,10 +482,10 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Account Management >> Computer Account Management - Success - Computer Account Management +Logon/Logoff >> Logon - Failure + Logon - + Success <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. @@ -475,6 +495,7 @@ Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion Present False + V-92987 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -492,7 +513,7 @@ If the system does not audit the following, this is a finding. Logon/Logoff >> Account Lockout - Success Account Lockout - + Failure <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. @@ -502,6 +523,7 @@ Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion Present False + V-92989 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -519,7 +541,7 @@ If the system does not audit the following, this is a finding. Logon/Logoff >> Account Lockout - Failure Account Lockout - + Success <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. @@ -529,6 +551,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93089 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -546,7 +569,7 @@ If the system does not audit the following, this is a finding: Account Management >> Other Account Management Events - Success Other Account Management Events - + Success <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. @@ -556,6 +579,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215</VulnDiscussion Present False + V-93091 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -573,7 +597,7 @@ If the system does not audit the following, this is a finding. Detailed Tracking >> Process Creation - Success Process Creation - + Success <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. @@ -583,6 +607,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93093 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -600,7 +625,7 @@ If the system does not audit the following, this is a finding. Policy Change >> Audit Policy Change - Success Audit Policy Change - + Failure <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. @@ -610,6 +635,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93095 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -627,7 +653,7 @@ If the system does not audit the following, this is a finding. Policy Change >> Audit Policy Change - Failure Audit Policy Change - + Success <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. @@ -637,6 +663,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93097 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -654,7 +681,7 @@ If the system does not audit the following, this is a finding. Policy Change >> Authentication Policy Change - Success Authentication Policy Change - + Success <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. @@ -664,6 +691,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93099 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -681,7 +709,7 @@ If the system does not audit the following, this is a finding. Policy Change >> Authorization Policy Change - Success Authorization Policy Change - + Success <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. @@ -691,6 +719,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93101 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -708,7 +737,7 @@ If the system does not audit the following, this is a finding. Privilege Use >> Sensitive Privilege Use - Success Sensitive Privilege Use - + Failure <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. @@ -718,6 +747,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93103 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -735,7 +765,7 @@ If the system does not audit the following, this is a finding. Privilege Use >> Sensitive Privilege Use - Failure Sensitive Privilege Use - + Success <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. @@ -745,6 +775,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93105 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -762,7 +793,7 @@ If the system does not audit the following, this is a finding. System >> IPsec Driver - Success IPsec Driver - + Failure <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. @@ -772,6 +803,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93107 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -789,7 +821,7 @@ If the system does not audit the following, this is a finding. System >> IPsec Driver - Failure IPsec Driver - + Success <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. @@ -799,6 +831,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93109 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -816,7 +849,7 @@ If the system does not audit the following, this is a finding. System >> Other System Events - Success Other System Events - + Failure <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. @@ -826,6 +859,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93111 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -843,7 +877,7 @@ If the system does not audit the following, this is a finding. System >> Other System Events - Failure Other System Events - + Success <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. @@ -853,6 +887,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93113 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -870,7 +905,7 @@ If the system does not audit the following, this is a finding. System >> Security State Change - Success Security State Change - + Success <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. @@ -880,6 +915,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93115 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -897,7 +933,7 @@ If the system does not audit the following, this is a finding. System >> Security System Extension - Success Security System Extension - + Success <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. @@ -907,6 +943,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPO Present False + V-93117 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -924,7 +961,7 @@ If the system does not audit the following, this is a finding. System >> System Integrity - Success System Integrity - + Failure <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. @@ -934,6 +971,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPO Present False + V-93119 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -951,7 +989,7 @@ If the system does not audit the following, this is a finding. System >> System Integrity - Failure System Integrity - + Success <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. @@ -961,6 +999,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93133 False This applies to domain controllers. It is NA for other systems. @@ -980,7 +1019,7 @@ If the system does not audit the following, this is a finding. DS Access >> Directory Service Access - Success Directory Service Access - + Failure <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. @@ -990,6 +1029,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93135 False This applies to domain controllers. It is NA for other systems. @@ -1009,7 +1049,7 @@ If the system does not audit the following, this is a finding. DS Access >> Directory Service Access - Failure Directory Service Access - + Success <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. @@ -1019,6 +1059,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93137 False This applies to domain controllers. It is NA for other systems. @@ -1038,7 +1079,7 @@ If the system does not audit the following, this is a finding. DS Access >> Directory Service Changes - Success Directory Service Changes - + Failure <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. @@ -1048,6 +1089,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93139 False This applies to domain controllers. It is NA for other systems. @@ -1067,7 +1109,7 @@ If the system does not audit the following, this is a finding. DS Access >> Directory Service Changes - Failure Directory Service Changes - + Success <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. @@ -1075,6 +1117,7 @@ Credential Validation records events related to validation tests on credentials Present False + V-93153 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1092,7 +1135,7 @@ If the system does not audit the following, this is a finding. Account Logon >> Credential Validation - Success Credential Validation - + Failure <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. @@ -1100,6 +1143,7 @@ Credential Validation records events related to validation tests on credentials Present False + V-93155 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1117,14 +1161,15 @@ If the system does not audit the following, this is a finding. Account Logon >> Credential Validation - Failure Credential Validation - + Success <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. -Plug and Play activity records events related to the successful connection of external devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Audit Group Membership records information related to the group membership of a user's logon token.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93159 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1139,17 +1184,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Detailed Tracking >> Plug and Play Events - Success - Plug and Play Events +Logon/Logoff >> Group Membership - Success + Group Membership - + Success <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 Group Membership records information related to the group membership of a user's logon token.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Special Logon records special logons that have administrative privileges and can be used to elevate processes. + +Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93161 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1164,19 +1212,18 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Group Membership - Success - Group Membership +Logon/Logoff >> Special Logon - Success + Special Logon - + Success <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 that have administrative privileges and can be used to elevate processes. - -Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93163 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1191,17 +1238,18 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Special Logon - Success - Special Logon +Object Access >> Other Object Access Events - Success + Other Object Access Events - - Success + + Failure <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 for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93165 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1216,17 +1264,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Object Access >> Other Object Access Events - Success +Object Access >> Other Object Access Events - Failure Other Object Access Events - - Failure + + Success <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 for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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. + +Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93171 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1241,17 +1292,18 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Object Access >> Other Object Access Events - Failure - Other Object Access Events +Logon/Logoff >> Logoff - Success + Logoff - + Success <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. -Removable Storage auditing under Object Access 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></IAControls> +Plug and Play activity records events related to the successful connection of external devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93157 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1266,19 +1318,18 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Object Access >> Removable Storage - Success - -Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. - Removable Storage +Detailed Tracking >> Plug and Play Events - Success + Plug and Play Events - - Failure + + Success <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. Removable Storage auditing under Object Access 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></IAControls> Present False + V-93167 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1293,21 +1344,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Object Access >> Removable Storage - Failure +Object Access >> Removable Storage - Success Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. Removable Storage - - Success + + Failure <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. - -Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Removable Storage auditing under Object Access 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></IAControls> Present False + V-93169 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1322,16 +1372,19 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Logoff - Success - Logoff +Object Access >> Removable Storage - Failure + +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. + Removable Storage - + <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 a file system that supports NTFS attributes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> NTFS|ReFS False + V-92991 -match False @@ -1347,11 +1400,12 @@ For each local volume, if the file system does not indicate "NTFS", this is a fi This does not apply to system partitions such the Recovery and EFI System Partition. - + <VulnDiscussion>Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level 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> 10.0.17763 False + V-93215 -le False @@ -1367,246 +1421,240 @@ Preview versions must not be used in a production environment. - - <VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems relying on the directory service. - -For Active Directory (AD), the Group Policy objects require special attention. In a distributed administration model (i.e., help desk), Group Policy objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for Group Policy objects, this could allow an intruder to change the security policy applied to all domain client computers (workstations and servers).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93485 False This applies to domain controllers. It is NA for other systems. -Review the permissions on Group Policy objects. - -Open "Group Policy Management" (available from various menus or run "gpmc.msc"). - -Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). +Review user account mappings to PKI certificates. -For each Group Policy object: +Open "Windows PowerShell". -Select the Group Policy object item in the left pane. +Enter "Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled". -Select the "Delegation" tab in the right pane. +Exclude disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. -Select the "Advanced" button. +If the User Principal Name (UPN) is not in the format of an individual's identifier for the certificate type and for the appropriate domain suffix, this is a finding. -Select each Group or user name. +For standard NIPRNet certificates, the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI). -View the permissions. +Alt Tokens and other certificates may use a different UPN format than the EDI-PI which vary by organization. Verified these with the organization. -If any standard user accounts or groups have "Allow" permissions greater than "Read" and "Apply group policy", this is a finding. +NIPRNet Example: -Other access permissions that allow the objects to be updated are considered findings unless specifically documented by the ISSO. +Name - User Principal Name +User1 - 1234567890@mil -The default permissions noted below satisfy this requirement. +See PKE documentation for other network domain suffixes. -The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next "Advanced" button, the desired Permission entry, and the "Edit" button. +If the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding. + + + <VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93381 + False + + Required roles and features will vary based on the function of the individual system. -Authenticated Users - Read, Apply group policy, Special permissions +Roles and features specifically required to be disabled per the STIG are identified in separate requirements. -The special permissions for Authenticated Users are for Read-type Properties. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. +If the organization has not documented the roles and features required for the system(s), this is a finding. -The special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties: +The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State". + + + <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 nonrepudiation or individual accountability for system access and resource usage.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93437 + False + + Determine whether any shared accounts exist. If no shared accounts exist, this is NA. -CREATOR OWNER - Special permissions -SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions -Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions +Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. -The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on organization created Group Policy objects. +If unapproved shared accounts exist, this is a finding. - - <VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. - -For Active Directory, the OU objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a denial of service (DoS) to authorized users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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, disabled until needed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93457 False - This applies to domain controllers. It is NA for other systems. + Open "Windows PowerShell". -Review the permissions on domain-defined OUs. +Domain Controllers: -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" -Ensure "Advanced Features" is selected in the "View" menu. +This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. -For each OU that is defined (folder in folder icon) excluding the Domain Controllers OU: +Member servers and standalone systems: -Right-click the OU and select "Properties". +Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) -Select the "Security" tab. +"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { + $user = ([ADSI]$_.Path) + $lastLogin = $user.Properties.LastLogin.Value + $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 + if ($lastLogin -eq $null) { + $lastLogin = 'Never' + } + Write-Host $user.Name $lastLogin $enabled +}" -If the Allow type permissions on the OU are not at least as restrictive as those below, this is a finding. +This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). +For example: User1 10/31/2015 5:49:56 AM True -The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "Edit" or "View" button. +Review the list of accounts returned by the above queries to determine the finding validity for each account reported. -Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. +Exclude the following accounts: -CREATOR OWNER - Special permissions +- Built-in administrator account (Renamed, SID ending in 500) +- Built-in guest account (Renamed, Disabled, SID ending in 501) +- Application accounts -Self - Special permissions +If any enabled accounts have not been logged on to within the past 35 days, this is a finding. -Authenticated Users - Read, Special permissions +Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO. + + + <VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93567 + False + + Verify DoD-approved ESS software is installed and properly operating. Ask the site ISSM for documentation of the ESS software installation and configuration. -The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. +If the ISSM is not able to provide a documented configuration for an installed ESS or if the ESS software is not properly maintained or used, this is a finding. -SYSTEM - Full Control +Note: Example of documentation can be a copy of the site's CCB approved Software Baseline with version of software noted or a memo from the ISSM stating current ESS software and version. + + + <VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems relying on the directory service. -Domain Admins - Full Control +For Active Directory (AD), the Group Policy objects require special attention. In a distributed administration model (i.e., help desk), Group Policy objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for Group Policy objects, this could allow an intruder to change the security policy applied to all domain client computers (workstations and servers).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93033 + False + + This applies to domain controllers. It is NA for other systems. -Enterprise Admins - Full Control +Review the permissions on Group Policy objects. -Key Admins - Special permissions +Open "Group Policy Management" (available from various menus or run "gpmc.msc"). -Enterprise Key Admins - Special permissions +Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions +For each Group Policy object: -Pre-Windows 2000 Compatible Access - Special permissions +Select the Group Policy object item in the left pane. -The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. +Select the "Delegation" tab in the right pane. -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions +Select the "Advanced" button. -If an ISSO-approved distributed administration model (help desk or other user support staff) is implemented, permissions above Read may be allowed for groups documented by the ISSO. +Select each Group or user name. -If any OU with improper permissions includes identification or authentication data (e.g., accounts, passwords, or password hash data) used by systems to determine access control, the severity is CAT I (e.g., OUs that include user accounts, including service/application accounts). +View the permissions. -If an OU with improper permissions does not include identification and authentication data used by systems to determine access control, the severity is CAT II (e.g., Workstation, Printer OUs). - - - <VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine whether there is a HIDS or HIPS on each server. +If any standard user accounts or groups have "Allow" permissions greater than "Read" and "Apply group policy", this is a finding. -If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. +Other access permissions that allow the objects to be updated are considered findings unless specifically documented by the ISSO. -A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. +The default permissions noted below satisfy this requirement. -If a HIDS is not installed on the system, this is a finding. - - - <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> - - False - False - - Search all drives for *.p12 and *.pfx files. +The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next "Advanced" button, the desired Permission entry, and the "Edit" button. -If any files with these extensions exist, this is a finding. +Authenticated Users - Read, Apply group policy, Special permissions -This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. 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. - - - <VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Required roles and features will vary based on the function of the individual system. +The special permissions for Authenticated Users are for Read-type Properties. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. -Roles and features specifically required to be disabled per the STIG are identified in separate requirements. +The special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties: -If the organization has not documented the roles and features required for the system(s), this is a finding. +CREATOR OWNER - Special permissions +SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions +Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions -The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State". +The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on organization created Group Policy objects. - - <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 nonrepudiation or individual accountability for system access and resource usage.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. + +For Active Directory, the OU objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a denial of service (DoS) to authorized users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93037 False - Determine whether any shared accounts exist. If no shared accounts exist, this is NA. + This applies to domain controllers. It is NA for other systems. -Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity. +Review the permissions on domain-defined OUs. -If unapproved shared accounts exist, this is a finding. - - - <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, disabled until needed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Open "Windows PowerShell". +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Domain Controllers: +Ensure "Advanced Features" is selected in the "View" menu. -Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00" +For each OU that is defined (folder in folder icon) excluding the Domain Controllers OU: -This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate. +Right-click the OU and select "Properties". -Member servers and standalone systems: +Select the "Security" tab. -Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.) +If the Allow type permissions on the OU are not at least as restrictive as those below, this is a finding. -"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach { - $user = ([ADSI]$_.Path) - $lastLogin = $user.Properties.LastLogin.Value - $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2 - if ($lastLogin -eq $null) { - $lastLogin = 'Never' - } - Write-Host $user.Name $lastLogin $enabled -}" +The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "Edit" or "View" button. -This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False). -For example: User1 10/31/2015 5:49:56 AM True +Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. -Review the list of accounts returned by the above queries to determine the finding validity for each account reported. +CREATOR OWNER - Special permissions -Exclude the following accounts: +Self - Special permissions -- Built-in administrator account (Renamed, SID ending in 500) -- Built-in guest account (Renamed, Disabled, SID ending in 501) -- Application accounts +Authenticated Users - Read, Special permissions -If any enabled accounts have not been logged on to within the past 35 days, this is a finding. +The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. -Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO. - - - <VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - This applies to domain controllers. It is NA for other systems. +SYSTEM - Full Control -Review user account mappings to PKI certificates. +Domain Admins - Full Control -Open "Windows PowerShell". +Enterprise Admins - Full Control -Enter "Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled". +Key Admins - Special permissions -Exclude disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. +Enterprise Key Admins - Special permissions -If the User Principal Name (UPN) is not in the format of an individual's identifier for the certificate type and for the appropriate domain suffix, this is a finding. +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions -For standard NIPRNet certificates, the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI). +Pre-Windows 2000 Compatible Access - Special permissions -Alt Tokens and other certificates may use a different UPN format than the EDI-PI which vary by organization. Verified these with the organization. +The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. -NIPRNet Example: +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions -Name - User Principal Name -User1 - 1234567890@mil +If an ISSO-approved distributed administration model (help desk or other user support staff) is implemented, permissions above Read may be allowed for groups documented by the ISSO. -See PKE documentation for other network domain suffixes. +If any OU with improper permissions includes identification or authentication data (e.g., accounts, passwords, or password hash data) used by systems to determine access control, the severity is CAT I (e.g., OUs that include user accounts, including service/application accounts). -If the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding. +If an OU with improper permissions does not include identification and authentication data used by systems to determine access control, the severity is CAT II (e.g., Workstation, Printer OUs). - + <VulnDiscussion>Directory data that is not appropriately encrypted is subject to compromise. Commercial-grade encryption does not provide adequate protection when the classification level of directory data in transit is higher than the level of the network.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93513 False This applies to domain controllers. It is NA for other systems. @@ -1619,19 +1667,37 @@ If the classification level of the Windows domain controller is higher than the If the classification level of the Windows domain controller is higher than the level of the network traversed and NSA-approved encryption is not used, this is a finding. - - <VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93219 + False + + Determine whether there is a HIDS or HIPS on each server. + +If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. + +A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. + +If a HIDS is not installed on the system, this is a finding. + + + <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> False + V-93221 False - Verify DoD approved HBSS software is installed, configured, and properly operating. Ask the operator to document the HBSS software installation and configuration. + Search all drives for *.p12 and *.pfx files. + +If any files with these extensions exist, this is a finding. -If the operator is not able to provide a documented configuration for an installed HBSS or if the HBSS software is not properly configured, maintained, or used, this is a finding. +This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. 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. - + <VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. @@ -1641,6 +1707,7 @@ If temporary accounts are used, the operating system must be configured to autom To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-92975 False Review temporary user accounts for expiration dates. @@ -1663,1157 +1730,1198 @@ Run "Net user [username]", where [username] is the name of the temporary user ac If "Account expires" has not been defined within 72 hours for any temporary user account, this is a finding. - - <VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. - -Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. - -To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Domain controllers are part of the chain of trust for PKI authentications. Without the appropriate certificate, the authenticity of the domain controller cannot be verified. Domain controllers must have a server certificate to establish authenticity as part of PKI authentications in the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93481 False - Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. + This applies to domain controllers. It is NA for other systems. -If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. +Run "MMC". -If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. +Select "Add/Remove Snap-in" from the "File" menu. -Domain Controllers: +Select "Certificates" in the left pane and click the "Add >" button. -Open "PowerShell". +Select "Computer Account" and click "Next". -Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". +Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". -If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. +Click "OK". -Member servers and standalone systems: +Select and expand the Certificates (Local Computer) entry in the left pane. -Open "Command Prompt". +Select and expand the Personal entry in the left pane. -Run "Net user [username]", where [username] is the name of the emergency account. +Select the Certificates entry in the left pane. -If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. +If no certificate for the domain controller exists in the right pane, this is a finding. - - <VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93483 False - Open "Printers & scanners" in "Settings". + This applies to domain controllers. It is NA for other systems. -If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) +Run "MMC". -For each printer: +Select "Add/Remove Snap-in" from the "File" menu. -Select the printer and "Manage". +Select "Certificates" in the left pane and click the "Add >" button. -Select "Printer Properties". +Select "Computer Account" and click "Next". -Select the "Sharing" tab. +Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". -If "Share this printer" is checked, select the "Security" tab. +Click "OK". -If any standard user accounts or groups have permissions other than "Print", this is a finding. +Select and expand the Certificates (Local Computer) entry in the left pane. -The default is for the "Everyone" group to be given "Print" permission. +Select and expand the Personal entry in the left pane. -"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts. - - - <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. +Select the Certificates entry in the left pane. -System administrators must log on to systems using only accounts with the minimum level of authority necessary. +In the right pane, examine the "Issued By" field for the certificate to determine the issuing CA. -Standard user accounts must not be members of the built-in Administrators group.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +If the "Issued By" field of the PKI certificate being used by the domain controller does not indicate the issuing CA is part of the DoD PKI or an approved ECA, this is a finding. + +If the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding. + +There are multiple sources from which lists of valid DoD CAs and approved ECAs can be obtained: + +The Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil. + +DoD Public Key Enablement (PKE) Engineering Support maintains the InstallRoot utility to manage DoD supported root certificates on Windows computers, which includes a list of authorized CAs. The utility package can be downloaded from the PKI and PKE Tools page on IASE: + +http://iase.disa.mil/pki-pke/function_pages/tools.html + + + <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. + +Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93473 False - This applies to domain controllers. A separate version applies to other systems. + Review the password last set date for the built-in Administrator account. -Review the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group. +Domain controllers: -Standard user accounts must not be members of the local administrator group. +Open "PowerShell". -If prohibited accounts are members of the local administrators group, this is a finding. +Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". -If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding. +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. + +Member servers and standalone systems: + +Open "Command Prompt". + +Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. + +(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) + +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. - - <VulnDiscussion>Improper access permissions for directory data-related files could allow unauthorized users to read, modify, or delete directory data or audit trails.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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> False + V-93475 False - This applies to domain controllers. It is NA for other systems. - -Run "Regedit". + Review the password never expires status for enabled user accounts. -Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". +Open "PowerShell". -Note the directory locations in the values for: +Domain Controllers: -Database log files path -DSA Database file +Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". -By default, they will be \Windows\NTDS. +Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. -If the locations are different, the following will need to be run for each. +If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. -Open "Command Prompt (Admin)". +Member servers and standalone systems: -Navigate to the NTDS directory (\Windows\NTDS by default). +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. -Run "icacls *.*". +Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). -If the permissions on each file are not as restrictive as the following, this is a finding: +If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding. + + + <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></IAControls> + + False + V-93461 + False + + Determine if manually managed application/service accounts exist. If none exist, this is NA. -NT AUTHORITY\SYSTEM:(I)(F) -BUILTIN\Administrators:(I)(F) +Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. -(I) - permission inherited from parent container -(F) - full access +If such a policy does not exist or has not been implemented, this is a finding. - - <VulnDiscussion>When Active Directory objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. - -The Domain Controllers OU object requires special attention as the Domain Controllers are central to the configuration and management of the domain. Inappropriate access permissions defined for the Domain Controllers OU could allow an intruder or unauthorized personnel to make changes that could lead to the compromise of the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-92993 False - This applies to domain controllers. It is NA for other systems. + Open "Printers & scanners" in "Settings". -Review the permissions on the Domain Controllers OU. +If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +For each printer: -Select "Advanced Features" in the "View" menu if not previously selected. +Select the printer and "Manage". -Select the "Domain Controllers" OU (folder in folder icon). +Select "Printer Properties". -Right-click and select "Properties". +Select the "Sharing" tab. -Select the "Security" tab. +If "Share this printer" is checked, select the "Security" tab. -If the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding. +If any standard user accounts or groups have permissions other than "Print", this is a finding. -The default permissions listed below satisfy this requirement. +The default is for the "Everyone" group to be given "Print" permission. -Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions and are not a finding. +"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts. + + + <VulnDiscussion>Executing application servers on the same host machine with a directory server may substantially weaken the security of the directory server. Web or database server applications usually require the addition of many programs and accounts, increasing the attack surface of the computer. -The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "View" or "Edit" button. +Some applications require the addition of privileged accounts, providing potential sources of compromise. Some applications (such as Microsoft Exchange) may require the use of network ports or services conflicting with the directory server. In this case, non-standard ports might be selected, and this could interfere with intrusion detection or prevention services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93417 + False + + This applies to domain controllers, it is NA for other systems. -Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. +Review the installed roles the domain controller is supporting. -CREATOR OWNER - Special permissions +Start "Server Manager". -SELF - Special permissions +Select "AD DS" in the left pane and the server name under "Servers" to the right. -Authenticated Users - Read, Special permissions +Select "Add (or Remove) Roles and Features" from "Tasks" in the "Roles and Features" section. (Cancel before any changes are made.) -The special permissions for Authenticated Users are Read types. +Determine if any additional server roles are installed. A basic domain controller setup will include the following: -If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. +- Active Directory Domain Services +- DNS Server +- File and Storage Services -SYSTEM - Full Control +If any roles not requiring installation on a domain controller are installed, this is a finding. -Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions +A Domain Name System (DNS) server integrated with the directory server (e.g., AD-integrated DNS) is an acceptable application. However, the DNS server must comply with the DNS STIG security requirements. -Enterprise Admins - Full Control +Run "Programs and Features". -Key Admins - Special permissions +Review installed applications. -Enterprise Key Admins - Special permissions +If any applications are installed that are not required for the domain controller, this is a finding. + + + <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. 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> + + False + V-93439 + False + + Review the password required status for enabled user accounts. -Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions +Open "PowerShell". -Pre-Windows 2000 Compatible Access - Special permissions +Domain Controllers: -The Special permissions for Pre-Windows 2000 Compatible Access are Read types. +Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". -If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. +Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). -ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions - - - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. +If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. +Member servers and standalone systems: -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. + +Exclude disabled accounts (e.g., DefaultAccount, Guest). + +If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. + + + <VulnDiscussion>Smart cards such as the CAC support a two-factor authentication technique. This provides a higher level of trust in the asserted identity than use of the username and password for authentication. + +Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93441 False This applies to domain controllers. It is NA for other systems. -Review the auditing configuration for all Group Policy objects. - -Open "Group Policy Management" (available from various menus or run "gpmc.msc"). - -Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). - -For each Group Policy object: +Open "PowerShell". -Select the Group Policy object item in the left pane. +Enter the following: -Select the "Delegation" tab in the right pane. +"Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name" +("DistinguishedName" may be substituted for "Name" for more detailed output.) -Select the "Advanced" button. +If any user accounts, including administrators, are listed, this is a finding. -Select the "Advanced" button again and then the "Auditing" tab. -If the audit settings for any Group Policy object are not at least as inclusive as those below, this is a finding: +Alternately: -Type - Fail -Principal - Everyone -Access - Full Control -Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects +To view sample accounts in "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): -The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. +Select the Organizational Unit (OU) where the user accounts are located. (By default, this is the Users node; however, accounts may be under other organization-defined OUs.) -Type - Success -Principal - Everyone -Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) -Inherited from - Parent Object -Applies to - Descendant groupPolicyContainer objects +Right-click the sample user account and select "Properties". -Two instances with the following summary information will be listed: +Select the "Account" tab. -Type - Success -Principal - Everyone -Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) -Inherited from - Parent Object -Applies to - Descendant Organization Unit Objects +If any user accounts, including administrators, do not have "Smart card is required for interactive logon" checked in the "Account Options" area, this is a finding. - - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + + <VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. +Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-92977 False - This applies to domain controllers. It is NA for other systems. + Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. -Review the auditing configuration for the Domain object. +If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. -Ensure "Advanced Features" is selected in the "View" menu. +Domain Controllers: -Select the domain being reviewed in the left pane. +Open "PowerShell". -Right-click the domain name and select "Properties". +Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". -Select the "Security" tab. +If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. -Select the "Advanced" button and then the "Auditing" tab. +Member servers and standalone systems: -If the audit settings on the Domain object are not at least as inclusive as those below, this is a finding: +Open "Command Prompt". -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only +Run "Net user [username]", where [username] is the name of the emergency account. -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. + + + <VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93531 + False + + If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) -Two instances with the following summary information will be listed: +Run "Computer Management". -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - None -Applies to - Special +Navigate to System Tools >> Shared Folders >> Shares. -Type - Success -Principal - Domain Users -Access - All extended rights -Inherited from - None -Applies to - This object only +Right-click any non-system-created shares. -Type - Success -Principal - Administrators -Access - All extended rights -Inherited from - None -Applies to - This object only +Select "Properties". -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner) - - - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. +Select the "Share Permissions" tab. -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. +If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Select the "Security" tab. + +If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. + + + <VulnDiscussion>When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. + +The directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93535 False This applies to domain controllers. It is NA for other systems. -Review the auditing configuration for Infrastructure object. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select the domain being reviewed in the left pane. - -Right-click the "Infrastructure" object in the right pane and select "Properties". - -Select the "Security" tab. +Run "Regedit". -Select the "Advanced" button and then the "Auditing" tab. +Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". -If the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding: +Note the directory locations in the values for "DSA Database file". -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None +Open "Command Prompt". -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Enter "net share". -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) +Note the logical drive(s) or file system partition for any organization-created data shares. -Two instances with the following summary information will be listed: +Ignore system shares (e.g., NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) should not be ignored. -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) +If user shares are located on the same logical partition as the directory server data files, this is a finding. - - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>The failure to terminate inactive network connections increases the risk of a successful attack on the directory server. The longer an established session is in progress, the more time an attacker has to hijack the session, implement a means to passively intercept data, or compromise any protections on client access. For example, if an attacker gains control of a client computer, an existing (already authenticated) session with the directory server could allow access to the directory. The lack of confidentiality protection in LDAP-based sessions increases exposure to this vulnerability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93509 False This applies to domain controllers. It is NA for other systems. -Review the auditing configuration for the Domain Controller OU object. +Open an elevated "Command Prompt" (run as administrator). -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +Enter "ntdsutil". -Ensure "Advanced Features" is selected in the "View" menu. +At the "ntdsutil:" prompt, enter "LDAP policies". -Select the "Domain Controllers OU" under the domain being reviewed in the left pane. +At the "ldap policy:" prompt, enter "connections". -Right-click the "Domain Controllers OU" object and select "Properties". +At the "server connections:" prompt, enter "connect to server [host-name]" +(where [host-name] is the computer name of the domain controller). -Select the "Security" tab. +At the "server connections:" prompt, enter "q". -Select the "Advanced" button and then the "Auditing" tab. +At the "ldap policy:" prompt, enter "show values". -If the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding: +If the value for MaxConnIdleTime is greater than "300" (5 minutes) or is not specified, this is a finding. -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object and all descendant objects +Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit. -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Alternately, Dsquery can be used to display MaxConnIdleTime: -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Permissions: all create, delete and modify permissions) +Open "Command Prompt (Admin)". +Enter the following command (on a single line). -Type - Success -Principal - Everyone -Access - Write all properties -Inherited from - None -Applies to - This object and all descendant objects +dsquery * "cn=Default Query Policy,cn=Query-Policies,cn=Directory Service, cn=Windows NT,cn=Services,cn=Configuration,dc=[forest-name]" -attr LDAPAdminLimits -Two instances with the following summary information will be listed: +The quotes are required and dc=[forest-name] is the fully qualified LDAP name of the domain being reviewed (e.g., dc=disaost,dc=mil). -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objects +If the results do not specify a "MaxConnIdleTime" or it has a value greater than "300" (5 minutes), this is a finding. - - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + + <VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. +Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93515 False - This applies to domain controllers. It is NA for other systems. - -Review the auditing configuration for the "AdminSDHolder" object. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). - -Ensure "Advanced Features" is selected in the "View" menu. - -Select "System" under the domain being reviewed in the left pane. - -Right-click the "AdminSDHolder" object in the right pane and select "Properties". - -Select the "Security" tab. + Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. -Select the "Advanced" button and then the "Auditing" tab. +If they do not, this is a finding. + + + <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. -If the audit settings on the "AdminSDHolder" object are not at least as inclusive as those below, this is a finding: +System administrators must log on to systems using only accounts with the minimum level of authority necessary. -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None -Applies to - This object only +Standard user accounts must not be members of the built-in Administrators group.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93027 + False + + This applies to domain controllers. A separate version applies to other systems. -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Review the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group. -Type - Success -Principal - Everyone -Access - Special -Inherited from - None -Applies to - This object only -(Access - Special = Write all properties, Modify permissions, Modify owner) +Standard user accounts must not be members of the local administrator group. -Two instances with the following summary information will be listed: +If prohibited accounts are members of the local administrators group, this is a finding. -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) -Applies to - Descendant Organizational Unit objects +If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding. - - <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. - -For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. - -Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Improper access permissions for directory data-related files could allow unauthorized users to read, modify, or delete directory data or audit trails.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93029 False This applies to domain controllers. It is NA for other systems. -Review the auditing configuration for the "RID Manager$" object. - -Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). +Run "Regedit". -Ensure "Advanced Features" is selected in the "View" menu. +Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". -Select "System" under the domain being reviewed in the left pane. +Note the directory locations in the values for: -Right-click the "RID Manager$" object in the right pane and select "Properties". +Database log files path +DSA Database file -Select the "Security" tab. +By default, they will be \Windows\NTDS. -Select the "Advanced" button and then the "Auditing" tab. +If the locations are different, the following will need to be run for each. -If the audit settings on the "RID Manager$" object are not at least as inclusive as those below, this is a finding: +Open "Command Prompt (Admin)". -Type - Fail -Principal - Everyone -Access - Full Control -Inherited from - None +Navigate to the NTDS directory (\Windows\NTDS by default). -The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. +Run "icacls *.*". -Type - Success -Principal - Everyone -Access - Special -Inherited from - None - (Access - Special = Write all properties, All extended rights, Change RID master) +If the permissions on each file are not as restrictive as the following, this is a finding: -Two instances with the following summary information will be listed: +NT AUTHORITY\SYSTEM:(I)(F) +BUILTIN\Administrators:(I)(F) -Type - Success -Principal - Everyone -Access - (blank) -Inherited from - (CN of domain) +(I) - permission inherited from parent container +(F) - full access - - <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine if a process to back up log data to a different system or media than the system being audited has been implemented. + + <VulnDiscussion>When Active Directory objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service. -If it has not, this is a finding. - - - <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +The Domain Controllers OU object requires special attention as the Domain Controllers are central to the configuration and management of the domain. Inappropriate access permissions defined for the Domain Controllers OU could allow an intruder or unauthorized personnel to make changes that could lead to the compromise of the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93035 False - Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. + This applies to domain controllers. It is NA for other systems. -If they are not, this is a finding. - - - <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> - - False - False - - Review the Windows time service configuration. +Review the permissions on the Domain Controllers OU. -Open an elevated "Command Prompt" (run as administrator). +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Enter "W32tm /query /configuration". +Select "Advanced Features" in the "View" menu if not previously selected. -Domain-joined systems (excluding the domain controller with the PDC emulator role): +Select the "Domain Controllers" OU (folder in folder icon). -If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. +Right-click and select "Properties". -Other systems: +Select the "Security" tab. -If systems are configured with a "Type" of "NTP", including standalone systems and the domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. +If the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding. -To determine the domain controller with the PDC Emulator role: +The default permissions listed below satisfy this requirement. -Open "PowerShell". +Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions and are not a finding. -Enter "Get-ADDomain | FT PDCEmulator". - - - <VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code 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> - - False - False - - Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. +The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "View" or "Edit" button. -If system files are not monitored for unauthorized changes, this is a finding. +Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement. -A properly configured HBSS Policy Auditor 5.2 or later File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. The Asset module within HBSS does not meet this requirement. - - - <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 account. +CREATOR OWNER - Special permissions -Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to not access the Internet or use applications such as email. +SELF - Special permissions -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. +Authenticated Users - Read, Special permissions -Whitelisting can be used to enforce the policy to ensure compliance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. +The special permissions for Authenticated Users are Read types. -If it does not, this is a finding. +If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. -The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. - - - <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> - - False - False - - If no accounts are members of the Backup Operators group, this is NA. +SYSTEM - Full Control -Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. +Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions -If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding. +Enterprise Admins - Full Control + +Key Admins - Special permissions + +Enterprise Key Admins - Special permissions + +Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions + +Pre-Windows 2000 Compatible Access - Special permissions + +The Special permissions for Pre-Windows 2000 Compatible Access are Read types. + +If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding. + +ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions - - <VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account passwords.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93121 False - Determine if manually managed application/service accounts exist. If none exist, this is NA. + This applies to domain controllers. It is NA for other systems. -If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. +Review the auditing configuration for all Group Policy objects. -Identify manually managed application/service accounts. +Open "Group Policy Management" (available from various menus or run "gpmc.msc"). -To determine the date a password was last changed: +Navigate to "Group Policy Objects" in the domain being reviewed (Forest >> Domains >> Domain). -Domain controllers: +For each Group Policy object: -Open "PowerShell". +Select the Group Policy object item in the left pane. -Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. +Select the "Delegation" tab in the right pane. -If the "PasswordLastSet" date is more than one year old, this is a finding. +Select the "Advanced" button. +Select the "Advanced" button again and then the "Auditing" tab. -Member servers and standalone systems: +If the audit settings for any Group Policy object are not at least as inclusive as those below, this is a finding: -Open "Command Prompt". +Type - Fail +Principal - Everyone +Access - Full Control +Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects -Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. +The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. -If the "Password Last Set" date is more than one year old, this is a finding. +Type - Success +Principal - Everyone +Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected) +Inherited from - Parent Object +Applies to - Descendant groupPolicyContainer objects + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions) +Inherited from - Parent Object +Applies to - Descendant Organization Unit Objects - - <VulnDiscussion>The krbtgt account acts as a service account for the Kerberos Key Distribution Center (KDC) service. The account and password are created when a domain is created and the password is typically not changed. If the krbtgt account is compromised, attackers can create valid Kerberos Ticket Granting Tickets (TGT). + + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. -The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and the amount of time equal to or greater than the maximum Kerberos ticket lifetime, and changing again reduces the risk of issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93123 False - This requirement is applicable to domain controllers; it is NA for other systems. + This applies to domain controllers. It is NA for other systems. -Open "Windows PowerShell". +Review the auditing configuration for the Domain object. -Enter "Get-ADUser krbtgt -Property PasswordLastSet". +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -If the "PasswordLastSet" date is more than 180 days old, this is a finding. - - - <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - For standalone systems, this is NA. +Ensure "Advanced Features" is selected in the "View" menu. -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. +Select the domain being reviewed in the left pane. -Verify the system has a TPM and it is ready for use. +Right-click the domain name and select "Properties". -Run "tpm.msc". +Select the "Security" tab. -Review the sections in the center pane. +Select the "Advanced" button and then the "Auditing" tab. -"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". +If the audit settings on the Domain object are not at least as inclusive as those below, this is a finding: -TPM Manufacturer Information - Specific Version = 2.0 or 1.2 +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only -If a TPM is not found or is not ready for use, this is a finding. - - - <VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - If FTP is not installed on the system, this is NA. +Two instances with the following summary information will be listed: -Open "Internet Information Services (IIS) Manager". +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - None +Applies to - Special -Select the server. +Type - Success +Principal - Domain Users +Access - All extended rights +Inherited from - None +Applies to - This object only -Double-click "FTP Authentication". +Type - Success +Principal - Administrators +Access - All extended rights +Inherited from - None +Applies to - This object only -If the "Anonymous Authentication" status is "Enabled", this is a finding. +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner) - - <VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93125 False - If FTP is not installed on the system, this is NA. + This applies to domain controllers. It is NA for other systems. -Open "Internet Information Services (IIS) Manager". +Review the auditing configuration for Infrastructure object. -Select "Sites" under the server name. +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -For any sites with a Binding that lists FTP, right-click the site and select "Explore". +Ensure "Advanced Features" is selected in the "View" menu. -If the site is not defined to a specific folder for shared FTP resources, this is a finding. +Select the domain being reviewed in the left pane. -If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding. - - - <VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must run in "UEFI" mode. +Right-click the "Infrastructure" object in the right pane and select "Properties". -Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". +Select the "Security" tab. -Run "System Information". +Select the "Advanced" button and then the "Auditing" tab. -Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding. - - - <VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must have Secure Boot enabled. +If the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding: -Run "System Information". +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None -Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -On server core installations, run the following PowerShell command: +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master) -Confirm-SecureBootUEFI +Two instances with the following summary information will be listed: -If a value of "True" is not returned, this is a finding. +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) - - <VulnDiscussion>To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. + +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93127 False This applies to domain controllers. It is NA for other systems. -Open "Command Prompt" (not elevated). +Review the auditing configuration for the Domain Controller OU object. -Run "ldp.exe". +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -From the "Connection menu", select "Bind". +Ensure "Advanced Features" is selected in the "View" menu. -Clear the User, Password, and Domain fields. +Select the "Domain Controllers OU" under the domain being reviewed in the left pane. -Select "Simple bind" for the Bind type and click "OK". +Right-click the "Domain Controllers OU" object and select "Properties". -Confirmation of anonymous access will be displayed at the end: +Select the "Security" tab. -res = ldap_simple_bind_s -Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON' +Select the "Advanced" button and then the "Auditing" tab. -From the "Browse" menu, select "Search". - -In the Search dialog, enter the DN of the domain naming context (generally something like "dc=disaost,dc=mil") in the Base DN field. +If the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding: -Clear the Attributes field and select "Run". +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object and all descendant objects -Error messages should display related to Bind and user not authenticated. +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding. +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Permissions: all create, delete and modify permissions) -The following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access. +Type - Success +Principal - Everyone +Access - Write all properties +Inherited from - None +Applies to - This object and all descendant objects -Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. +Two instances with the following summary information will be listed: -Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address. +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objects - - <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> - - False - False - - Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account. + + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. -If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding. - - - <VulnDiscussion>Using a whitelist provides a configuration management method to allow the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. -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> +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93129 False - This is applicable to unclassified systems. For other systems, this is NA. + This applies to domain controllers. It is NA for other systems. -Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. +Review the auditing configuration for the "AdminSDHolder" object. -If an application whitelisting program is not in use on the system, this is a finding. +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Configuration of whitelisting applications will vary by the program. +Ensure "Advanced Features" is selected in the "View" menu. -AppLocker is a whitelisting application built into Windows Server. A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules. +Select "System" under the domain being reviewed in the left pane. -If AppLocker is used, perform the following to view the configuration of AppLocker: +Right-click the "AdminSDHolder" object in the right pane and select "Properties". -Open "PowerShell". +Select the "Security" tab. -If the AppLocker PowerShell module has not been imported previously, execute the following first: +Select the "Advanced" button and then the "Auditing" tab. -Import-Module AppLocker +If the audit settings on the "AdminSDHolder" object are not at least as inclusive as those below, this is a finding: -Execute the following command, substituting [c:\temp\file.xml] with a location and file name appropriate for the system: +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None +Applies to - This object only -Get-AppLockerPolicy -Effective -XML > c:\temp\file.xml +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -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. +Type - Success +Principal - Everyone +Access - Special +Inherited from - None +Applies to - This object only +(Access - Special = Write all properties, Modify permissions, Modify owner) -Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: +Two instances with the following summary information will be listed: -https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) +Applies to - Descendant Organizational Unit objects - - <VulnDiscussion>Executing application servers on the same host machine with a directory server may substantially weaken the security of the directory server. Web or database server applications usually require the addition of many programs and accounts, increasing the attack surface of the computer. + + <VulnDiscussion>When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. -Some applications require the addition of privileged accounts, providing potential sources of compromise. Some applications (such as Microsoft Exchange) may require the use of network ports or services conflicting with the directory server. In this case, non-standard ports might be selected, and this could interfere with intrusion detection or prevention services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder. + +Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93131 False - This applies to domain controllers, it is NA for other systems. + This applies to domain controllers. It is NA for other systems. -Review the installed roles the domain controller is supporting. +Review the auditing configuration for the "RID Manager$" object. -Start "Server Manager". +Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc"). -Select "AD DS" in the left pane and the server name under "Servers" to the right. +Ensure "Advanced Features" is selected in the "View" menu. -Select "Add (or Remove) Roles and Features" from "Tasks" in the "Roles and Features" section. (Cancel before any changes are made.) +Select "System" under the domain being reviewed in the left pane. -Determine if any additional server roles are installed. A basic domain controller setup will include the following: +Right-click the "RID Manager$" object in the right pane and select "Properties". -- Active Directory Domain Services -- DNS Server -- File and Storage Services +Select the "Security" tab. -If any roles not requiring installation on a domain controller are installed, this is a finding. +Select the "Advanced" button and then the "Auditing" tab. -A Domain Name System (DNS) server integrated with the directory server (e.g., AD-integrated DNS) is an acceptable application. However, the DNS server must comply with the DNS STIG security requirements. +If the audit settings on the "RID Manager$" object are not at least as inclusive as those below, this is a finding: -Run "Programs and Features". +Type - Fail +Principal - Everyone +Access - Full Control +Inherited from - None -Review installed applications. +The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default. -If any applications are installed that are not required for the domain controller, this is a finding. +Type - Success +Principal - Everyone +Access - Special +Inherited from - None + (Access - Special = Write all properties, All extended rights, Change RID master) + +Two instances with the following summary information will be listed: + +Type - Success +Principal - Everyone +Access - (blank) +Inherited from - (CN of domain) - - <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. 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> + + <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93183 False - Review the password required status for enabled user accounts. - -Open "PowerShell". - -Domain Controllers: - -Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". - -Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). - -If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. - -Member servers and standalone systems: - -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. - -Exclude disabled accounts (e.g., DefaultAccount, Guest). + Determine if a process to back up log data to a different system or media than the system being audited has been implemented. -If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. +If it has not, this is a finding. - - <VulnDiscussion>Smart cards such as the CAC support a two-factor authentication technique. This provides a higher level of trust in the asserted identity than use of the username and password for authentication. - -Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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> False + V-93187 False - This applies to domain controllers. It is NA for other systems. - -Open "PowerShell". - -Enter the following: + Review the Windows time service configuration. -"Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name" -("DistinguishedName" may be substituted for "Name" for more detailed output.) +Open an elevated "Command Prompt" (run as administrator). -If any user accounts, including administrators, are listed, this is a finding. +Enter "W32tm /query /configuration". +Domain-joined systems (excluding the domain controller with the PDC emulator role): -Alternately: +If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding. -To view sample accounts in "Active Directory Users and Computers" (available from various menus or run "dsa.msc"): +Other systems: -Select the Organizational Unit (OU) where the user accounts are located. (By default, this is the Users node; however, accounts may be under other organization-defined OUs.) +If systems are configured with a "Type" of "NTP", including standalone systems and the domain controller with the PDC Emulator role, and do not have a DoD time server defined for "NTPServer", this is a finding. -Right-click the sample user account and select "Properties". +To determine the domain controller with the PDC Emulator role: -Select the "Account" tab. +Open "PowerShell". -If any user accounts, including administrators, do not have "Smart card is required for interactive logon" checked in the "Account Options" area, this is a finding. +Enter "Get-ADDomain | FT PDCEmulator". - - <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></IAControls> + + <VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code 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> False + V-93203 False - Determine if manually managed application/service accounts exist. If none exist, this is NA. + Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. -Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. +If system files are not monitored for unauthorized changes, this is a finding. -If such a policy does not exist or has not been implemented, this is a finding. +A properly configured and approved DoD HBSS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. - - <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. + + <VulnDiscussion>Using a whitelist provides a configuration management method to allow the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. -Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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> False + V-93379 False - Review the password last set date for the built-in Administrator account. - -Domain controllers: + This is applicable to unclassified systems. For other systems, this is NA. -Open "PowerShell". +Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs. -Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". +If an application whitelisting program is not in use on the system, this is a finding. -If the "PasswordLastSet" date is greater than "60" days old, this is a finding. +Configuration of whitelisting applications will vary by the program. -Member servers and standalone systems: +AppLocker is a whitelisting application built into Windows Server. A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules. -Open "Command Prompt". +If AppLocker is used, perform the following to view the configuration of AppLocker: -Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. +Open "PowerShell". -(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) +If the AppLocker PowerShell module has not been imported previously, execute the following first: -If the "PasswordLastSet" date is greater than "60" days old, this is a finding. - - - <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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> - - False - False - - Review the password never expires status for enabled user accounts. +Import-Module AppLocker -Open "PowerShell". +Execute the following command, substituting [c:\temp\file.xml] with a location and file name appropriate for the system: -Domain Controllers: +Get-AppLockerPolicy -Effective -XML > c:\temp\file.xml -Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". +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. -Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. +Implementation guidance for AppLocker is available in the NSA paper "Application Whitelisting using Microsoft AppLocker" at the following link: -If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm + + + <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. -Member servers and standalone systems: +Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. +Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. -Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). +Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93543 + False + + If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. -If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding. +If protection methods have not been implemented, this is a finding. - - <VulnDiscussion>Domain controllers are part of the chain of trust for PKI authentications. Without the appropriate certificate, the authenticity of the domain controller cannot be verified. Domain controllers must have a server certificate to establish authenticity as part of PKI authentications in the domain.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93185 False - This applies to domain controllers. It is NA for other systems. - -Run "MMC". - -Select "Add/Remove Snap-in" from the "File" menu. - -Select "Certificates" in the left pane and click the "Add >" button. + Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. -Select "Computer Account" and click "Next". +If they are not, this is a finding. + + + <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> + + False + V-93369 + False + + Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account. -Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". +If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding. + + + <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 account. -Click "OK". +Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to not access the Internet or use applications such as email. -Select and expand the Certificates (Local Computer) entry in the left pane. +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. -Select and expand the Personal entry in the left pane. +Whitelisting can be used to enforce the policy to ensure compliance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93205 + False + + Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. -Select the Certificates entry in the left pane. +If it does not, this is a finding. -If no certificate for the domain controller exists in the right pane, this is a finding. +The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. - - <VulnDiscussion>A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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> False + V-93207 False - This applies to domain controllers. It is NA for other systems. - -Run "MMC". - -Select "Add/Remove Snap-in" from the "File" menu. + If no accounts are members of the Backup Operators group, this is NA. -Select "Certificates" in the left pane and click the "Add >" button. +Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks. -Select "Computer Account" and click "Next". +If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding. + + + <VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account passwords.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93209 + False + + Determine if manually managed application/service accounts exist. If none exist, this is NA. -Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish". +If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding. -Click "OK". +Identify manually managed application/service accounts. -Select and expand the Certificates (Local Computer) entry in the left pane. +To determine the date a password was last changed: -Select and expand the Personal entry in the left pane. +Domain controllers: -Select the Certificates entry in the left pane. +Open "PowerShell". -In the right pane, examine the "Issued By" field for the certificate to determine the issuing CA. +Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account. -If the "Issued By" field of the PKI certificate being used by the domain controller does not indicate the issuing CA is part of the DoD PKI or an approved ECA, this is a finding. +If the "PasswordLastSet" date is more than one year old, this is a finding. -If the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding. -There are multiple sources from which lists of valid DoD CAs and approved ECAs can be obtained: +Member servers and standalone systems: -The Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil. +Open "Command Prompt". -DoD Public Key Enablement (PKE) Engineering Support maintains the InstallRoot utility to manage DoD supported root certificates on Windows computers, which includes a list of authorized CAs. The utility package can be downloaded from the PKI and PKE Tools page on IASE: +Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account. -http://iase.disa.mil/pki-pke/function_pages/tools.html +If the "Password Last Set" date is more than one year old, this is a finding. - - <VulnDiscussion>The failure to terminate inactive network connections increases the risk of a successful attack on the directory server. The longer an established session is in progress, the more time an attacker has to hijack the session, implement a means to passively intercept data, or compromise any protections on client access. For example, if an attacker gains control of a client computer, an existing (already authenticated) session with the directory server could allow access to the directory. The lack of confidentiality protection in LDAP-based sessions increases exposure to this vulnerability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93213 False - This applies to domain controllers. It is NA for other systems. - -Open an elevated "Command Prompt" (run as administrator). - -Enter "ntdsutil". + For standalone systems, this is NA. -At the "ntdsutil:" prompt, enter "LDAP policies". +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. -At the "ldap policy:" prompt, enter "connections". +Verify the system has a TPM and it is ready for use. -At the "server connections:" prompt, enter "connect to server [host-name]" -(where [host-name] is the computer name of the domain controller). +Run "tpm.msc". -At the "server connections:" prompt, enter "q". +Review the sections in the center pane. -At the "ldap policy:" prompt, enter "show values". +"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken". -If the value for MaxConnIdleTime is greater than "300" (5 minutes) or is not specified, this is a finding. +TPM Manufacturer Information - Specific Version = 2.0 or 1.2 -Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit. +If a TPM is not found or is not ready for use, this is a finding. + + + <VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. -Alternately, Dsquery can be used to display MaxConnIdleTime: +Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93223 + False + + If FTP is not installed on the system, this is NA. -Open "Command Prompt (Admin)". -Enter the following command (on a single line). +Open "Internet Information Services (IIS) Manager". -dsquery * "cn=Default Query Policy,cn=Query-Policies,cn=Directory Service, cn=Windows NT,cn=Services,cn=Configuration,dc=[forest-name]" -attr LDAPAdminLimits +Select the server. -The quotes are required and dc=[forest-name] is the fully qualified LDAP name of the domain being reviewed (e.g., dc=disaost,dc=mil). +Double-click "FTP Authentication". -If the results do not specify a "MaxConnIdleTime" or it has a value greater than "300" (5 minutes), this is a finding. +If the "Anonymous Authentication" status is "Enabled", this is a finding. - - <VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. - -Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). - -Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93225 False - Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. + If FTP is not installed on the system, this is NA. -If they do not, this is a finding. +Open "Internet Information Services (IIS) Manager". + +Select "Sites" under the server name. + +For any sites with a Binding that lists FTP, right-click the site and select "Explore". + +If the site is not defined to a specific folder for shared FTP resources, this is a finding. + +If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding. - - <VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93229 False - If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) + Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must run in "UEFI" mode. -Run "Computer Management". +Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS". -Navigate to System Tools >> Shared Folders >> Shares. +Run "System Information". -Right-click any non-system-created shares. +Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding. + + + <VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93231 + False + + Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must have Secure Boot enabled. -Select "Properties". +Run "System Information". -Select the "Share Permissions" tab. +Under "System Summary", if "Secure Boot State" does not display "On", this is a finding. -If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. +On server core installations, run the following PowerShell command: -Select the "Security" tab. +Confirm-SecureBootUEFI -If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. +If a value of "True" is not returned, this is a finding. - - <VulnDiscussion>When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. - -The directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93271 False This applies to domain controllers. It is NA for other systems. -Run "Regedit". +Open "Command Prompt" (not elevated). -Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters". +Run "ldp.exe". -Note the directory locations in the values for "DSA Database file". +From the "Connection menu", select "Bind". -Open "Command Prompt". +Clear the User, Password, and Domain fields. -Enter "net share". +Select "Simple bind" for the Bind type and click "OK". -Note the logical drive(s) or file system partition for any organization-created data shares. +Confirmation of anonymous access will be displayed at the end: -Ignore system shares (e.g., NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) should not be ignored. +res = ldap_simple_bind_s +Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON' -If user shares are located on the same logical partition as the directory server data files, this is a finding. - - - <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. +From the "Browse" menu, select "Search". -Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. +In the Search dialog, enter the DN of the domain naming context (generally something like "dc=disaost,dc=mil") in the Base DN field. -Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. +Clear the Attributes field and select "Run". -Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Error messages should display related to Bind and user not authenticated. + +If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding. + +The following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access. + +Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. + +Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address. + + + <VulnDiscussion>The krbtgt account acts as a service account for the Kerberos Key Distribution Center (KDC) service. The account and password are created when a domain is created and the password is typically not changed. If the krbtgt account is compromised, attackers can create valid Kerberos Ticket Granting Tickets (TGT). + +The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and the amount of time equal to or greater than the maximum Kerberos ticket lifetime, and changing again reduces the risk of issues.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93211 False - If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. + This requirement is applicable to domain controllers; it is NA for other systems. -If protection methods have not been implemented, this is a finding. +Open "Windows PowerShell". + +Enter "Get-ADUser krbtgt -Property PasswordLastSet". + +If the "PasswordLastSet" date is more than 180 days old, this is a finding. - + <VulnDiscussion>Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be established for some reason.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93227 False Review the effective User Rights setting in Local Group Policy Editor. @@ -2829,7 +2937,237 @@ If any unresolved SIDs exist and are not for currently valid accounts or groups, - + + + + + + Eventlog + False + + + FullControl + + + + + SYSTEM + False + + + FullControl + + + + + Administrators + False + + + FullControl + + + <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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + True + False + V-93189 + False + + %windir%\SYSTEM32\WINEVT\LOGS\Application.evtx + Navigate to the Application event log file. + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. + +If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + + + Eventlog + False + + + FullControl + + + + + SYSTEM + False + + + FullControl + + + + + Administrators + False + + + FullControl + + + <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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + True + False + V-93191 + False + + %windir%\SYSTEM32\WINEVT\LOGS\Security.evtx + Navigate to the Security event log file. + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. + +If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + + + Eventlog + False + + + FullControl + + + + + SYSTEM + False + + + FullControl + + + + + Administrators + False + + + FullControl + + + <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. + +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + True + False + V-93193 + False + + %windir%\SYSTEM32\WINEVT\LOGS\System.evtx + Navigate to the System event log file. + +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. + +If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: + +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control + + + + + + + TrustedInstaller + False + + + FullControl + + + + + Administrators + False + + + ReadAndExecute + + + + + SYSTEM + False + + + ReadAndExecute + + + + + Users + False + + + ReadAndExecute + + + + + ALL APPLICATION PACKAGES + False + + + ReadAndExecute + + + + + ALL RESTRICTED APPLICATION PACKAGES + False + + + ReadAndExecute + + + <VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. + +Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. + +Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + True + False + V-93195 + False + + %windir%\SYSTEM32\eventvwr.exe + Navigate to "%SystemRoot%\System32". + +View the permissions on "Eventvwr.exe". + +If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. + +The default permissions below satisfy this requirement: + +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute + + @@ -2888,6 +3226,7 @@ Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPO True False + V-93019 False %SystemDrive%\ @@ -2936,7 +3275,7 @@ BUILTIN\Users:(CI)(IO)(WD) CREATOR OWNER:(OI)(CI)(IO)(F) Successfully processed 1 files; Failed processing 0 files - + @@ -3019,6 +3358,7 @@ Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPO True False + V-93021.a False %ProgramFiles(x86)% @@ -3065,7 +3405,7 @@ APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(G Successfully processed 1 files; Failed processing 0 files - + @@ -3148,6 +3488,7 @@ Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPO True False + V-93021.b False %ProgramFiles% @@ -3194,7 +3535,7 @@ APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(G Successfully processed 1 files; Failed processing 0 files - + @@ -3277,6 +3618,7 @@ Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPO True False + V-93023 False %windir% @@ -3335,7 +3677,7 @@ APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) Successfully processed 1 files; Failed processing 0 files - + @@ -3350,6 +3692,7 @@ Successfully processed 1 files; Failed processing 0 files True False + V-93025.a False HKLM:\SECURITY @@ -3371,7 +3714,7 @@ S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4 If the defaults have not been changed, these are not a finding. - + @@ -3418,6 +3761,7 @@ If the defaults have not been changed, these are not a finding. True False + V-93025.b False HKLM:\SOFTWARE @@ -3442,7 +3786,7 @@ S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4 If the defaults have not been changed, these are not a finding. - + @@ -3489,6 +3833,7 @@ If the defaults have not been changed, these are not a finding. True False + V-93025.c False HKLM:\SYSTEM @@ -3513,7 +3858,7 @@ S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4 If the defaults have not been changed, these are not a finding. - + @@ -3570,6 +3915,7 @@ The SYSVOL directory contains public files (to the domain) such as policies and True False + V-93031 False %windir%\sysvol @@ -3605,263 +3951,41 @@ CREATOR OWNER:(OI)(CI)(IO)(F) (RX) - Read & execute -Run "icacls /help" to view definitions of other permission codes. - -Alternately, open "File Explorer". - -Navigate to \Windows\SYSVOL (or the directory noted previously if different). - -Right-click the directory and select properties. - -Select the "Security" tab and click "Advanced". - -Default permissions: - -C:\Windows\SYSVOL -Type - "Allow" for all -Inherited from - "None" for all - -Principal - Access - Applies to - -Authenticated Users - Read & execute- This folder, subfolder, and files -Server Operators - Read & execute- This folder, subfolder, and files -Administrators - Special - This folder only (Special = Basic Permissions: all selected except Full control) -CREATOR OWNER - Full control - Subfolders and files only -Administrators - Full control - Subfolders and files only -SYSTEM - Full control - This folder, subfolders, and files - - - - - - - Eventlog - False - - - FullControl - - - - - SYSTEM - False - - - FullControl - - - - - Administrators - False - - - FullControl - - - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - True - False - False - - %windir%\SYSTEM32\WINEVT\LOGS\Application.evtx - Navigate to the Application event log file. - -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. - -If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: - -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control - - - - - - - Eventlog - False - - - FullControl - - - - - SYSTEM - False - - - FullControl - - - - - Administrators - False - - - FullControl - - - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - True - False - False - - %windir%\SYSTEM32\WINEVT\LOGS\Security.evtx - Navigate to the Security event log file. - -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. - -If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: - -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control +Run "icacls /help" to view definitions of other permission codes. - - - - - - Eventlog - False - - - FullControl - - - - - SYSTEM - False - - - FullControl - - - - - Administrators - False - - - FullControl - - - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + + + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - True False + V-93565 + BottomUp + System + ASLR + true False - %windir%\SYSTEM32\WINEVT\LOGS\System.evtx - Navigate to the System event log file. - -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. - -If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: - -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control - - - - - - - TrustedInstaller - False - - - FullControl - - - - - Administrators - False - - - ReadAndExecute - - - - - SYSTEM - False - - - ReadAndExecute - - - - - Users - False - - - ReadAndExecute - - - - - ALL APPLICATION PACKAGES - False - - - ReadAndExecute - - - - - ALL RESTRICTED APPLICATION PACKAGES - False - - - ReadAndExecute - - - <VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. + This is applicable to unclassified systems, for other systems this is NA. -Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". -Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - True - False - False - - %windir%\SYSTEM32\eventvwr.exe - Navigate to "%SystemRoot%\System32". +Run "Windows PowerShell" with elevated privileges (run as administrator). -View the permissions on "Eventvwr.exe". +Enter "Get-ProcessMitigation -System". -If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. +If the status of "ASLR: BottomUp" is "OFF", this is a finding. -The default permissions below satisfy this requirement: +Values that would not be a finding include: -TrustedInstaller - Full Control -Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute +ON +NOTSET (Default configuration) - - - + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Data Execution Prevention (DEP)", are enabled by default at the system level. DEP prevents code from being run from data-only memory pages. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93313 Enable System DEP @@ -3883,10 +4007,11 @@ Values that would not be a finding include: ON NOTSET (Default configuration) - + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Control flow guard (CFG)", are enabled by default at the system level. CFG ensures flow integrity for indirect calls. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93315 Enable System ControlFlowGuard @@ -3908,10 +4033,11 @@ Values that would not be a finding include: ON NOTSET (Default configuration) - + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate exception chains (SEHOP)", are enabled by default at the system level. SEHOP (structured exception handling overwrite protection) ensures the integrity of an exception chain during exception dispatch. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93317 Enable System SEHOP @@ -3933,10 +4059,11 @@ Values that would not be a finding include: ON NOTSET (Default configuration) - + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate heap integrity", are enabled by default at the system level. "Validate heap integrity" terminates a process when heap corruption is detected. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93319 TerminateOnError System Heap @@ -3958,10 +4085,11 @@ Values that would not be a finding include: ON NOTSET (Default configuration) - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.a Enable Acrobat.exe DEP @@ -3970,10 +4098,11 @@ NOTSET (Default configuration) Acrobat.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.b BottomUp Acrobat.exe ASLR @@ -3982,10 +4111,11 @@ NOTSET (Default configuration) Acrobat.exe:ASLR:BottomUp:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.c ForceRelocateImages Acrobat.exe ASLR @@ -3994,10 +4124,11 @@ NOTSET (Default configuration) Acrobat.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.d EnableExportAddressFilter Acrobat.exe Payload @@ -4006,10 +4137,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.e EnableExportAddressFilterPlus Acrobat.exe Payload @@ -4018,10 +4150,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.f EnableImportAddressFilter Acrobat.exe Payload @@ -4030,10 +4163,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.g EnableRopStackPivot Acrobat.exe Payload @@ -4042,10 +4176,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.h EnableRopCallerCheck Acrobat.exe Payload @@ -4054,10 +4189,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.i EnableRopSimExec Acrobat.exe Payload @@ -4066,10 +4202,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.a Enable AcroRd32.exe DEP @@ -4078,10 +4215,11 @@ NOTSET (Default configuration) AcroRd32.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.b BottomUp AcroRd32.exe ASLR @@ -4090,10 +4228,11 @@ NOTSET (Default configuration) AcroRd32.exe:ASLR:BottomUp:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.c ForceRelocateImages AcroRd32.exe ASLR @@ -4102,10 +4241,11 @@ NOTSET (Default configuration) AcroRd32.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.d EnableExportAddressFilter AcroRd32.exe Payload @@ -4114,10 +4254,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.e EnableExportAddressFilterPlus AcroRd32.exe Payload @@ -4126,10 +4267,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.f EnableImportAddressFilter AcroRd32.exe Payload @@ -4138,10 +4280,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.g EnableRopStackPivot AcroRd32.exe Payload @@ -4150,10 +4293,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.h EnableRopCallerCheck AcroRd32.exe Payload @@ -4162,10 +4306,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.i EnableRopSimExec AcroRd32.exe Payload @@ -4174,10 +4319,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93325 Enable chrome.exe DEP @@ -4200,10 +4346,11 @@ Enable: ON The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.a Enable EXCEL.EXE DEP @@ -4212,10 +4359,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.b ForceRelocateImages EXCEL.EXE ASLR @@ -4224,10 +4372,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.c EnableExportAddressFilter EXCEL.EXE Payload @@ -4236,10 +4385,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.d EnableExportAddressFilterPlus EXCEL.EXE Payload @@ -4248,10 +4398,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.e EnableImportAddressFilter EXCEL.EXE Payload @@ -4260,10 +4411,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.f EnableRopStackPivot EXCEL.EXE Payload @@ -4272,10 +4424,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.g EnableRopCallerCheck EXCEL.EXE Payload @@ -4284,10 +4437,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.h EnableRopSimExec EXCEL.EXE Payload @@ -4296,10 +4450,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93329.a Enable firefox.exe DEP @@ -4308,10 +4463,11 @@ The PowerShell command produces a list of mitigations; only those with a require firefox.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93329.b BottomUp firefox.exe ASLR @@ -4320,10 +4476,11 @@ The PowerShell command produces a list of mitigations; only those with a require firefox.exe:ASLR:BottomUp:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93329.c ForceRelocateImages firefox.exe ASLR @@ -4332,10 +4489,11 @@ The PowerShell command produces a list of mitigations; only those with a require firefox.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.a Enable FLTLDR.EXE DEP @@ -4344,10 +4502,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.b BlockRemoteImageLoads FLTLDR.EXE ImageLoad @@ -4356,10 +4515,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:ImageLoad:BlockRemoteImageLoads:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.c EnableExportAddressFilter FLTLDR.EXE Payload @@ -4368,10 +4528,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.d EnableExportAddressFilterPlus FLTLDR.EXE Payload @@ -4380,10 +4541,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.e EnableImportAddressFilter FLTLDR.EXE Payload @@ -4392,10 +4554,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.f EnableRopStackPivot FLTLDR.EXE Payload @@ -4404,10 +4567,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.g EnableRopCallerCheck FLTLDR.EXE Payload @@ -4416,10 +4580,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.h EnableRopSimExec FLTLDR.EXE Payload @@ -4428,10 +4593,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.i DisallowChildProcessCreation FLTLDR.EXE ChildProcess @@ -4440,10 +4606,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Child Process:DisallowChildProcessCreation:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.a Enable GROOVE.EXE DEP @@ -4452,10 +4619,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.b ForceRelocateImages GROOVE.EXE ASLR @@ -4464,10 +4632,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.c BlockRemoteImageLoads GROOVE.EXE ImageLoad @@ -4476,10 +4645,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:ImageLoad:BlockRemoteImageLoads:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.d EnableExportAddressFilter GROOVE.EXE Payload @@ -4488,10 +4658,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.e EnableExportAddressFilterPlus GROOVE.EXE Payload @@ -4500,10 +4671,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.f EnableImportAddressFilter GROOVE.EXE Payload @@ -4512,10 +4684,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.g EnableRopStackPivot GROOVE.EXE Payload @@ -4524,10 +4697,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.h EnableRopCallerCheck GROOVE.EXE Payload @@ -4536,10 +4710,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.i EnableRopSimExec GROOVE.EXE Payload @@ -4548,10 +4723,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.j DisallowChildProcessCreation GROOVE.EXE ChildProcess @@ -4560,10 +4736,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Child Process:DisallowChildProcessCreation:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.a Enable iexplore.exe DEP @@ -4572,10 +4749,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.b BottomUp iexplore.exe ASLR @@ -4584,10 +4762,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:ASLR:BottomUp:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.c ForceRelocateImages iexplore.exe ASLR @@ -4596,10 +4775,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.d EnableExportAddressFilter iexplore.exe Payload @@ -4608,10 +4788,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.e EnableExportAddressFilterPlus iexplore.exe Payload @@ -4620,10 +4801,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.f EnableImportAddressFilter iexplore.exe Payload @@ -4632,10 +4814,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.g EnableRopStackPivot iexplore.exe Payload @@ -4644,10 +4827,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.h EnableRopCallerCheck iexplore.exe Payload @@ -4656,10 +4840,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.i EnableRopSimExec iexplore.exe Payload @@ -4668,10 +4853,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.a Enable INFOPATH.EXE DEP @@ -4680,10 +4866,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.b ForceRelocateImages INFOPATH.EXE ASLR @@ -4692,10 +4879,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.c EnableExportAddressFilter INFOPATH.EXE Payload @@ -4704,10 +4892,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.d EnableExportAddressFilterPlus INFOPATH.EXE Payload @@ -4716,10 +4905,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.e EnableImportAddressFilter INFOPATH.EXE Payload @@ -4728,10 +4918,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.f EnableRopStackPivot INFOPATH.EXE Payload @@ -4740,10 +4931,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.g EnableRopCallerCheck INFOPATH.EXE Payload @@ -4752,10 +4944,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.h EnableRopSimExec INFOPATH.EXE Payload @@ -4764,10 +4957,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.a Enable java.exe DEP @@ -4776,10 +4970,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.b EnableExportAddressFilter java.exe Payload @@ -4788,10 +4983,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.c EnableExportAddressFilterPlus java.exe Payload @@ -4800,10 +4996,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.d EnableImportAddressFilter java.exe Payload @@ -4812,10 +5009,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.e EnableRopStackPivot java.exe Payload @@ -4824,10 +5022,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.f EnableRopCallerCheck java.exe Payload @@ -4836,10 +5035,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.g EnableRopSimExec java.exe Payload @@ -4848,10 +5048,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.h Enable javaw.exe DEP @@ -4860,10 +5061,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.i EnableExportAddressFilter javaw.exe Payload @@ -4872,10 +5074,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.j EnableExportAddressFilterPlus javaw.exe Payload @@ -4884,10 +5087,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.k EnableImportAddressFilter javaw.exe Payload @@ -4896,10 +5100,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.l EnableRopStackPivot javaw.exe Payload @@ -4908,10 +5113,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.m EnableRopCallerCheck javaw.exe Payload @@ -4920,10 +5126,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.n EnableRopSimExec javaw.exe Payload @@ -4932,10 +5139,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.o Enable javaws.exe DEP @@ -4944,10 +5152,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.p EnableExportAddressFilter javaws.exe Payload @@ -4956,10 +5165,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.q EnableExportAddressFilterPlus javaws.exe Payload @@ -4968,10 +5178,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.r EnableImportAddressFilter javaws.exe Payload @@ -4980,10 +5191,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.s EnableRopStackPivot javaws.exe Payload @@ -4992,10 +5204,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.t EnableRopCallerCheck javaws.exe Payload @@ -5004,10 +5217,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.u EnableRopSimExec javaws.exe Payload @@ -5016,10 +5230,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.a Enable lync.exe DEP @@ -5028,10 +5243,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.b ForceRelocateImages lync.exe ASLR @@ -5040,10 +5256,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.c EnableExportAddressFilter lync.exe Payload @@ -5052,10 +5269,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.d EnableExportAddressFilterPlus lync.exe Payload @@ -5064,10 +5282,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.e EnableImportAddressFilter lync.exe Payload @@ -5076,10 +5295,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.f EnableRopStackPivot lync.exe Payload @@ -5088,10 +5308,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.g EnableRopCallerCheck lync.exe Payload @@ -5100,10 +5321,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.h EnableRopSimExec lync.exe Payload @@ -5112,10 +5334,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.a Enable MSACCESS.EXE DEP @@ -5124,10 +5347,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.b ForceRelocateImages MSACCESS.EXE ASLR @@ -5136,10 +5360,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.c EnableExportAddressFilter MSACCESS.EXE Payload @@ -5148,10 +5373,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.d EnableExportAddressFilterPlus MSACCESS.EXE Payload @@ -5160,10 +5386,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.e EnableImportAddressFilter MSACCESS.EXE Payload @@ -5172,10 +5399,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.f EnableRopStackPivot MSACCESS.EXE Payload @@ -5184,10 +5412,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.g EnableRopCallerCheck MSACCESS.EXE Payload @@ -5196,10 +5425,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.h EnableRopSimExec MSACCESS.EXE Payload @@ -5208,10 +5438,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.a Enable MSPUB.EXE DEP @@ -5220,10 +5451,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.b ForceRelocateImages MSPUB.EXE ASLR @@ -5232,10 +5464,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.c EnableExportAddressFilter MSPUB.EXE Payload @@ -5244,10 +5477,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.d EnableExportAddressFilterPlus MSPUB.EXE Payload @@ -5256,10 +5490,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.e EnableImportAddressFilter MSPUB.EXE Payload @@ -5268,10 +5503,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.f EnableRopStackPivot MSPUB.EXE Payload @@ -5280,10 +5516,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.g EnableRopCallerCheck MSPUB.EXE Payload @@ -5292,10 +5529,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.h EnableRopSimExec MSPUB.EXE Payload @@ -5304,10 +5542,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.a Enable OIS.EXE DEP @@ -5316,10 +5555,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.b EnableExportAddressFilter OIS.EXE Payload @@ -5328,10 +5568,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.c EnableExportAddressFilterPlus OIS.EXE Payload @@ -5340,10 +5581,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.d EnableImportAddressFilter OIS.EXE Payload @@ -5352,10 +5594,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.e EnableRopStackPivot OIS.EXE Payload @@ -5364,10 +5607,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.f EnableRopCallerCheck OIS.EXE Payload @@ -5376,10 +5620,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.g EnableRopSimExec OIS.EXE Payload @@ -5388,10 +5633,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.a Enable OneDrive.exe DEP @@ -5400,10 +5646,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.b ForceRelocateImages OneDrive.exe ASLR @@ -5412,10 +5659,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.c BlockRemoteImageLoads OneDrive.exe ImageLoad @@ -5424,10 +5672,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:ImageLoad:BlockRemoteImageLoads:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.d EnableExportAddressFilter OneDrive.exe Payload @@ -5436,10 +5685,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.e EnableExportAddressFilterPlus OneDrive.exe Payload @@ -5448,10 +5698,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.f EnableImportAddressFilter OneDrive.exe Payload @@ -5460,10 +5711,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.g EnableRopStackPivot OneDrive.exe Payload @@ -5472,10 +5724,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.h EnableRopCallerCheck OneDrive.exe Payload @@ -5484,10 +5737,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.i EnableRopSimExec OneDrive.exe Payload @@ -5496,10 +5750,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.a Enable OUTLOOK.EXE DEP @@ -5508,10 +5763,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.b ForceRelocateImages OUTLOOK.EXE ASLR @@ -5520,10 +5776,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.c EnableExportAddressFilter OUTLOOK.EXE Payload @@ -5532,10 +5789,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.d EnableExportAddressFilterPlus OUTLOOK.EXE Payload @@ -5544,10 +5802,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.e EnableImportAddressFilter OUTLOOK.EXE Payload @@ -5556,10 +5815,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.f EnableRopStackPivot OUTLOOK.EXE Payload @@ -5568,10 +5828,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.g EnableRopCallerCheck OUTLOOK.EXE Payload @@ -5580,10 +5841,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.h EnableRopSimExec OUTLOOK.EXE Payload @@ -5592,10 +5854,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.a Enable plugin-container.exe DEP @@ -5604,10 +5867,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.b EnableExportAddressFilter plugin-container.exe Payload @@ -5616,10 +5880,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.c EnableExportAddressFilterPlus plugin-container.exe Payload @@ -5628,10 +5893,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.d EnableImportAddressFilter plugin-container.exe Payload @@ -5640,10 +5906,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.e EnableRopStackPivot plugin-container.exe Payload @@ -5652,10 +5919,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.f EnableRopCallerCheck plugin-container.exe Payload @@ -5664,10 +5932,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.g EnableRopSimExec plugin-container.exe Payload @@ -5676,10 +5945,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.a Enable POWERPNT.EXE DEP @@ -5688,10 +5958,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.b ForceRelocateImages POWERPNT.EXE ASLR @@ -5700,10 +5971,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.c EnableExportAddressFilter POWERPNT.EXE Payload @@ -5712,10 +5984,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.d EnableExportAddressFilterPlus POWERPNT.EXE Payload @@ -5724,10 +5997,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.e EnableImportAddressFilter POWERPNT.EXE Payload @@ -5736,10 +6010,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.f EnableRopStackPivot POWERPNT.EXE Payload @@ -5748,10 +6023,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.g EnableRopCallerCheck POWERPNT.EXE Payload @@ -5760,10 +6036,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.h EnableRopSimExec POWERPNT.EXE Payload @@ -5772,10 +6049,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.a Enable PPTVIEW.EXE DEP @@ -5784,10 +6062,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.b ForceRelocateImages PPTVIEW.EXE ASLR @@ -5796,10 +6075,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.c EnableExportAddressFilter PPTVIEW.EXE Payload @@ -5808,10 +6088,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.d EnableExportAddressFilterPlus PPTVIEW.EXE Payload @@ -5820,10 +6101,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.e EnableImportAddressFilter PPTVIEW.EXE Payload @@ -5832,10 +6114,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.f EnableRopStackPivot PPTVIEW.EXE Payload @@ -5844,10 +6127,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.g EnableRopCallerCheck PPTVIEW.EXE Payload @@ -5856,10 +6140,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.h EnableRopSimExec PPTVIEW.EXE Payload @@ -5868,10 +6153,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.a Enable VISIO.EXE DEP @@ -5880,10 +6166,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.b ForceRelocateImages VISIO.EXE ASLR @@ -5892,10 +6179,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.c EnableExportAddressFilter VISIO.EXE Payload @@ -5904,10 +6192,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.d EnableExportAddressFilterPlus VISIO.EXE Payload @@ -5916,10 +6205,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.e EnableImportAddressFilter VISIO.EXE Payload @@ -5928,10 +6218,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.f EnableRopStackPivot VISIO.EXE Payload @@ -5940,10 +6231,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.g EnableRopCallerCheck VISIO.EXE Payload @@ -5952,10 +6244,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.h EnableRopSimExec VISIO.EXE Payload @@ -5964,10 +6257,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.a Enable VPREVIEW.EXE DEP @@ -5976,10 +6270,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.b ForceRelocateImages VPREVIEW.EXE ASLR @@ -5988,10 +6283,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.c EnableExportAddressFilter VPREVIEW.EXE Payload @@ -6000,10 +6296,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.d EnableExportAddressFilterPlus VPREVIEW.EXE Payload @@ -6012,10 +6309,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.e EnableImportAddressFilter VPREVIEW.EXE Payload @@ -6024,10 +6322,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.f EnableRopStackPivot VPREVIEW.EXE Payload @@ -6036,10 +6335,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.g EnableRopCallerCheck VPREVIEW.EXE Payload @@ -6048,10 +6348,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.h EnableRopSimExec VPREVIEW.EXE Payload @@ -6060,10 +6361,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.a Enable WINWORD.EXE DEP @@ -6072,10 +6374,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.b ForceRelocateImages WINWORD.EXE ASLR @@ -6084,10 +6387,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.c EnableExportAddressFilter WINWORD.EXE Payload @@ -6096,10 +6400,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.d EnableExportAddressFilterPlus WINWORD.EXE Payload @@ -6108,10 +6413,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.e EnableImportAddressFilter WINWORD.EXE Payload @@ -6120,10 +6426,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.f EnableRopStackPivot WINWORD.EXE Payload @@ -6132,10 +6439,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.g EnableRopCallerCheck WINWORD.EXE Payload @@ -6144,10 +6452,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.h EnableRopSimExec WINWORD.EXE Payload @@ -6156,10 +6465,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93365.a Enable wmplayer.exe DEP @@ -6168,10 +6478,11 @@ The PowerShell command produces a list of mitigations; only those with a require wmplayer.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93365.b EnableRopStackPivot wmplayer.exe Payload @@ -6180,10 +6491,11 @@ The PowerShell command produces a list of mitigations; only those with a require wmplayer.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93365.c EnableRopCallerCheck wmplayer.exe Payload @@ -6192,10 +6504,11 @@ The PowerShell command produces a list of mitigations; only those with a require wmplayer.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93365.d EnableRopSimExec wmplayer.exe Payload @@ -6204,10 +6517,11 @@ The PowerShell command produces a list of mitigations; only those with a require wmplayer.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.a Enable wordpad.exe DEP @@ -6216,10 +6530,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.b EnableExportAddressFilter wordpad.exe Payload @@ -6228,10 +6543,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.c EnableExportAddressFilterPlus wordpad.exe Payload @@ -6240,10 +6556,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.d EnableImportAddressFilter wordpad.exe Payload @@ -6252,10 +6569,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.e EnableRopStackPivot wordpad.exe Payload @@ -6264,10 +6582,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.f EnableRopCallerCheck wordpad.exe Payload @@ -6276,46 +6595,102 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.g EnableRopSimExec wordpad.exe Payload true False - wordpad.exe:Payload:EnableRopSimExec:ON + wordpad.exe:Payload:EnableRopSimExec:ON + + + + + <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93147 + False + + 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: LegalNoticeText + +Value Type: REG_SZ +Value: See message text below + +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. + 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. + LegalNoticeText + String - - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + Present False - BottomUp - System - ASLR - true - False - - This is applicable to unclassified systems, for other systems this is NA. + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93149 + True + '{0}' -match '^(DoD Notice and Consent Banner|US Department of Defense Warning Statement)$' + If the following registry value does not exist or is not configured as specified, this is a finding: -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Run "Windows PowerShell" with elevated privileges (run as administrator). +Value Name: LegalNoticeCaption -Enter "Get-ProcessMitigation -System". +Value Type: REG_SZ +Value: See message title options below -If the status of "ASLR: BottomUp" is "OFF", this is a finding. +"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. -Values that would not be a finding include: +If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. -ON -NOTSET (Default configuration) +Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required. + + LegalNoticeCaption + String - - - + <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. Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -6323,6 +6698,7 @@ Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPO Present False HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-92961 True '{0}' -le '900' -and '{0}' -gt '0' If the following registry value does not exist or is not configured as specified, this is a finding: @@ -6338,7 +6714,7 @@ Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled)InactivityTimeoutSecs Dword - + <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. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -6346,6 +6722,7 @@ Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion Present False HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-92971 False If the following registry value does not exist or is not configured as specified, this is a finding: @@ -6361,7 +6738,7 @@ Value: 0x00000001 (1) fEncryptRPCTraffic Dword - + <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. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -6369,6 +6746,7 @@ Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion Present False HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-92973 False If the following registry value does not exist or is not configured as specified, this is a finding: @@ -6384,91 +6762,62 @@ Value: 0x00000003 (3) MinEncryptionLevel Dword - - <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + + <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. -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit + V-93173 False 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: LegalNoticeText - -Value Type: REG_SZ -Value: See message text below - -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. - 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. +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ --This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. +Value Name: ProcessCreationIncludeCmdLine_Enabled --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. - LegalNoticeText - String +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + ProcessCreationIncludeCmdLine_Enabled + Dword - - <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + + <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. -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System - True - '{0}' -match '^(DoD Notice and Consent Banner|US Department of Defense Warning Statement)$' + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging + V-93175 + False + 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: LegalNoticeCaption - -Value Type: REG_SZ -Value: See message title options below - -"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. +Registry Path: \SOFTWARE\ Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ -If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. +Value Name: EnableScriptBlockLogging -Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required. - - LegalNoticeCaption - String +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + EnableScriptBlockLogging + Dword - + <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></IAControls> Present False HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93151 False If the following registry value does not exist or is not configured as specified, this is a finding: @@ -6484,1203 +6833,1267 @@ Value: 0x00000001 (1) SCENoApplyLegacyAuditPolicy Dword - - <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. + + <VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. -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> +The cornerstone of the PKI is the private key used to encrypt or digitally sign information. + +If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. + +Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography + V-93493 False 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\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Cryptography\ -Value Name: ProcessCreationIncludeCmdLine_Enabled +Value Name: ForceKeyProtection -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - ProcessCreationIncludeCmdLine_Enabled +Type: REG_DWORD +Value: 0x00000002 (2) + 2 + ForceKeyProtection Dword - - <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 PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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> + + <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 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93467 False 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\PowerShell\ScriptBlockLogging\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: EnableScriptBlockLogging +Value Name: NoLMHash Value Type: REG_DWORD Value: 0x00000001 (1) 1 - EnableScriptBlockLogging + NoLMHash Dword - - <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> + + <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 determine 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\Application - True - '{0}' -ge '32768' - If the system is configured to write events directly to an audit server, this is NA. - -If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + V-93469 + False + + 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\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -Value Name: MaxSize +Value Name: EnablePlainTextPassword -Type: REG_DWORD -Value: 0x00008000 (32768) (or greater) - - MaxSize +Value Type: REG_DWORD +Value: 0x00000000 (0) + 0 + EnablePlainTextPassword Dword - - <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> + + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\Security - True - '{0}' -ge '196608' - If the system is configured to write events directly to an audit server, this is NA. + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters + V-93393 + False + + Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, 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\Windows\EventLog\Security\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ -Value Name: MaxSize +Value Name: SMB1 Type: REG_DWORD -Value: 0x00030000 (196608) (or greater) - - MaxSize +Value: 0x00000000 (0) + 0 + SMB1 Dword - - <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> + + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\System - True - '{0}' -ge '32768' - If the system is configured to write events directly to an audit server, this is NA. + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mrxsmb10 + V-93395 + False + + Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. -If the following registry value does not exist or is not configured as specified, this is a finding: +If the following registry value is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\ +Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ -Value Name: MaxSize +Value Name: Start Type: REG_DWORD -Value: 0x00008000 (32768) (or greater) - - MaxSize +Value: 0x00000004 (4) + 4 + Start Dword - - <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> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization + V-93399 False - If the following registry value does not exist or is not configured as specified, this is a finding: + 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\Installer\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\ -Value Name: EnableUserControl +Value Name: NoLockScreenSlideshow -Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EnableUserControl +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + NoLockScreenSlideshow Dword - - <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></IAControls> + + <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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is enforced.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest + V-93401 False 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\Installer\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\ -Value Name: AlwaysInstallElevated +Value Name: UseLogonCredential -Type: REG_DWORD -Value: 0x00000000 (0) +Type: REG_DWORD +Value: 0x00000000 (0) 0 - AlwaysInstallElevated + UseLogonCredential Dword - - <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></IAControls> + + <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 will prevent 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers + V-93403 False 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\Services\Tcpip6\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ -Value Name: DisableIPSourceRouting +Value Name: DisableWebPnPDownload Type: REG_DWORD -Value: 0x00000002 (2) - 2 - DisableIPSourceRouting +Value: 0x00000001 (1) + 1 + DisableWebPnPDownload Dword - - <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> + + <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 will prevent 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers + V-93405 False 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\Services\Tcpip\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ -Value Name: DisableIPSourceRouting +Value Name: DisableHTTPPrinting -Value Type: REG_DWORD -Value: 0x00000002 (2) - 2 - DisableIPSourceRouting +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + DisableHTTPPrinting Dword - - <VulnDiscussion>Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via the 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> + + <VulnDiscussion>Enabling interaction with the network selection UI allows users to change connections to available networks without signing in to Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + V-93407 False - If the following registry value does not exist or is not configured as specified, this is a finding: + 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: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ -Value Name: EnableICMPRedirect +Value Name: DontDisplayNetworkSelectionUI Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EnableICMPRedirect +Value: 0x00000001 (1) + 1 + DontDisplayNetworkSelectionUI Dword - - <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 will prevent 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AppCompat + V-93409 False 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\LanmanWorkstation\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\ -Value Name: AllowInsecureGuestAuth +Value Name: DisableInventory Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowInsecureGuestAuth +Value: 0x00000001 (1) + 1 + DisableInventory Dword - - <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + V-93411 False - Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ -Value Type: REG_SZ -Value Name: \\*\NETLOGON -Value: RequireMutualAuthentication=1, RequireIntegrity=1 - RequireMutualAuthentication=1, RequireIntegrity=1 - \\*\NETLOGON - String + This is applicable to unclassified systems; for other systems, 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\Windows\System\ + +Value Name: EnableSmartScreen + +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + EnableSmartScreen + Dword - - <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds + V-93413 False - Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ -Value Type: REG_SZ -Value Name: \\*\SYSVOL -Value: RequireMutualAuthentication=1, RequireIntegrity=1 - RequireMutualAuthentication=1, RequireIntegrity=1 - \\*\SYSVOL - String + The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ + +Value Name: AllowBasicAuthInClear + +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) + 0 + AllowBasicAuthInClear + Dword - - <VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search + V-93415 False 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\CredentialsDelegation\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\ -Value Name: AllowProtectedCreds +Value Name: AllowIndexingEncryptedStoresOrItems -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - AllowProtectedCreds +Value Type: REG_DWORD +Value: 0x00000000 (0) + 0 + AllowIndexingEncryptedStoresOrItems Dword - - <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. + +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters + V-93495 False - Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ -Value Type: REG_DWORD -Value Name: EnableVirtualizationBasedSecurity -Value: 0x00000001 (1) - 1 - EnableVirtualizationBasedSecurity - Dword - - - <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Present - False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard - True - '{0}' -match '1|3' - Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ + 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\Kerberos\Parameters\ + +Value Name: SupportedEncryptionTypes + Value Type: REG_DWORD -Value Name: RequirePlatformSecurityFeatures -Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) - - RequirePlatformSecurityFeatures +Value: 0x7ffffff8 (2147483640) + 2147483640 + SupportedEncryptionTypes Dword - - <VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls> + + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\EarlyLaunch - True - '{0}' -match '1|3|8|ShouldBeAbsent' - The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000007 (7)", this is a finding. + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client + V-93503 + False + + 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\Policies\EarlyLaunch\ - -Value Name: DriverLoadPolicy +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -Value Type: REG_DWORD -Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) +Value Name: AllowBasic -Possible values for this setting are: -8 - Good only -1 - Good and unknown -3 - Good, unknown and bad but critical -7 - All (which includes "bad" and would be a finding) - - DriverLoadPolicy +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + AllowBasic Dword - - <VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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> + + <VulnDiscussion>Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks. Disallowing Digest authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2} + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client + V-93505 False 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\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -Value Name: NoGPOListChanges +Value Name: AllowDigest Type: REG_DWORD Value: 0x00000000 (0) 0 - NoGPOListChanges + AllowDigest Dword - - <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> + + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51 + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + V-93507 False 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\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -Value Name: DCSettingIndex +Value Name: AllowBasic Type: REG_DWORD -Value: 0x00000001 (1) - 1 - DCSettingIndex +Value: 0x00000000 (0) + 0 + AllowBasic Dword - - <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51 + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI + V-93517 False 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\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ -Value Name: ACSettingIndex +Value Name: EnumerateAdministrators Type: REG_DWORD -Value: 0x00000001 (1) - 1 - ACSettingIndex +Value: 0x00000000 (0) + 0 + EnumerateAdministrators Dword - - <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection - True - '{0}' -match '0|1' - If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93521 + False + + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\DataCollection\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: AllowTelemetry +Value Name: EnableUIADesktopToggle -Type: REG_DWORD -Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic) - - AllowTelemetry +Value Type: REG_DWORD +Value: 0x00000000 (0) + 0 + EnableUIADesktopToggle Dword - - <VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93523 True - '{0}' -match '0|1|2|99|100' - If the following registry value does not exist or is not configured as specified, this is a finding: + '{0}' -match '1|2' + UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\DeliveryOptimization\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: DODownloadMode +Value Name: ConsentPromptBehaviorAdmin Value Type: REG_DWORD -Value: 0x00000000 (0) - No peering (HTTP Only) -0x00000001 (1) - Peers on same NAT only (LAN) -0x00000002 (2) - Local Network / Private group peering (Group) -0x00000063 (99) - Simple download mode, no peering (Simple) -0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) - -A value of 0x00000003 (3), Internet, is a finding. +Value: 0x00000002 (2) (Prompt for consent on the secure desktop) +0x00000001 (1) (Prompt for credentials on the secure desktop) - DODownloadMode + ConsentPromptBehaviorAdmin Dword - - <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></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93525 False - The default behavior is for File Explorer heap termination on corruption to be enabled. - -If the registry Value Name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -If it exists and is configured with a value of "1", this is a finding. +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\Explorer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: NoHeapTerminationOnCorruption +Value Name: EnableInstallerDetection Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - 0 - NoHeapTerminationOnCorruption +Value: 0x00000001 (1) + 1 + EnableInstallerDetection Dword - - <VulnDiscussion>The shell protocol will limit the set of folders that 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> + + <VulnDiscussion>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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93527 False - The default behavior is for shell protected mode to be turned on for File Explorer. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -If it exists and is configured with a value of "1", this is a finding. +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\Explorer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: PreXPSP2ShellProtocolBehavior +Value Name: EnableSecureUIAPaths Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - 0 - PreXPSP2ShellProtocolBehavior +Value: 0x00000001 (1) + 1 + EnableSecureUIAPaths Dword - - <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> + + <VulnDiscussion>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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93529 False - If the following registry value does not exist or is not configured as specified, this is a finding: + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\Internet Explorer\Feeds\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: DisableEnclosureDownload +Value Name: EnableVirtualization -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DisableEnclosureDownload + EnableVirtualization Dword - - <VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-93533 False - The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. + 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\Installer\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Value Name: SafeForScripting +Value Name: fDisableCdm -Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - 0 - SafeForScripting +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + fDisableCdm Dword - - <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> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93537 False - Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: DisableAutomaticRestartSignOn +Value Name: RestrictAnonymous Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DisableAutomaticRestartSignOn + RestrictAnonymous Dword - - <VulnDiscussion>Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + V-93539 False - This applies to domain controllers. It is NA for other systems. - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Value Name: RefusePasswordChange +Value Name: RestrictNullSessAccess Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - RefusePasswordChange +Value: 0x00000001 (1) + 1 + RestrictNullSessAccess Dword - - <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 does 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> + + <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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa - False - - If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\Application + V-93177 + True + '{0}' -ge '32768' + If the system is configured to write events directly to an audit server, 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: \SYSTEM\CurrentControlSet\Control\Lsa\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Application\ -Value Name: LimitBlankPasswordUse +Value Name: MaxSize -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - LimitBlankPasswordUse +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater) + + MaxSize Dword - - <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 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> + + <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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\Security + V-93179 True - '{0}' -le '30' -and '{0}' -gt '0' - This is the default configuration for this setting (30 days). + '{0}' -ge '196608' + If the system is configured to write events directly to an audit server, 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: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\ -Value Name: MaximumPasswordAge +Value Name: MaxSize -Value Type: REG_DWORD -Value: 0x0000001e (30) (or less, but not 0) +Type: REG_DWORD +Value: 0x00030000 (196608) (or greater) - MaximumPasswordAge + MaxSize Dword - - <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> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\System + V-93181 True - '{0}' -match '1|2' - If the following registry value does not exist or is not configured as specified, this is a finding: + '{0}' -ge '32768' + If the system is configured to write events directly to an audit server, this is NA. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ +If the following registry value does not exist or is not configured as specified, this is a finding: -Value Name: scremoveoption +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\ -Value Type: REG_SZ -Value: 1 (Lock Workstation) or 2 (Force Logoff) +Value Name: MaxSize -If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO. +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater) - scremoveoption - String + MaxSize + Dword - - <VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + V-93199 False 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\Lsa\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: RestrictAnonymousSAM +Value Name: EnableUserControl -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - RestrictAnonymousSAM +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + EnableUserControl Dword - - <VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + V-93201 False 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\Lsa\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: EveryoneIncludesAnonymous +Value Name: AlwaysInstallElevated -Value Type: REG_DWORD +Type: REG_DWORD Value: 0x00000000 (0) 0 - EveryoneIncludesAnonymous + AlwaysInstallElevated Dword - - <VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls> + + <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon as media is inserted into 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + V-93373 False 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\LSA\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -Value Name: UseMachineId +Value Name: NoAutoplayfornonVolume Type: REG_DWORD Value: 0x00000001 (1) 1 - UseMachineId + NoAutoplayfornonVolume Dword - - <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></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\MSV1_0 + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + V-93375 False 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\LSA\MSV1_0\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ -Value Name: allownullsessionfallback +Value Name: NoAutorun Type: REG_DWORD -Value: 0x00000000 (0) - 0 - allownullsessionfallback +Value: 0x00000001 (1) + 1 + NoAutorun Dword - - <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></IAControls> + + <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon media is inserted into 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. Enabling this policy disables 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\pku2u + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer + V-93377 False 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\LSA\pku2u\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\ -Value Name: AllowOnlineID +Value Name: NoDriveTypeAutoRun Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowOnlineID +Value: 0x000000ff (255) + 255 + NoDriveTypeAutoRun Dword - - <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 standalone 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></IAControls> + + <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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-93425 False 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\Lsa\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Value Name: LmCompatibilityLevel +Value Name: DisablePasswordSaving -Value Type: REG_DWORD -Value: 0x00000005 (5) - 5 - LmCompatibilityLevel +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + DisablePasswordSaving Dword - - <VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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> + + <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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LDAP + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-93427 False 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\Services\LDAP\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Value Name: LDAPClientIntegrity +Value Name: fPromptForPassword -Value Type: REG_DWORD +Type: REG_DWORD Value: 0x00000001 (1) 1 - LDAPClientIntegrity + fPromptForPassword Dword - - <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> + + <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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + V-93429 False 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\Lsa\MSV1_0\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -Value Name: NTLMMinClientSec +Value Name: DisableRunAs -Value Type: REG_DWORD -Value: 0x20080000 (537395200) - 537395200 - NTLMMinClientSec +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + DisableRunAs Dword - - <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> + + <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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93431 False - If the following registry value does not exist or is not configured as specified, this is a finding: + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\Lsa\MSV1_0\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: NTLMMinServerSec +Value Name: FilterAdministratorToken Value Type: REG_DWORD -Value: 0x20080000 (537395200) - 537395200 - NTLMMinServerSec +Value: 0x00000001 (1) + 1 + FilterAdministratorToken Dword - - <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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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> + + <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93433 False - If the following registry value does not exist or is not configured as specified, this is a finding: + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: ProtectionMode +Value Name: ConsentPromptBehaviorUser Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - ProtectionMode +Value: 0x00000000 (0) + 0 + ConsentPromptBehaviorUser Dword - - <VulnDiscussion>Attachments from outside sources may contain malicious code. 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> + + <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93435 False - The default behavior is for Windows to mark file attachments with their zone information. - -If the registry Value Name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000002 (2) (or if the Value Name does not exist)", this is not a finding. + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -If it exists and is configured with a value of "1", this is a finding. +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\Microsoft\Windows\CurrentVersion\Policies\Attachments\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: SaveZoneInformation +Value Name: EnableLUA Value Type: REG_DWORD -Value: 0x00000002 (2) (or if the Value Name does not exist) - 2 - SaveZoneInformation +Value: 0x00000001 (1) + 1 + EnableLUA Dword - - <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon as media is inserted into 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></IAControls> + + <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 the 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93455 False 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\Explorer\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: NoAutoplayfornonVolume +Value Name: DisablePasswordChange -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - NoAutoplayfornonVolume +Value Type: REG_DWORD +Value: 0x00000000 (0) + 0 + DisablePasswordChange Dword - - <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></IAControls> + + <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. + +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client + V-93499 False 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\Explorer\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -Value Name: NoAutorun +Value Name: AllowUnencryptedTraffic Type: REG_DWORD -Value: 0x00000001 (1) - 1 - NoAutorun +Value: 0x00000000 (0) + 0 + AllowUnencryptedTraffic Dword - - <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon media is inserted into 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. Enabling this policy disables 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> + + <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. + +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + V-93501 False 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\Explorer\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -Value Name: NoDriveTypeAutoRun +Value Name: AllowUnencryptedTraffic Type: REG_DWORD -Value: 0x000000ff (255) - 255 - NoDriveTypeAutoRun +Value: 0x00000000 (0) + 0 + AllowUnencryptedTraffic Dword - - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 server's 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netbt\Parameters + V-93541 False - Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\Services\LanmanServer\Parameters\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netbt\Parameters\ -Value Name: SMB1 +Value Name: NoNameReleaseOnDemand -Type: REG_DWORD -Value: 0x00000000 (0) - 0 - SMB1 +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + NoNameReleaseOnDemand Dword - - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mrxsmb10 + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93547 False - Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. - -If the following registry value is not configured as specified, this is a finding: + 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\Services\mrxsmb10\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: Start +Value Name: RequireSignOrSeal -Type: REG_DWORD -Value: 0x00000004 (4) - 4 - Start +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + RequireSignOrSeal Dword - - <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> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93549 False - Verify the registry value below. - -If it does not exist or is not configured as specified, this is a finding. + 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\Personalization\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: NoLockScreenSlideshow +Value Name: SealSecureChannel Value Type: REG_DWORD Value: 0x00000001 (1) 1 - NoLockScreenSlideshow + SealSecureChannel Dword - - <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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is enforced.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93551 False 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\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: UseLogonCredential +Value Name: SignSecureChannel -Type: REG_DWORD -Value: 0x00000000 (0) - 0 - UseLogonCredential +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + SignSecureChannel Dword - - <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 will prevent uncontrolled updates to the system. + + <VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. -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> +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93553 False 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\Printers\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: DisableWebPnPDownload +Value Name: RequireStrongKey -Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_DWORD +Value: 0x00000001 (1) + +This setting may prevent a system from being joined to a domain if not configured consistently between systems. 1 - DisableWebPnPDownload + RequireStrongKey Dword - - <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 will prevent uncontrolled updates to the system. + + <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. -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> +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + V-93555 False 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\Printers\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -Value Name: DisableHTTPPrinting +Value Name: RequireSecuritySignature -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DisableHTTPPrinting + RequireSecuritySignature Dword - - <VulnDiscussion>Enabling interaction with the network selection UI allows users to change connections to available networks without signing in to Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + V-93557 False - Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -Value Name: DontDisplayNetworkSelectionUI +Value Name: EnableSecuritySignature Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DontDisplayNetworkSelectionUI + EnableSecuritySignature Dword - - <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 will prevent uncontrolled updates to the system. + + <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. -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></IAControls> +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AppCompat + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + V-93559 False 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\AppCompat\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Value Name: DisableInventory +Value Name: RequireSecuritySignature -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DisableInventory + RequireSecuritySignature Dword - - <VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + V-93561 False - This is applicable to unclassified systems; for other systems, this is NA. - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Value Name: EnableSmartScreen +Value Name: EnableSecuritySignature Value Type: REG_DWORD Value: 0x00000001 (1) 1 - EnableSmartScreen + EnableSecuritySignature Dword - - <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Data Execution Prevention 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + V-93563 False - The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. + The default behavior is for Data Execution Prevention to be turned on for File Explorer. If the registry value name below does not exist, this is not a finding. @@ -7689,590 +8102,577 @@ If it exists and is configured with a value of "0x00000000 (0) (or if the Value If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -Value Name: AllowBasicAuthInClear +Value Name: NoDataExecutionPrevention Value Type: REG_DWORD Value: 0x00000000 (0) (or if the Value Name does not exist) 0 - AllowBasicAuthInClear + NoDataExecutionPrevention Dword - - <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></IAControls> + + <VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy + V-93511 False 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\Windows Search\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ -Value Name: AllowIndexingEncryptedStoresOrItems +Value Name: Enabled Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowIndexingEncryptedStoresOrItems +Value: 0x00000001 (1) + +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; otherwise. the browser will not be able to connect to a secure site. + 1 + Enabled Dword - - <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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters + V-93233 False 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ -Value Name: DisablePasswordSaving +Value Name: DisableIPSourceRouting Type: REG_DWORD -Value: 0x00000001 (1) - 1 - DisablePasswordSaving +Value: 0x00000002 (2) + 2 + DisableIPSourceRouting Dword - - <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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters + V-93235 False 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ -Value Name: fPromptForPassword +Value Name: DisableIPSourceRouting -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - fPromptForPassword +Value Type: REG_DWORD +Value: 0x00000002 (2) + 2 + DisableIPSourceRouting Dword - - <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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via the 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters + V-93237 False 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\WinRM\Service\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ -Value Name: DisableRunAs +Value Name: EnableICMPRedirect -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - DisableRunAs +Value Type: REG_DWORD +Value: 0x00000000 (0) + 0 + EnableICMPRedirect Dword - - <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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation + V-93239 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation\ -Value Name: FilterAdministratorToken +Value Name: AllowInsecureGuestAuth -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - FilterAdministratorToken +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + AllowInsecureGuestAuth Dword - - <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths + V-93241.a False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: ConsentPromptBehaviorUser - -Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - ConsentPromptBehaviorUser - Dword + Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ +Value Type: REG_SZ +Value Name: \\*\NETLOGON +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + RequireMutualAuthentication=1, RequireIntegrity=1 + \\*\NETLOGON + String - - <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths + V-93241.b False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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: EnableLUA - -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - EnableLUA - Dword + Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ +Value Type: REG_SZ +Value Name: \\*\SYSVOL +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + RequireMutualAuthentication=1, RequireIntegrity=1 + \\*\SYSVOL + String - - <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 the 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> + + <VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation + V-93243 False 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\Services\Netlogon\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ -Value Name: DisablePasswordChange +Value Name: AllowProtectedCreds -Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - DisablePasswordChange +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + AllowProtectedCreds Dword - - <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 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></IAControls> + + <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard + V-93245.a False - 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\Lsa\ - -Value Name: NoLMHash - + Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ Value Type: REG_DWORD +Value Name: EnableVirtualizationBasedSecurity Value: 0x00000001 (1) 1 - NoLMHash + EnableVirtualizationBasedSecurity Dword - - <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 determine 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> + + <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters - False - - 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\Services\LanmanWorkstation\Parameters\ - -Value Name: EnablePlainTextPassword - -Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EnablePlainTextPassword + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard + V-93245.b + True + '{0}' -match '1|3' + Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ +Value Type: REG_DWORD +Value Name: RequirePlatformSecurityFeatures +Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) + + RequirePlatformSecurityFeatures Dword - - <VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. - -The cornerstone of the PKI is the private key used to encrypt or digitally sign information. - -If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. - -Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography - False - - If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\EarlyLaunch + V-93249 + True + '{0}' -match '1|3|8|ShouldBeAbsent' + The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Cryptography\ +If the registry value name below does not exist, this is not a finding. -Value Name: ForceKeyProtection +If it exists and is configured with a value of "0x00000007 (7)", this is a finding. -Type: REG_DWORD -Value: 0x00000002 (2) - 2 - ForceKeyProtection +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ + +Value Name: DriverLoadPolicy + +Value Type: REG_DWORD +Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) + +Possible values for this setting are: +8 - Good only +1 - Good and unknown +3 - Good, unknown and bad but critical +7 - All (which includes "bad" and would be a finding) + + DriverLoadPolicy Dword - - <VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. - -Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2} + V-93251 False 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\Kerberos\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ -Value Name: SupportedEncryptionTypes +Value Name: NoGPOListChanges -Value Type: REG_DWORD -Value: 0x7ffffff8 (2147483640) - 2147483640 - SupportedEncryptionTypes +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + NoGPOListChanges Dword - - <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. - -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51 + V-93253 False 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\WinRM\Client\ +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ -Value Name: AllowUnencryptedTraffic +Value Name: DCSettingIndex Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowUnencryptedTraffic +Value: 0x00000001 (1) + 1 + DCSettingIndex Dword - - <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. - -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51 + V-93255 False 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\WinRM\Service\ +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ -Value Name: AllowUnencryptedTraffic +Value Name: ACSettingIndex Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowUnencryptedTraffic +Value: 0x00000001 (1) + 1 + ACSettingIndex Dword - - <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client - False - + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection + V-93257 + True + '{0}' -match '0|1' 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\WinRM\Client\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DataCollection\ -Value Name: AllowBasic +Value Name: AllowTelemetry Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowBasic +Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic) + + AllowTelemetry Dword - - <VulnDiscussion>Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks. Disallowing Digest authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client - False - + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization + V-93259 + True + '{0}' -match '0|1|2|99|100' 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\WinRM\Client\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\ -Value Name: AllowDigest +Value Name: DODownloadMode -Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowDigest +Value Type: REG_DWORD +Value: 0x00000000 (0) - No peering (HTTP Only) +0x00000001 (1) - Peers on same NAT only (LAN) +0x00000002 (2) - Local Network / Private group peering (Group) +0x00000063 (99) - Simple download mode, no peering (Simple) +0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) + +A value of 0x00000003 (3), Internet, is a finding. + + DODownloadMode Dword - - <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + V-93261 False - If the following registry value does not exist or is not configured as specified, this is a finding: + The default behavior is for File Explorer heap termination on corruption to be enabled. + +If the registry Value Name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -Value Name: AllowBasic +Value Name: NoHeapTerminationOnCorruption -Type: REG_DWORD -Value: 0x00000000 (0) +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) 0 - AllowBasic + NoHeapTerminationOnCorruption Dword - - <VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>The shell protocol will limit the set of folders that 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + V-93263 False - If the following registry value does not exist or is not configured as specified, this is a finding: + The default behavior is for shell protected mode to be turned on for File Explorer. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ -Value Name: Enabled +Value Name: PreXPSP2ShellProtocolBehavior Value Type: REG_DWORD -Value: 0x00000001 (1) - -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; otherwise. the browser will not be able to connect to a secure site. - 1 - Enabled +Value: 0x00000000 (0) (or if the Value Name does not exist) + 0 + PreXPSP2ShellProtocolBehavior Dword - - <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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds + V-93265 False 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\CredUI\ +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ -Value Name: EnumerateAdministrators +Value Name: DisableEnclosureDownload Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EnumerateAdministrators +Value: 0x00000001 (1) + 1 + DisableEnclosureDownload Dword - - <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + V-93267 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -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\ + The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. -Value Name: EnableUIADesktopToggle +If the registry value name below does not exist, this is not a finding. -Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EnableUIADesktopToggle - Dword - - - <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></IAControls> - - Present - False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System - True - '{0}' -match '1|2' - UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). +If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. -If the following registry value does not exist or is not configured as specified, this is a finding: +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: ConsentPromptBehaviorAdmin +Value Name: SafeForScripting Value Type: REG_DWORD -Value: 0x00000002 (2) (Prompt for consent on the secure desktop) -0x00000001 (1) (Prompt for credentials on the secure desktop) - - ConsentPromptBehaviorAdmin +Value: 0x00000000 (0) (or if the Value Name does not exist) + 0 + SafeForScripting Dword - - <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></IAControls> + + <VulnDiscussion>Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93273 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + This applies to domain controllers. It is NA for other systems. 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: EnableInstallerDetection +Value Name: RefusePasswordChange Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - EnableInstallerDetection +Value: 0x00000000 (0) + 0 + RefusePasswordChange Dword - - <VulnDiscussion>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> + + <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 does 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93279 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: EnableSecureUIAPaths +Value Name: LimitBlankPasswordUse Value Type: REG_DWORD Value: 0x00000001 (1) 1 - EnableSecureUIAPaths + LimitBlankPasswordUse Dword - - <VulnDiscussion>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></IAControls> + + <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 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System - False - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93285 + True + '{0}' -le '30' -and '{0}' -gt '0' + This is the default configuration for this setting (30 days). 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: EnableVirtualization +Value Name: MaximumPasswordAge Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - EnableVirtualization +Value: 0x0000001e (30) (or less, but not 0) + + MaximumPasswordAge Dword - - <VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services - False - + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon + V-93287 + True + '{0}' -match '1|2' 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\ +Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ -Value Name: fDisableCdm +Value Name: scremoveoption -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - fDisableCdm - Dword +Value Type: REG_SZ +Value: 1 (Lock Workstation) or 2 (Force Logoff) + +If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO. + + scremoveoption + String - - <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></IAControls> + + <VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls> Present False HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93291 False If the following registry value does not exist or is not configured as specified, this is a finding: @@ -8280,295 +8680,263 @@ Value: 0x00000001 (1) Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: RestrictAnonymous +Value Name: RestrictAnonymousSAM Value Type: REG_DWORD Value: 0x00000001 (1) 1 - RestrictAnonymous + RestrictAnonymousSAM Dword - - <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></IAControls> + + <VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93293 False 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\Services\LanManServer\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: RestrictNullSessAccess +Value Name: EveryoneIncludesAnonymous Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - RestrictNullSessAccess +Value: 0x00000000 (0) + 0 + EveryoneIncludesAnonymous Dword - - <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 server's 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> + + <VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netbt\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA + V-93295 False 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\Services\Netbt\Parameters\ - -Value Name: NoNameReleaseOnDemand - -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - NoNameReleaseOnDemand - Dword - - - <VulnDiscussion>Unsigned network traffic is susceptible to man-in-the-middle attacks, where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. The risk of an attacker pulling this off can be decreased by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPsec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man-in-the-middle attacks extremely difficult. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Present - False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters - False - - This applies to domain controllers. It is NA for other systems. - -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\Services\NTDS\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\ -Value Name: LDAPServerIntegrity +Value Name: UseMachineId -Value Type: REG_DWORD -Value: 0x00000002 (2) - 2 - LDAPServerIntegrity +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + UseMachineId Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\MSV1_0 + V-93297 False 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ -Value Name: RequireSignOrSeal +Value Name: allownullsessionfallback -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - RequireSignOrSeal +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + allownullsessionfallback Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\pku2u + V-93299 False 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\pku2u\ -Value Name: SealSecureChannel +Value Name: AllowOnlineID -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - SealSecureChannel +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + AllowOnlineID Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 standalone 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93301 False 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: SignSecureChannel +Value Name: LmCompatibilityLevel Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - SignSecureChannel - Dword - - - <VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Value: 0x00000005 (5) + 5 + LmCompatibilityLevel + Dword + + + <VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LDAP + V-93303 False 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LDAP\ -Value Name: RequireStrongKey +Value Name: LDAPClientIntegrity Value Type: REG_DWORD -Value: 0x00000001 (1) - -This setting may prevent a system from being joined to a domain if not configured consistently between systems. +Value: 0x00000001 (1) 1 - RequireStrongKey + LDAPClientIntegrity Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 + V-93305 False 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\Services\LanmanWorkstation\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ -Value Name: RequireSecuritySignature +Value Name: NTLMMinClientSec Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - RequireSecuritySignature +Value: 0x20080000 (537395200) + 537395200 + NTLMMinClientSec Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 + V-93307 False 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\Services\LanmanWorkstation\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ -Value Name: EnableSecuritySignature +Value Name: NTLMMinServerSec Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - EnableSecuritySignature +Value: 0x20080000 (537395200) + 537395200 + NTLMMinServerSec Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager + V-93309 False 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\Services\LanManServer\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\ -Value Name: RequireSecuritySignature +Value Name: ProtectionMode Value Type: REG_DWORD Value: 0x00000001 (1) 1 - RequireSecuritySignature + ProtectionMode Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Attachments from outside sources may contain malicious code. 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments + V-93311 False - If the following registry value does not exist or is not configured as specified, this is a finding: + The default behavior is for Windows to mark file attachments with their zone information. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ +If the registry Value Name below does not exist, this is not a finding. -Value Name: EnableSecuritySignature +If it exists and is configured with a value of "0x00000002 (2) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ + +Value Name: SaveZoneInformation Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - EnableSecuritySignature +Value: 0x00000002 (2) (or if the Value Name does not exist) + 2 + SaveZoneInformation Dword - - <VulnDiscussion>Data Execution Prevention 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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93269 False - The default behavior is for Data Execution Prevention to be turned on for File Explorer. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. + 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\Explorer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: NoDataExecutionPrevention +Value Name: DisableAutomaticRestartSignOn Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - 0 - NoDataExecutionPrevention +Value: 0x00000001 (1) + 1 + DisableAutomaticRestartSignOn Dword - + <VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. Organizations must disable the Windows Preview pane and Windows Detail pane.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -8576,6 +8944,7 @@ Organizations must disable the Windows Preview pane and Windows Detail pane.< Present False HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + V-102625.a False Registry Hive: HKEY_CURRENT_USER @@ -8587,7 +8956,7 @@ Value: 1 NoPreviewPane Dword - + <VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. Organizations must disable the Windows Preview pane and Windows Detail pane.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -8595,6 +8964,7 @@ Organizations must disable the Windows Preview pane and Windows Detail pane.< Present False HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + V-102625.b False Registry Hive: HKEY_CURRENT_USER @@ -8608,117 +8978,112 @@ Value: 1 - + DoD Root CA 2 <VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93487.a True location for DoD Root CA 2 certificate is present DoD Root CA 2,8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 - + DoD Root CA 3 <VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93487.b True location for DoD Root CA 3 certificate is present DoD Root CA 3,D73CA91102A2204A36459ED32213B467D7CE97FB D73CA91102A2204A36459ED32213B467D7CE97FB - + DoD Root CA 4 <VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93487.c True location for DoD Root CA 4 certificate is present DoD Root CA 4,B8269F25DBD937ECAFD4C35A9838571723F2D026 B8269F25DBD937ECAFD4C35A9838571723F2D026 - + DoD Root CA 5 <VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93487.d True location for DoD Root CA 5 certificate is present DoD Root CA 5,4ECB5CC3095670454DA1CBD410FC921F46B8564B 4ECB5CC3095670454DA1CBD410FC921F46B8564B - - DoD Interoperability Root CA 1 - <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. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - True - location for DoD Interoperability Root CA 1 certificate is present - DoD Interoperability Root CA 1,22BBE981F0694D246CC1472ED2B021DC8540A22F - 22BBE981F0694D246CC1472ED2B021DC8540A22F - - + DoD Interoperability Root CA 2 <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. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93489.a True location for DoD Interoperability Root CA 2 certificate is present - DoD Interoperability Root CA 2,FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4 - FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4 + DoD Interoperability Root CA 2,AC06108CA348CC03B53795C64BF84403C1DBD341 + AC06108CA348CC03B53795C64BF84403C1DBD341 - - DoD Interoperability Root CA 2 + + DoD Interoperability Root CA 1 <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. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93489.b True - location for DoD Interoperability Root CA 2 certificate is present - DoD Interoperability Root CA 2,FFAD03329B9E527A43EEC66A56F9CBB5393E6E13 - FFAD03329B9E527A43EEC66A56F9CBB5393E6E13 + location for DoD Interoperability Root CA 1 certificate is present + DoD Interoperability Root CA 1,A8C27332CCB4CA49554CE55D34062A7DD2850C02 + A8C27332CCB4CA49554CE55D34062A7DD2850C02 - - US DoD CCEB Interoperability Root CA 1 + + US DoD CCEB Interoperability Root CA 2 <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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93491.a True - location for US DoD CCEB Interoperability Root CA 1 certificate is present - US DoD CCEB Interoperability Root CA 1,DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3 - DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3 + location for US DoD CCEB Interoperability Root CA 2 certificate is present + US DoD CCEB Interoperability Root CA 2,AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 + AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 - + US DoD CCEB Interoperability Root CA 2 <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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93491.b True location for US DoD CCEB Interoperability Root CA 2 certificate is present @@ -8727,10 +9092,34 @@ Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion - + + <VulnDiscussion>Unsigned network traffic is susceptible to man-in-the-middle attacks, where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. The risk of an attacker pulling this off can be decreased by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPsec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man-in-the-middle attacks extremely difficult. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93545 + Domain_controller_LDAP_server_signing_requirements + Require Signing + False + + This applies to domain controllers. It is NA for other systems. + +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\Services\NTDS\Parameters\ + +Value Name: LDAPServerIntegrity + +Value Type: REG_DWORD +Value: 0x00000002 (2) + + <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> False + V-93289 Network access: Allow anonymous SID/Name translation Disabled False @@ -8743,83 +9132,103 @@ Navigate to Local Computer Policy >> Computer Configuration >> Windo If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding. - - <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> + + <VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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> False - Accounts: Rename administrator account - - True - '{0}' -ne 'Administrator' + V-93497 + Accounts: Guest account status + Disabled + False + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. +If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. - - <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> + + <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> False - Accounts: Rename guest account + V-93281 + Accounts: Rename administrator account True - '{0}' -ne 'Guest' + '{0}' -ne 'Administrator' Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. +If the value for "Accounts: Rename administrator account" is not set to a value other than "Administrator", this is a finding. - - <VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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> + + <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> False - Accounts: Guest account status - Disabled - False - + V-93283 + Accounts: Rename guest account + + True + '{0}' -ne 'Guest' Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. -If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. +If the value for "Accounts: Rename guest account" is not set to a value other than "Guest", this is a finding. - + <VulnDiscussion>Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93217 True ServiceName/StartupType is populated with correct AntiVirus service information Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution. -If there is no anti-virus solution installed on the system, this is a finding. +If there is no anti-virus solution installed on the system, this is a finding. + +Verify if Windows Defender is in use or enabled: + +Open "PowerShell". + +Enter “get-service | where {$_.DisplayName -Like "*Defender*"} | Select Status,DisplayName” + +Verify if third-party anti-virus is in use or enabled: + +Open "PowerShell". + +Enter "get-service | where {$_.DisplayName -Like "*mcafee*"} | Select Status,DisplayName” + +Enter "get-service | where {$_.DisplayName -Like "*symantec*"} | Select Status,DisplayName” + Running - + <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></IAControls> Present False + V-93571 True ServiceName/StartupType is populated with correct Firewall service information Determine if a host-based firewall is installed and enabled on the system. @@ -8835,35 +9244,34 @@ The configuration requirements will be determined by the applicable firewall STI - - SeDenyRemoteInteractiveLogonRight + + SeSecurityPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. -The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. +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. -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> - Deny log on through Remote Desktop Services +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + Manage auditing and security log - False - Guests + True + Administrators False + V-93197 False - This applies to domain controllers. A separate version applies to other systems. - -Verify the effective setting in Local Group Policy Editor. + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. -If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: +If any accounts or groups other than the following are granted the "Manage auditing and security log" user right, this is a finding. -- Guests Group +- Administrators - + SeNetworkLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8873,6 +9281,7 @@ Accounts with the "Access this computer from the network" right may access resou True Administrators,Authenticated Users,Enterprise Domain Controllers False + V-92995 False This applies to domain controllers. It is NA for other systems. @@ -8891,7 +9300,7 @@ If any accounts or groups other than the following are granted the "Access this - + SeRemoteInteractiveLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8901,6 +9310,7 @@ Accounts with the "Allow log on through Remote Desktop Services" user right can True Administrators False + V-92997 False This applies to domain controllers, it is NA for other systems. @@ -8916,7 +9326,7 @@ If any accounts or groups other than the following are granted the "Allow log on - + SeDenyNetworkLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8928,6 +9338,7 @@ The Guests group must be assigned this right to prevent unauthenticated access.& False Guests False + V-92999 False This applies to domain controllers. A separate version applies to other systems. @@ -8944,7 +9355,7 @@ If the following accounts or groups are not defined for the "Deny access to this - + SeDenyBatchLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8956,6 +9367,7 @@ The Guests group must be assigned to prevent unauthenticated access.</VulnDis False Guests False + V-93001 False This applies to domain controllers. A separate version applies to other systems. @@ -8972,7 +9384,7 @@ If the following accounts or groups are not defined for the "Deny log on as a ba - + SeDenyServiceLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8984,6 +9396,7 @@ Incorrect configurations could prevent services from starting and result in a de True NULL False + V-93003 False This applies to domain controllers. A separate version applies to other systems. @@ -8998,7 +9411,7 @@ If any accounts or groups are defined for the "Deny log on as a service" user ri - + SeDenyInteractiveLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9010,6 +9423,7 @@ The Guests group must be assigned this right to prevent unauthenticated access.& False Guests False + V-93005 False This applies to domain controllers. A separate version applies to other systems. @@ -9026,7 +9440,7 @@ If the following accounts or groups are not defined for the "Deny log on locally - + SeInteractiveLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9036,6 +9450,7 @@ Accounts with the "Allow log on locally" user right can log on interactively to True Administrators False + V-93017 False Verify the effective setting in Local Group Policy Editor. @@ -9050,7 +9465,36 @@ If any accounts or groups other than the following are granted the "Allow log on - + + SeDenyRemoteInteractiveLogonRight + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. + +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> + Deny log on through Remote Desktop Services + + False + Guests + False + V-92963 + False + + This applies to domain controllers. A separate version applies to other systems. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: + +- Guests Group + + + + SeMachineAccountPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9060,6 +9504,7 @@ Accounts with the "Add workstations to domain" right may add computers to a doma True Administrators False + V-93039 False This applies to domain controllers. It is NA for other systems. @@ -9076,7 +9521,7 @@ If any accounts or groups other than the following are granted the "Add workstat - + SeEnableDelegationPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9086,6 +9531,7 @@ The "Enable computer and user accounts to be trusted for delegation" user right True Administrators False + V-93041 False This applies to domain controllers. A separate version applies to other systems. @@ -9102,7 +9548,7 @@ If any accounts or groups other than the following are granted the "Enable compu - + SeTrustedCredManAccessPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9112,6 +9558,7 @@ Accounts with the "Access Credential Manager as a trusted caller" user right may True NULL False + V-93049 False Verify the effective setting in Local Group Policy Editor. @@ -9124,7 +9571,7 @@ If any accounts or groups are granted the "Access Credential Manager as a truste - + SeTcbPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9134,6 +9581,7 @@ Accounts with the "Act as part of the operating system" user right can assume th True NULL False + V-93051 False Verify the effective setting in Local Group Policy Editor. @@ -9146,7 +9594,7 @@ If any accounts or groups (to include administrators), are granted the "Act as p - + SeBackupPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9156,6 +9604,7 @@ Accounts with the "Back up files and directories" user right can circumvent file True Administrators False + V-93053 False Verify the effective setting in Local Group Policy Editor. @@ -9170,7 +9619,7 @@ If any accounts or groups other than the following are granted the "Back up file - + SeCreatePagefilePrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9180,6 +9629,7 @@ Accounts with the "Create a pagefile" user right can change the size of a pagefi True Administrators False + V-93055 False Verify the effective setting in Local Group Policy Editor. @@ -9194,7 +9644,7 @@ If any accounts or groups other than the following are granted the "Create a pag - + SeCreateTokenPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9204,6 +9654,7 @@ The "Create a token object" user right allows a process to create an access toke True NULL False + V-93057 False Verify the effective setting in Local Group Policy Editor. @@ -9216,7 +9667,7 @@ If any accounts or groups are granted the "Create a token object" user right, th - + SeCreateGlobalPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9226,6 +9677,7 @@ Accounts with the "Create global objects" user right can create objects that are True Administrators,Service,Local Service,Network Service False + V-93059 False Verify the effective setting in Local Group Policy Editor. @@ -9243,7 +9695,7 @@ If any accounts or groups other than the following are granted the "Create globa - + SeCreatePermanentPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9253,6 +9705,7 @@ Accounts with the "Create permanent shared objects" user right could expose sens True NULL False + V-93061 False Verify the effective setting in Local Group Policy Editor. @@ -9265,7 +9718,7 @@ If any accounts or groups are granted the "Create permanent shared objects" user - + SeCreateSymbolicLinkPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9275,6 +9728,7 @@ Accounts with the "Create symbolic links" user right can create pointers to othe True False + V-93063 True '{0}' -match '^(Administrators,NT Virtual Machine\\Virtual Machines|Administrators)$' Verify the effective setting in Local Group Policy Editor. @@ -9289,7 +9743,7 @@ If any accounts or groups other than the following are granted the "Create symbo - + SeDebugPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9299,6 +9753,7 @@ Accounts with the "Debug programs" user right can attach a debugger to any proce True Administrators False + V-93065 False Verify the effective setting in Local Group Policy Editor. @@ -9313,7 +9768,7 @@ If any accounts or groups other than the following are granted the "Debug progra - + SeRemoteShutdownPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9323,6 +9778,7 @@ Accounts with the "Force shutdown from a remote system" user right can remotely True Administrators False + V-93067 False Verify the effective setting in Local Group Policy Editor. @@ -9337,7 +9793,7 @@ If any accounts or groups other than the following are granted the "Force shutdo - + SeAuditPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9347,6 +9803,7 @@ The "Generate security audits" user right specifies users and processes that can True Local Service,Network Service False + V-93069 False Verify the effective setting in Local Group Policy Editor. @@ -9362,7 +9819,7 @@ If any accounts or groups other than the following are granted the "Generate sec - + SeImpersonatePrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9372,6 +9829,7 @@ The "Impersonate a client after authentication" user right allows a program to i True Administrators,Service,Local Service,Network Service False + V-93071 False Verify the effective setting in Local Group Policy Editor. @@ -9389,7 +9847,7 @@ If any accounts or groups other than the following are granted the "Impersonate - + SeIncreaseBasePriorityPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9399,6 +9857,7 @@ Accounts with the "Increase scheduling priority" user right can change a schedul True Administrators False + V-93073 False Verify the effective setting in Local Group Policy Editor. @@ -9413,7 +9872,7 @@ If any accounts or groups other than the following are granted the "Increase sch - + SeLoadDriverPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9423,6 +9882,7 @@ The "Load and unload device drivers" user right allows a user to load device dri True Administrators False + V-93075 False Verify the effective setting in Local Group Policy Editor. @@ -9437,7 +9897,7 @@ If any accounts or groups other than the following are granted the "Load and unl - + SeLockMemoryPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9447,6 +9907,7 @@ The "Lock pages in memory" user right allows physical memory to be assigned to p True NULL False + V-93077 False Verify the effective setting in Local Group Policy Editor. @@ -9459,7 +9920,7 @@ If any accounts or groups are granted the "Lock pages in memory" user right, thi - + SeSystemEnvironmentPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9469,6 +9930,7 @@ Accounts with the "Modify firmware environment values" user right can change har True Administrators False + V-93079 False Verify the effective setting in Local Group Policy Editor. @@ -9483,7 +9945,7 @@ If any accounts or groups other than the following are granted the "Modify firmw - + SeManageVolumePrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9493,6 +9955,7 @@ Accounts with the "Perform volume maintenance tasks" user right can manage volum True Administrators False + V-93081 False Verify the effective setting in Local Group Policy Editor. @@ -9507,7 +9970,7 @@ If any accounts or groups other than the following are granted the "Perform volu - + SeProfileSingleProcessPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9517,6 +9980,7 @@ Accounts with the "Profile single process" user right can monitor non-system pro True Administrators False + V-93083 False Verify the effective setting in Local Group Policy Editor. @@ -9531,7 +9995,7 @@ If any accounts or groups other than the following are granted the "Profile sing - + SeRestorePrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9541,6 +10005,7 @@ Accounts with the "Restore files and directories" user right can circumvent file True Administrators False + V-93085 False Verify the effective setting in Local Group Policy Editor. @@ -9555,7 +10020,7 @@ If any accounts or groups other than the following are granted the "Restore file - + SeTakeOwnershipPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -9565,6 +10030,7 @@ Accounts with the "Take ownership of files or other objects" user right can take True Administrators False + V-93087 False Verify the effective setting in Local Group Policy Editor. @@ -9577,41 +10043,16 @@ If any accounts or groups other than the following are granted the "Take ownersh - Administrators - - - - SeSecurityPrivilege - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - Manage auditing and security log - - True - Administrators - False - False - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -- Administrators - - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93383 Fax False @@ -9623,11 +10064,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93385 PNRP False @@ -9639,11 +10081,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93387 Simple-TCPIP False @@ -9655,11 +10098,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93389 TFTP-Client False @@ -9671,11 +10115,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Absent False + V-93391 FS-SMB1 False @@ -9689,11 +10134,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Absent False + V-93397 PowerShell-v2 False @@ -9705,11 +10151,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Absent False + V-93421 Web-Ftp-Service False @@ -9725,11 +10172,12 @@ An Installed State of "Available" or "Removed" is not a finding. If the system has the role of an FTP server, this must be documented with the ISSO. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93423 Telnet-Client False diff --git a/source/StigData/Processed/WindowsServer-2019-MS-1.5.org.default.xml b/source/StigData/Processed/WindowsServer-2019-MS-1.5.org.default.xml deleted file mode 100644 index 88567b239..000000000 --- a/source/StigData/Processed/WindowsServer-2019-MS-1.5.org.default.xml +++ /dev/null @@ -1,79 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/source/StigData/Processed/WindowsServer-2019-MS-2.2.org.default.xml b/source/StigData/Processed/WindowsServer-2019-MS-2.2.org.default.xml new file mode 100644 index 000000000..d33d4cf3f --- /dev/null +++ b/source/StigData/Processed/WindowsServer-2019-MS-2.2.org.default.xml @@ -0,0 +1,77 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/source/StigData/Processed/WindowsServer-2019-MS-1.5.xml b/source/StigData/Processed/WindowsServer-2019-MS-2.2.xml similarity index 90% rename from source/StigData/Processed/WindowsServer-2019-MS-1.5.xml rename to source/StigData/Processed/WindowsServer-2019-MS-2.2.xml index 59e8a2734..ea3761d06 100644 --- a/source/StigData/Processed/WindowsServer-2019-MS-1.5.xml +++ b/source/StigData/Processed/WindowsServer-2019-MS-2.2.xml @@ -1,9 +1,10 @@ - + - + <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 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> False + V-93141 True '{0}' -le '3' -and '{0}' -ne '0' Account lockout threshold @@ -18,12 +19,13 @@ If the "Account lockout threshold" is "0" or more than "3" attempts, this is a f - + <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. Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93143 True '{0}' -ge '15' Reset account lockout counter after @@ -38,30 +40,13 @@ If the "Reset account lockout counter after" value is less than "15" minutes, th - - <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - True - '{0}' -ge '15' -or '{0}' -eq '0' - Account lockout duration - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. - -If the "Account lockout duration" is less than "15" minutes (excluding "0"), this is a finding. - - - - + <VulnDiscussion>The use of complex passwords increases their strength against attack. The built-in Windows password complexity policy requires passwords to contain at least three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names. Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93459 False Password must meet complexity requirements @@ -76,29 +61,11 @@ If the value for "Password must meet complexity requirements" is not set to "Ena - - <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> - - False - True - '{0}' -ge '14' - Minimum password length - - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. - -If the value for the "Minimum password length," is less than "14" characters, this is a finding. - - - - + <VulnDiscussion>Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. 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></IAControls> False + V-93465 False Store passwords using reversible encryption @@ -113,10 +80,11 @@ If the value for "Store passwords using reversible encryption" is not set to "Di - + <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> False + V-93471 True '{0}' -ne '0' Minimum password age @@ -131,10 +99,11 @@ If the value for the "Minimum password age" is set to "0" days ("Password can be - + <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> False + V-93477 True '{0}' -le '60' -and '{0}' -ne '0' Maximum password age @@ -151,10 +120,11 @@ If the value is set to "0" (never expires), this is a finding. - + <VulnDiscussion>A system is more vulnerable to unauthorized access when system users recycle the same password several times without being required to change 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> False + V-93479 True '{0}' -ge '24' Enforce password history @@ -167,20 +137,60 @@ Navigate to Local Computer Policy >> Computer Configuration >> Windo If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding. + + + + <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> + + False + V-93463 + True + '{0}' -ge '14' + Minimum password length + + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy. + +If the value for the "Minimum password length," is less than "14" characters, this is a finding. + + + + + <VulnDiscussion>The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93145 + True + '{0}' -ge '15' -or '{0}' -eq '0' + Account lockout duration + + Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. + +If the "Account lockout duration" is less than "15" minutes (excluding "0"), this is a finding. + - + Success <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. +Security Group Management records events such as creating, deleting, or changing security groups, including changes in group members. -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92979 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -195,19 +205,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Logon - Success - Logon +Account Management >> Security Group Management - Success + Security Group Management - - Failure + + Success <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. +User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. -Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92981 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -222,19 +233,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Logon - Failure - Logon +Account Management >> User Account Management - Success + User Account Management - - Success + + Failure <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 security groups, including changes in group members. +User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts. Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92983 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -249,19 +261,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Account Management >> Security Group Management - Success - Security Group Management +Account Management >> User Account Management - Failure + User Account Management - + Success <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. +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. -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92967 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -276,19 +289,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Account Management >> User Account Management - Success - User Account Management +Logon/Logoff >> Logon - Success + Logon - + Failure <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. +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. -Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000476-GPOS-00221</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-92969 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -303,10 +317,10 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Account Management >> User Account Management - Failure - User Account Management +Logon/Logoff >> Logon - Failure + Logon - + Success <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. @@ -316,6 +330,7 @@ Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion Present False + V-92987 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -333,7 +348,7 @@ If the system does not audit the following, this is a finding. Logon/Logoff >> Account Lockout - Success Account Lockout - + Failure <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. @@ -343,6 +358,7 @@ Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214</VulnDiscussion Present False + V-92989 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -360,7 +376,7 @@ If the system does not audit the following, this is a finding. Logon/Logoff >> Account Lockout - Failure Account Lockout - + Success <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. @@ -370,6 +386,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93089 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -387,7 +404,7 @@ If the system does not audit the following, this is a finding: Account Management >> Other Account Management Events - Success Other Account Management Events - + Success <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. @@ -397,6 +414,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215</VulnDiscussion Present False + V-93091 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -414,7 +432,7 @@ If the system does not audit the following, this is a finding. Detailed Tracking >> Process Creation - Success Process Creation - + Success <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. @@ -424,6 +442,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93093 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -441,7 +460,7 @@ If the system does not audit the following, this is a finding. Policy Change >> Audit Policy Change - Success Audit Policy Change - + Failure <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. @@ -451,6 +470,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93095 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -468,7 +488,7 @@ If the system does not audit the following, this is a finding. Policy Change >> Audit Policy Change - Failure Audit Policy Change - + Success <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. @@ -478,6 +498,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93097 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -495,7 +516,7 @@ If the system does not audit the following, this is a finding. Policy Change >> Authentication Policy Change - Success Authentication Policy Change - + Success <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. @@ -505,6 +526,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93099 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -522,7 +544,7 @@ If the system does not audit the following, this is a finding. Policy Change >> Authorization Policy Change - Success Authorization Policy Change - + Success <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. @@ -532,6 +554,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93101 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -549,7 +572,7 @@ If the system does not audit the following, this is a finding. Privilege Use >> Sensitive Privilege Use - Success Sensitive Privilege Use - + Failure <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. @@ -559,6 +582,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPO Present False + V-93103 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -576,7 +600,7 @@ If the system does not audit the following, this is a finding. Privilege Use >> Sensitive Privilege Use - Failure Sensitive Privilege Use - + Success <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. @@ -586,6 +610,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93105 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -603,7 +628,7 @@ If the system does not audit the following, this is a finding. System >> IPsec Driver - Success IPsec Driver - + Failure <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. @@ -613,6 +638,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93107 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -630,7 +656,7 @@ If the system does not audit the following, this is a finding. System >> IPsec Driver - Failure IPsec Driver - + Success <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. @@ -640,6 +666,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93109 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -657,7 +684,7 @@ If the system does not audit the following, this is a finding. System >> Other System Events - Success Other System Events - + Failure <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. @@ -667,6 +694,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93111 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -684,7 +712,7 @@ If the system does not audit the following, this is a finding. System >> Other System Events - Failure Other System Events - + Success <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. @@ -694,6 +722,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93113 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -711,7 +740,7 @@ If the system does not audit the following, this is a finding. System >> Security State Change - Success Security State Change - + Success <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. @@ -721,6 +750,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPO Present False + V-93115 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -738,7 +768,7 @@ If the system does not audit the following, this is a finding. System >> Security System Extension - Success Security System Extension - + Success <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. @@ -748,6 +778,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPO Present False + V-93117 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -765,7 +796,7 @@ If the system does not audit the following, this is a finding. System >> System Integrity - Success System Integrity - + Failure <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. @@ -775,6 +806,7 @@ Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPO Present False + V-93119 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -792,7 +824,7 @@ If the system does not audit the following, this is a finding. System >> System Integrity - Failure System Integrity - + Success <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. @@ -800,6 +832,7 @@ Credential Validation records events related to validation tests on credentials Present False + V-93153 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -817,7 +850,7 @@ If the system does not audit the following, this is a finding. Account Logon >> Credential Validation - Success Credential Validation - + Failure <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. @@ -825,6 +858,7 @@ Credential Validation records events related to validation tests on credentials Present False + V-93155 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -842,14 +876,15 @@ If the system does not audit the following, this is a finding. Account Logon >> Credential Validation - Failure Credential Validation - + Success <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. -Plug and Play activity records events related to the successful connection of external devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Audit Group Membership records information related to the group membership of a user's logon token.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93159 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -864,17 +899,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Detailed Tracking >> Plug and Play Events - Success - Plug and Play Events +Logon/Logoff >> Group Membership - Success + Group Membership - + Success <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 Group Membership records information related to the group membership of a user's logon token.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Special Logon records special logons that have administrative privileges and can be used to elevate processes. + +Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93161 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -889,19 +927,18 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Group Membership - Success - Group Membership +Logon/Logoff >> Special Logon - Success + Special Logon - + Success <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 that have administrative privileges and can be used to elevate processes. - -Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93163 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -916,17 +953,18 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Special Logon - Success - Special Logon +Object Access >> Other Object Access Events - Success + Other Object Access Events - - Success + + Failure <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 for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93165 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -941,17 +979,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Object Access >> Other Object Access Events - Success +Object Access >> Other Object Access Events - Failure Other Object Access Events - - Failure + + Success <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 for other object access records events related to the management of task scheduler jobs and COM+ objects.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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. + +Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93171 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -966,17 +1007,18 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Object Access >> Other Object Access Events - Failure - Other Object Access Events +Logon/Logoff >> Logoff - Success + Logoff - + Success <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. -Removable Storage auditing under Object Access 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></IAControls> +Plug and Play activity records events related to the successful connection of external devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93157 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -991,19 +1033,18 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Object Access >> Removable Storage - Success - -Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. - Removable Storage +Detailed Tracking >> Plug and Play Events - Success + Plug and Play Events - - Failure + + Success <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. Removable Storage auditing under Object Access 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></IAControls> Present False + V-93167 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1018,21 +1059,20 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Object Access >> Removable Storage - Failure +Object Access >> Removable Storage - Success Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. Removable Storage - - Success + + Failure <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. - -Satisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Removable Storage auditing under Object Access 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></IAControls> Present False + V-93169 False Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN19-SO-000050) for the detailed auditing subcategories to be effective. @@ -1047,16 +1087,19 @@ Compare the "AuditPol" settings with the following: If the system does not audit the following, this is a finding. -Logon/Logoff >> Logoff - Success - Logoff +Object Access >> Removable Storage - Failure + +Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding. + Removable Storage - + <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 a file system that supports NTFS attributes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> NTFS|ReFS False + V-92991 -match False @@ -1072,11 +1115,12 @@ For each local volume, if the file system does not indicate "NTFS", this is a fi This does not apply to system partitions such the Recovery and EFI System Partition. - + <VulnDiscussion>Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level 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> 10.0.17763 False + V-93215 -le False @@ -1092,36 +1136,11 @@ Preview versions must not be used in a production environment. - - <VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Determine whether there is a HIDS or HIPS on each server. - -If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. - -A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. - -If a HIDS is not installed on the system, this is a finding. - - - <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> - - False - False - - 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 or Adobe PreFlight certificate files. 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. - - + <VulnDiscussion>Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93381 False Required roles and features will vary based on the function of the individual system. @@ -1132,10 +1151,11 @@ If the organization has not documented the roles and features required for the s The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State". - + <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 nonrepudiation or individual accountability for system access and resource usage.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93437 False Determine whether any shared accounts exist. If no shared accounts exist, this is NA. @@ -1144,10 +1164,11 @@ Shared accounts, such as required by an application, may be approved by the orga If unapproved shared accounts exist, this is a finding. - + <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, disabled until needed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93457 False Open "Windows PowerShell". @@ -1187,19 +1208,50 @@ If any enabled accounts have not been logged on to within the past 35 days, this Inactive accounts that have been reviewed and deemed to be required must be documented with the ISSO. - + <VulnDiscussion>Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using HBSS and periodic scanning using other tools.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93567 + False + + Verify DoD-approved ESS software is installed and properly operating. Ask the site ISSM for documentation of the ESS software installation and configuration. + +If the ISSM is not able to provide a documented configuration for an installed ESS or if the ESS software is not properly maintained or used, this is a finding. + +Note: Example of documentation can be a copy of the site's CCB approved Software Baseline with version of software noted or a memo from the ISSM stating current ESS software and version. + + + <VulnDiscussion>A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93219 + False + + Determine whether there is a HIDS or HIPS on each server. + +If the HIPS component of HBSS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. + +A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the ISSO. + +If a HIDS is not installed on the system, this is a finding. + + + <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> + + False + V-93221 False - Verify DoD approved HBSS software is installed, configured, and properly operating. Ask the operator to document the HBSS software installation and configuration. + Search all drives for *.p12 and *.pfx files. + +If any files with these extensions exist, this is a finding. -If the operator is not able to provide a documented configuration for an installed HBSS or if the HBSS software is not properly configured, maintained, or used, this is a finding. +This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. 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. - + <VulnDiscussion>If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. @@ -1209,6 +1261,7 @@ If temporary accounts are used, the operating system must be configured to autom To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-92975 False Review temporary user accounts for expiration dates. @@ -1231,53 +1284,91 @@ Run "Net user [username]", where [username] is the name of the temporary user ac If "Account expires" has not been defined within 72 hours for any temporary user account, this is a finding. - - <VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. - -Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. + + <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. -To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93473 False - Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. - -If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. - -If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. + Review the password last set date for the built-in Administrator account. -Domain Controllers: +Domain controllers: Open "PowerShell". -Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". +Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". -If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. Member servers and standalone systems: Open "Command Prompt". -Run "Net user [username]", where [username] is the name of the emergency account. +Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. -If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. +(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) + +If the "PasswordLastSet" date is greater than "60" days old, this is a finding. - - <VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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> False + V-93475 False - Open "Printers & scanners" in "Settings". + Review the password never expires status for enabled user accounts. -If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) +Open "PowerShell". -For each printer: +Domain Controllers: -Select the printer and "Manage". +Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". -Select "Printer Properties". +Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. + +If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. + +Member servers and standalone systems: + +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. + +Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). + +If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding. + + + <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></IAControls> + + False + V-93461 + False + + Determine if manually managed application/service accounts exist. If none exist, this is NA. + +Verify the organization has 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. + + + <VulnDiscussion>Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-92993 + False + + Open "Printers & scanners" in "Settings". + +If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.) + +For each printer: + +Select the printer and "Manage". + +Select "Printer Properties". Select the "Sharing" tab. @@ -1289,7 +1380,107 @@ The default is for the "Everyone" group to be given "Print" permission. "All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts. - + + <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. 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> + + False + V-93439 + False + + Review the password required status for enabled user accounts. + +Open "PowerShell". + +Domain Controllers: + +Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". + +Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). + +If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. + +Member servers and standalone systems: + +Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. + +Exclude disabled accounts (e.g., DefaultAccount, Guest). + +If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. + + + <VulnDiscussion>Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. + +Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. + +To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-92977 + False + + Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA. + +If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved. + +If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding. + +Domain Controllers: + +Open "PowerShell". + +Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate". + +If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. + +Member servers and standalone systems: + +Open "Command Prompt". + +Run "Net user [username]", where [username] is the name of the emergency account. + +If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding. + + + <VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93531 + False + + If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) + +Run "Computer Management". + +Navigate to System Tools >> Shared Folders >> Shares. + +Right-click any non-system-created shares. + +Select "Properties". + +Select the "Share Permissions" tab. + +If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. + +Select the "Security" tab. + +If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. + + + <VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. + +Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). + +Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93515 + False + + Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. + +If they do not, this is a finding. + + <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 using only accounts with the minimum level of authority necessary. @@ -1299,6 +1490,7 @@ For domain-joined member servers, the Domain Admins group must be replaced by a Standard user accounts must not be members of the built-in Administrators group.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93043 False This applies to member servers and standalone systems. A separate version applies to domain controllers. @@ -1319,30 +1511,22 @@ If accounts that do not have responsibility for administration of the system are If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding. - + <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93183 False Determine if a process to back up log data to a different system or media than the system being audited has been implemented. If it has not, this is a finding. - - <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. - -If they are not, this is a finding. - - + <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> False + V-93187 False Review the Windows time service configuration. @@ -1365,19 +1549,96 @@ Open "PowerShell". Enter "Get-ADDomain | FT PDCEmulator". - + <VulnDiscussion>Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code 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> False + V-93203 False Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. If system files are not monitored for unauthorized changes, this is a finding. -A properly configured HBSS Policy Auditor 5.2 or later File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. The Asset module within HBSS does not meet this requirement. +A properly configured and approved DoD HBSS solution that supports a File Integrity Monitor (FIM) module will meet the requirement for file integrity checking. + + + <VulnDiscussion>Using a whitelist provides a configuration management method to allow 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> + + False + V-93379 + False + + This 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. + +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 Server. 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 imported previously, 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" at the following link: + +https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm + + + <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. + +Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. + +Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. + +Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93543 + False + + If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. + +If protection methods have not been implemented, this is a finding. + + + <VulnDiscussion>Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93185 + False + + Verify the audit records, at a minimum, are off-loaded for interconnected systems in real time and off-loaded for standalone systems weekly. + +If they are not, this is a finding. + + + <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> + + False + V-93369 + False + + Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account. + +If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding. - + <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 account. Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to not access the Internet or use applications such as email. @@ -1387,6 +1648,7 @@ The policy should define specific exceptions for local service administration. T Whitelisting can be used to enforce the policy to ensure compliance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93205 False Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the Internet, such as web browsers, or with potential Internet sources, such as email, except as necessary for local service administration. @@ -1395,10 +1657,11 @@ If it does not, this is a finding. The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement. - + <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> False + V-93207 False If no accounts are members of the Backup Operators group, this is NA. @@ -1407,10 +1670,11 @@ Verify users with accounts in the Backup Operators group have a separate user ac If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding. - + <VulnDiscussion>Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account passwords.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93209 False Determine if manually managed application/service accounts exist. If none exist, this is NA. @@ -1438,10 +1702,11 @@ Enter 'Net User [application account name] | Find /i "Password Last Set"', where If the "Password Last Set" date is more than one year old, this is a finding. - + <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93213 False For standalone systems, this is NA. @@ -1460,12 +1725,13 @@ TPM Manufacturer Information - Specific Version = 2.0 or 1.2 If a TPM is not found or is not ready for use, this is a finding. - + <VulnDiscussion>The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult. Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized user.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93223 False If FTP is not installed on the system, this is NA. @@ -1478,10 +1744,11 @@ Double-click "FTP Authentication". If the "Anonymous Authentication" status is "Enabled", this is a finding. - + <VulnDiscussion>The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93225 False If FTP is not installed on the system, this is NA. @@ -1496,10 +1763,11 @@ If the site is not defined to a specific folder for shared FTP resources, this i If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding. - + <VulnDiscussion>UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these security features.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93229 False Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must run in "UEFI" mode. @@ -1510,10 +1778,11 @@ Run "System Information". Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding. - + <VulnDiscussion>Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93231 False Some older systems may not have UEFI firmware. This is currently a CAT III; it will be raised in severity at a future date when broad support of Windows hardware and firmware requirements are expected to be met. Devices that have UEFI firmware must have Secure Boot enabled. @@ -1528,218 +1797,257 @@ Confirm-SecureBootUEFI If a value of "True" is not returned, this is a finding. - - <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> + + <VulnDiscussion>Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be established for some reason.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93227 False - Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account. + Review the effective User Rights setting in Local Group Policy Editor. +Run "gpedit.msc". -If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding. +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +Review each User Right listed for any unresolved SIDs to determine whether they are valid, such as due to being temporarily disconnected from the domain. (Unresolved SIDs have the format that begins with "*S-1-".) + +If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding. + + - - <VulnDiscussion>Using a whitelist provides a configuration management method to allow the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. + + + + + + + + Eventlog + False + + + FullControl + + + + + SYSTEM + False + + + FullControl + + + + + Administrators + False + + + FullControl + + + <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. -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> +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + True False + V-93189 False - This 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. - -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 Server. 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 imported previously, 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" at the following link: - -https://www.iad.gov/iad/library/ia-guidance/tech-briefs/application-whitelisting-using-microsoft-applocker.cfm - - - <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. 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> - - False - False - - Review the password required status for enabled user accounts. - -Open "PowerShell". - -Domain Controllers: - -Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled". - -Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs). - -If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding. - -Member servers and standalone systems: - -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'. - -Exclude disabled accounts (e.g., DefaultAccount, Guest). + %windir%\SYSTEM32\WINEVT\LOGS\Application.evtx + Navigate to the Application event log file. -If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding. - - - <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></IAControls> - - False - False - - Determine if manually managed application/service accounts exist. If none exist, this is NA. +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. -Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length. +If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: -If such a policy does not exist or has not been implemented, this is a finding. +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control - - <VulnDiscussion>The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure. - -Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Review the password last set date for the built-in Administrator account. - -Domain controllers: - -Open "PowerShell". - -Enter "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like "*-500" | Ft Name, SID, PasswordLastSet". - -If the "PasswordLastSet" date is greater than "60" days old, this is a finding. - -Member servers and standalone systems: - -Open "Command Prompt". - -Enter 'Net User [account name] | Find /i "Password Last Set"', where [account name] is the name of the built-in administrator account. - -(The name of the built-in Administrator account must be changed to something other than "Administrator" per STIG requirements.) + + + + + + Eventlog + False + + + FullControl + + + + + SYSTEM + False + + + FullControl + + + + + Administrators + False + + + FullControl + + + <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. -If the "PasswordLastSet" date is greater than "60" days old, this is a finding. - - - <VulnDiscussion>Passwords that do not expire or are reused increase the exposure of a password with 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> +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + True False + V-93191 False - Review the password never expires status for enabled user accounts. - -Open "PowerShell". - -Domain Controllers: - -Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled". - -Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account. - -If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding. - -Member servers and standalone systems: + %windir%\SYSTEM32\WINEVT\LOGS\Security.evtx + Navigate to the Security event log file. -Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'. +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. -Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest). +If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: -If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding. +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control - - <VulnDiscussion>This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information. - -Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). - -Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest. + + + + + + Eventlog + False + + + FullControl + + + + + SYSTEM + False + + + FullControl + + + + + Administrators + False + + + FullControl + + + <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. -If they do not, this is a finding. - - - <VulnDiscussion>Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + True False + V-93193 False - If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.) - -Run "Computer Management". - -Navigate to System Tools >> Shared Folders >> Shares. - -Right-click any non-system-created shares. - -Select "Properties". - -Select the "Share Permissions" tab. + %windir%\SYSTEM32\WINEVT\LOGS\System.evtx + Navigate to the System event log file. -If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. +The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. -Select the "Security" tab. +If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: -If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding. +Eventlog - Full Control +SYSTEM - Full Control +Administrators - Full Control - - <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. - -Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. - -Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec. + + + + + + TrustedInstaller + False + + + FullControl + + + + + Administrators + False + + + ReadAndExecute + + + + + SYSTEM + False + + + ReadAndExecute + + + + + Users + False + + + ReadAndExecute + + + + + ALL APPLICATION PACKAGES + False + + + ReadAndExecute + + + + + ALL RESTRICTED APPLICATION PACKAGES + False + + + ReadAndExecute + + + <VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. -Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - False - - If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented. +Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. -If protection methods have not been implemented, this is a finding. - - - <VulnDiscussion>Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be established for some reason.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + True False + V-93195 False - Review the effective User Rights setting in Local Group Policy Editor. -Run "gpedit.msc". + %windir%\SYSTEM32\eventvwr.exe + Navigate to "%SystemRoot%\System32". -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. +View the permissions on "Eventvwr.exe". -Review each User Right listed for any unresolved SIDs to determine whether they are valid, such as due to being temporarily disconnected from the domain. (Unresolved SIDs have the format that begins with "*S-1-".) +If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. -If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding. +The default permissions below satisfy this requirement: - +TrustedInstaller - Full Control +Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute - - - + @@ -1798,6 +2106,7 @@ Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPO True False + V-93019 False %SystemDrive%\ @@ -1846,7 +2155,7 @@ BUILTIN\Users:(CI)(IO)(WD) CREATOR OWNER:(OI)(CI)(IO)(F) Successfully processed 1 files; Failed processing 0 files - + @@ -1929,6 +2238,7 @@ Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPO True False + V-93021.a False %ProgramFiles(x86)% @@ -1975,7 +2285,7 @@ APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(G Successfully processed 1 files; Failed processing 0 files - + @@ -2058,6 +2368,7 @@ Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPO True False + V-93021.b False %ProgramFiles% @@ -2104,7 +2415,7 @@ APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(G Successfully processed 1 files; Failed processing 0 files - + @@ -2187,6 +2498,7 @@ Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPO True False + V-93023 False %windir% @@ -2245,7 +2557,7 @@ APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX) APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE) Successfully processed 1 files; Failed processing 0 files - + @@ -2260,6 +2572,7 @@ Successfully processed 1 files; Failed processing 0 files True False + V-93025.a False HKLM:\SECURITY @@ -2281,7 +2594,7 @@ S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4 If the defaults have not been changed, these are not a finding. - + @@ -2328,6 +2641,7 @@ If the defaults have not been changed, these are not a finding. True False + V-93025.b False HKLM:\SOFTWARE @@ -2352,7 +2666,7 @@ S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4 If the defaults have not been changed, these are not a finding. - + @@ -2368,293 +2682,95 @@ If the defaults have not been changed, these are not a finding. Administrators False This Key and Subkeys - FullControl - - - - - SYSTEM - False - This Key and Subkeys - FullControl - - - - - CREATOR OWNER - False - Subkeys Only - FullControl - - - - - ALL APPLICATION PACKAGES - False - This Key and Subkeys - ReadKey - - - <VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - True - False - False - - HKLM:\SYSTEM - Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. -If any non-privileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. -If permissions are not as restrictive as the default permissions listed below, this is a finding: -Run "Regedit". -Right-click on the registry areas noted below. -Select "Permissions" and the "Advanced" button. -HKEY_LOCAL_MACHINE\SYSTEM -Type - "Allow" for all -Inherited from - "None" for all -Principal - Access - Applies to -Users - Read - This key and subkeys -Administrators - Full Control - This key and subkeys -SYSTEM - Full Control - This key and subkeys -CREATOR OWNER - Full Control - Subkeys only -ALL APPLICATION PACKAGES - Read - This key and subkeys -Other examples under the noted keys may also be sampled. There may be some instances where non-privileged groups have greater than Read permission. -Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID, this is currently not a finding. -S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 -If the defaults have not been changed, these are not a finding. - - - - - - - - Eventlog - False - - - FullControl - - - - - SYSTEM - False - - - FullControl - - - - - Administrators - False - - - FullControl - - - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - True - False - False - - %windir%\SYSTEM32\WINEVT\LOGS\Application.evtx - Navigate to the Application event log file. - -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. - -If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding: - -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control - - - - - - - Eventlog - False - - - FullControl - - - - - SYSTEM - False - - - FullControl - - - - - Administrators - False - - - FullControl - - - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - True - False - False - - %windir%\SYSTEM32\WINEVT\LOGS\Security.evtx - Navigate to the Security event log file. - -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. - -If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding: - -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control - - - - - - - Eventlog - False - - - FullControl - - - - - SYSTEM - False - - - FullControl - - - - - Administrators - False - - - FullControl - - - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - True - False - False - - %windir%\SYSTEM32\WINEVT\LOGS\System.evtx - Navigate to the System event log file. - -The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder. - -If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding: - -Eventlog - Full Control -SYSTEM - Full Control -Administrators - Full Control - - - - - - - TrustedInstaller - False - - - FullControl - - - - - Administrators - False - - - ReadAndExecute - - - - - SYSTEM - False - - - ReadAndExecute + FullControl - Users + SYSTEM False - - - ReadAndExecute + This Key and Subkeys + FullControl - ALL APPLICATION PACKAGES + CREATOR OWNER False - - - ReadAndExecute + Subkeys Only + FullControl - ALL RESTRICTED APPLICATION PACKAGES + ALL APPLICATION PACKAGES False - - - ReadAndExecute + This Key and Subkeys + ReadKey - <VulnDiscussion>Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. - -Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the modification or deletion of audit tools. - -Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + <VulnDiscussion>The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> True False + V-93025.c False - %windir%\SYSTEM32\eventvwr.exe - Navigate to "%SystemRoot%\System32". + HKLM:\SYSTEM + Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below. +If any non-privileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding. +If permissions are not as restrictive as the default permissions listed below, this is a finding: +Run "Regedit". +Right-click on the registry areas noted below. +Select "Permissions" and the "Advanced" button. +HKEY_LOCAL_MACHINE\SYSTEM +Type - "Allow" for all +Inherited from - "None" for all +Principal - Access - Applies to +Users - Read - This key and subkeys +Administrators - Full Control - This key and subkeys +SYSTEM - Full Control - This key and subkeys +CREATOR OWNER - Full Control - Subkeys only +ALL APPLICATION PACKAGES - Read - This key and subkeys +Other examples under the noted keys may also be sampled. There may be some instances where non-privileged groups have greater than Read permission. +Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID, this is currently not a finding. +S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681 +If the defaults have not been changed, these are not a finding. + + + + + + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + False + V-93565 + BottomUp + System + ASLR + true + False + + This is applicable to unclassified systems, for other systems this is NA. -View the permissions on "Eventvwr.exe". +The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". -If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding. +Run "Windows PowerShell" with elevated privileges (run as administrator). -The default permissions below satisfy this requirement: +Enter "Get-ProcessMitigation -System". -TrustedInstaller - Full Control -Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute +If the status of "ASLR: BottomUp" is "OFF", this is a finding. + +Values that would not be a finding include: + +ON +NOTSET (Default configuration) - - - + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Data Execution Prevention (DEP)", are enabled by default at the system level. DEP prevents code from being run from data-only memory pages. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93313 Enable System DEP @@ -2676,10 +2792,11 @@ Values that would not be a finding include: ON NOTSET (Default configuration) - + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Control flow guard (CFG)", are enabled by default at the system level. CFG ensures flow integrity for indirect calls. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93315 Enable System ControlFlowGuard @@ -2701,10 +2818,11 @@ Values that would not be a finding include: ON NOTSET (Default configuration) - + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate exception chains (SEHOP)", are enabled by default at the system level. SEHOP (structured exception handling overwrite protection) ensures the integrity of an exception chain during exception dispatch. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93317 Enable System SEHOP @@ -2726,10 +2844,11 @@ Values that would not be a finding include: ON NOTSET (Default configuration) - + <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Validate heap integrity", are enabled by default at the system level. "Validate heap integrity" terminates a process when heap corruption is detected. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93319 TerminateOnError System Heap @@ -2751,10 +2870,11 @@ Values that would not be a finding include: ON NOTSET (Default configuration) - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.a Enable Acrobat.exe DEP @@ -2763,10 +2883,11 @@ NOTSET (Default configuration) Acrobat.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.b BottomUp Acrobat.exe ASLR @@ -2775,10 +2896,11 @@ NOTSET (Default configuration) Acrobat.exe:ASLR:BottomUp:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.c ForceRelocateImages Acrobat.exe ASLR @@ -2787,10 +2909,11 @@ NOTSET (Default configuration) Acrobat.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.d EnableExportAddressFilter Acrobat.exe Payload @@ -2799,10 +2922,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.e EnableExportAddressFilterPlus Acrobat.exe Payload @@ -2811,10 +2935,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.f EnableImportAddressFilter Acrobat.exe Payload @@ -2823,10 +2948,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.g EnableRopStackPivot Acrobat.exe Payload @@ -2835,10 +2961,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.h EnableRopCallerCheck Acrobat.exe Payload @@ -2847,10 +2974,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93321.i EnableRopSimExec Acrobat.exe Payload @@ -2859,10 +2987,11 @@ NOTSET (Default configuration) Acrobat.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.a Enable AcroRd32.exe DEP @@ -2871,10 +3000,11 @@ NOTSET (Default configuration) AcroRd32.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.b BottomUp AcroRd32.exe ASLR @@ -2883,10 +3013,11 @@ NOTSET (Default configuration) AcroRd32.exe:ASLR:BottomUp:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.c ForceRelocateImages AcroRd32.exe ASLR @@ -2895,10 +3026,11 @@ NOTSET (Default configuration) AcroRd32.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.d EnableExportAddressFilter AcroRd32.exe Payload @@ -2907,10 +3039,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.e EnableExportAddressFilterPlus AcroRd32.exe Payload @@ -2919,10 +3052,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.f EnableImportAddressFilter AcroRd32.exe Payload @@ -2931,10 +3065,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.g EnableRopStackPivot AcroRd32.exe Payload @@ -2943,10 +3078,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.h EnableRopCallerCheck AcroRd32.exe Payload @@ -2955,10 +3091,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93323.i EnableRopSimExec AcroRd32.exe Payload @@ -2967,10 +3104,11 @@ NOTSET (Default configuration) AcroRd32.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93325 Enable chrome.exe DEP @@ -2993,10 +3131,11 @@ Enable: ON The PowerShell command produces a list of mitigations; only those with a required status of "ON" are listed here. - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.a Enable EXCEL.EXE DEP @@ -3005,10 +3144,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.b ForceRelocateImages EXCEL.EXE ASLR @@ -3017,10 +3157,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.c EnableExportAddressFilter EXCEL.EXE Payload @@ -3029,10 +3170,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.d EnableExportAddressFilterPlus EXCEL.EXE Payload @@ -3041,10 +3183,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.e EnableImportAddressFilter EXCEL.EXE Payload @@ -3053,10 +3196,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.f EnableRopStackPivot EXCEL.EXE Payload @@ -3065,10 +3209,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.g EnableRopCallerCheck EXCEL.EXE Payload @@ -3077,10 +3222,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93327.h EnableRopSimExec EXCEL.EXE Payload @@ -3089,10 +3235,11 @@ The PowerShell command produces a list of mitigations; only those with a require EXCEL.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93329.a Enable firefox.exe DEP @@ -3101,10 +3248,11 @@ The PowerShell command produces a list of mitigations; only those with a require firefox.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93329.b BottomUp firefox.exe ASLR @@ -3113,10 +3261,11 @@ The PowerShell command produces a list of mitigations; only those with a require firefox.exe:ASLR:BottomUp:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93329.c ForceRelocateImages firefox.exe ASLR @@ -3125,10 +3274,11 @@ The PowerShell command produces a list of mitigations; only those with a require firefox.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.a Enable FLTLDR.EXE DEP @@ -3137,10 +3287,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.b BlockRemoteImageLoads FLTLDR.EXE ImageLoad @@ -3149,10 +3300,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:ImageLoad:BlockRemoteImageLoads:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.c EnableExportAddressFilter FLTLDR.EXE Payload @@ -3161,10 +3313,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.d EnableExportAddressFilterPlus FLTLDR.EXE Payload @@ -3173,10 +3326,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.e EnableImportAddressFilter FLTLDR.EXE Payload @@ -3185,10 +3339,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.f EnableRopStackPivot FLTLDR.EXE Payload @@ -3197,10 +3352,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.g EnableRopCallerCheck FLTLDR.EXE Payload @@ -3209,10 +3365,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.h EnableRopSimExec FLTLDR.EXE Payload @@ -3221,10 +3378,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93331.i DisallowChildProcessCreation FLTLDR.EXE ChildProcess @@ -3233,10 +3391,11 @@ The PowerShell command produces a list of mitigations; only those with a require FLTLDR.EXE:Child Process:DisallowChildProcessCreation:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.a Enable GROOVE.EXE DEP @@ -3245,10 +3404,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.b ForceRelocateImages GROOVE.EXE ASLR @@ -3257,10 +3417,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.c BlockRemoteImageLoads GROOVE.EXE ImageLoad @@ -3269,10 +3430,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:ImageLoad:BlockRemoteImageLoads:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.d EnableExportAddressFilter GROOVE.EXE Payload @@ -3281,10 +3443,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.e EnableExportAddressFilterPlus GROOVE.EXE Payload @@ -3293,10 +3456,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.f EnableImportAddressFilter GROOVE.EXE Payload @@ -3305,10 +3469,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.g EnableRopStackPivot GROOVE.EXE Payload @@ -3317,10 +3482,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.h EnableRopCallerCheck GROOVE.EXE Payload @@ -3329,10 +3495,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.i EnableRopSimExec GROOVE.EXE Payload @@ -3341,10 +3508,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93333.j DisallowChildProcessCreation GROOVE.EXE ChildProcess @@ -3353,10 +3521,11 @@ The PowerShell command produces a list of mitigations; only those with a require GROOVE.EXE:Child Process:DisallowChildProcessCreation:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.a Enable iexplore.exe DEP @@ -3365,10 +3534,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.b BottomUp iexplore.exe ASLR @@ -3377,10 +3547,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:ASLR:BottomUp:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.c ForceRelocateImages iexplore.exe ASLR @@ -3389,10 +3560,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.d EnableExportAddressFilter iexplore.exe Payload @@ -3401,10 +3573,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.e EnableExportAddressFilterPlus iexplore.exe Payload @@ -3413,10 +3586,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.f EnableImportAddressFilter iexplore.exe Payload @@ -3425,10 +3599,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.g EnableRopStackPivot iexplore.exe Payload @@ -3437,10 +3612,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.h EnableRopCallerCheck iexplore.exe Payload @@ -3449,10 +3625,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93335.i EnableRopSimExec iexplore.exe Payload @@ -3461,10 +3638,11 @@ The PowerShell command produces a list of mitigations; only those with a require iexplore.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.a Enable INFOPATH.EXE DEP @@ -3473,10 +3651,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.b ForceRelocateImages INFOPATH.EXE ASLR @@ -3485,10 +3664,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.c EnableExportAddressFilter INFOPATH.EXE Payload @@ -3497,10 +3677,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.d EnableExportAddressFilterPlus INFOPATH.EXE Payload @@ -3509,10 +3690,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.e EnableImportAddressFilter INFOPATH.EXE Payload @@ -3521,10 +3703,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.f EnableRopStackPivot INFOPATH.EXE Payload @@ -3533,10 +3716,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.g EnableRopCallerCheck INFOPATH.EXE Payload @@ -3545,10 +3729,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93337.h EnableRopSimExec INFOPATH.EXE Payload @@ -3557,10 +3742,11 @@ The PowerShell command produces a list of mitigations; only those with a require INFOPATH.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.a Enable java.exe DEP @@ -3569,10 +3755,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.b EnableExportAddressFilter java.exe Payload @@ -3581,10 +3768,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.c EnableExportAddressFilterPlus java.exe Payload @@ -3593,10 +3781,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.d EnableImportAddressFilter java.exe Payload @@ -3605,10 +3794,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.e EnableRopStackPivot java.exe Payload @@ -3617,10 +3807,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.f EnableRopCallerCheck java.exe Payload @@ -3629,10 +3820,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.g EnableRopSimExec java.exe Payload @@ -3641,10 +3833,11 @@ The PowerShell command produces a list of mitigations; only those with a require java.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.h Enable javaw.exe DEP @@ -3653,10 +3846,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.i EnableExportAddressFilter javaw.exe Payload @@ -3665,10 +3859,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.j EnableExportAddressFilterPlus javaw.exe Payload @@ -3677,10 +3872,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.k EnableImportAddressFilter javaw.exe Payload @@ -3689,10 +3885,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.l EnableRopStackPivot javaw.exe Payload @@ -3701,10 +3898,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.m EnableRopCallerCheck javaw.exe Payload @@ -3713,10 +3911,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.n EnableRopSimExec javaw.exe Payload @@ -3725,10 +3924,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaw.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.o Enable javaws.exe DEP @@ -3737,10 +3937,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.p EnableExportAddressFilter javaws.exe Payload @@ -3749,10 +3950,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.q EnableExportAddressFilterPlus javaws.exe Payload @@ -3761,10 +3963,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.r EnableImportAddressFilter javaws.exe Payload @@ -3773,10 +3976,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.s EnableRopStackPivot javaws.exe Payload @@ -3785,10 +3989,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.t EnableRopCallerCheck javaws.exe Payload @@ -3797,10 +4002,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93339.u EnableRopSimExec javaws.exe Payload @@ -3809,10 +4015,11 @@ The PowerShell command produces a list of mitigations; only those with a require javaws.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.a Enable lync.exe DEP @@ -3821,10 +4028,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.b ForceRelocateImages lync.exe ASLR @@ -3833,10 +4041,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.c EnableExportAddressFilter lync.exe Payload @@ -3845,10 +4054,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.d EnableExportAddressFilterPlus lync.exe Payload @@ -3857,10 +4067,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.e EnableImportAddressFilter lync.exe Payload @@ -3869,10 +4080,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.f EnableRopStackPivot lync.exe Payload @@ -3881,10 +4093,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.g EnableRopCallerCheck lync.exe Payload @@ -3893,10 +4106,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93341.h EnableRopSimExec lync.exe Payload @@ -3905,10 +4119,11 @@ The PowerShell command produces a list of mitigations; only those with a require lync.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.a Enable MSACCESS.EXE DEP @@ -3917,10 +4132,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.b ForceRelocateImages MSACCESS.EXE ASLR @@ -3929,10 +4145,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.c EnableExportAddressFilter MSACCESS.EXE Payload @@ -3941,10 +4158,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.d EnableExportAddressFilterPlus MSACCESS.EXE Payload @@ -3953,10 +4171,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.e EnableImportAddressFilter MSACCESS.EXE Payload @@ -3965,10 +4184,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.f EnableRopStackPivot MSACCESS.EXE Payload @@ -3977,10 +4197,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.g EnableRopCallerCheck MSACCESS.EXE Payload @@ -3989,10 +4210,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93343.h EnableRopSimExec MSACCESS.EXE Payload @@ -4001,10 +4223,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSACCESS.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.a Enable MSPUB.EXE DEP @@ -4013,10 +4236,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.b ForceRelocateImages MSPUB.EXE ASLR @@ -4025,10 +4249,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.c EnableExportAddressFilter MSPUB.EXE Payload @@ -4037,10 +4262,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.d EnableExportAddressFilterPlus MSPUB.EXE Payload @@ -4049,10 +4275,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.e EnableImportAddressFilter MSPUB.EXE Payload @@ -4061,10 +4288,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.f EnableRopStackPivot MSPUB.EXE Payload @@ -4073,10 +4301,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.g EnableRopCallerCheck MSPUB.EXE Payload @@ -4085,10 +4314,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93345.h EnableRopSimExec MSPUB.EXE Payload @@ -4097,10 +4327,11 @@ The PowerShell command produces a list of mitigations; only those with a require MSPUB.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.a Enable OIS.EXE DEP @@ -4109,10 +4340,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.b EnableExportAddressFilter OIS.EXE Payload @@ -4121,10 +4353,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.c EnableExportAddressFilterPlus OIS.EXE Payload @@ -4133,10 +4366,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.d EnableImportAddressFilter OIS.EXE Payload @@ -4145,10 +4379,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.e EnableRopStackPivot OIS.EXE Payload @@ -4157,10 +4392,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.f EnableRopCallerCheck OIS.EXE Payload @@ -4169,10 +4405,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93347.g EnableRopSimExec OIS.EXE Payload @@ -4181,10 +4418,11 @@ The PowerShell command produces a list of mitigations; only those with a require OIS.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.a Enable OneDrive.exe DEP @@ -4193,10 +4431,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.b ForceRelocateImages OneDrive.exe ASLR @@ -4205,10 +4444,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.c BlockRemoteImageLoads OneDrive.exe ImageLoad @@ -4217,10 +4457,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:ImageLoad:BlockRemoteImageLoads:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.d EnableExportAddressFilter OneDrive.exe Payload @@ -4229,10 +4470,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.e EnableExportAddressFilterPlus OneDrive.exe Payload @@ -4241,10 +4483,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.f EnableImportAddressFilter OneDrive.exe Payload @@ -4253,10 +4496,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.g EnableRopStackPivot OneDrive.exe Payload @@ -4265,10 +4509,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.h EnableRopCallerCheck OneDrive.exe Payload @@ -4277,10 +4522,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93349.i EnableRopSimExec OneDrive.exe Payload @@ -4289,10 +4535,11 @@ The PowerShell command produces a list of mitigations; only those with a require OneDrive.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.a Enable OUTLOOK.EXE DEP @@ -4301,10 +4548,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.b ForceRelocateImages OUTLOOK.EXE ASLR @@ -4313,10 +4561,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.c EnableExportAddressFilter OUTLOOK.EXE Payload @@ -4325,10 +4574,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.d EnableExportAddressFilterPlus OUTLOOK.EXE Payload @@ -4337,10 +4587,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.e EnableImportAddressFilter OUTLOOK.EXE Payload @@ -4349,10 +4600,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.f EnableRopStackPivot OUTLOOK.EXE Payload @@ -4361,10 +4613,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.g EnableRopCallerCheck OUTLOOK.EXE Payload @@ -4373,10 +4626,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93351.h EnableRopSimExec OUTLOOK.EXE Payload @@ -4385,10 +4639,11 @@ The PowerShell command produces a list of mitigations; only those with a require OUTLOOK.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.a Enable plugin-container.exe DEP @@ -4397,10 +4652,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.b EnableExportAddressFilter plugin-container.exe Payload @@ -4409,10 +4665,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.c EnableExportAddressFilterPlus plugin-container.exe Payload @@ -4421,10 +4678,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.d EnableImportAddressFilter plugin-container.exe Payload @@ -4433,10 +4691,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.e EnableRopStackPivot plugin-container.exe Payload @@ -4445,10 +4704,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.f EnableRopCallerCheck plugin-container.exe Payload @@ -4457,10 +4717,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93353.g EnableRopSimExec plugin-container.exe Payload @@ -4469,10 +4730,11 @@ The PowerShell command produces a list of mitigations; only those with a require plugin-container.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.a Enable POWERPNT.EXE DEP @@ -4481,10 +4743,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.b ForceRelocateImages POWERPNT.EXE ASLR @@ -4493,10 +4756,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.c EnableExportAddressFilter POWERPNT.EXE Payload @@ -4505,10 +4769,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.d EnableExportAddressFilterPlus POWERPNT.EXE Payload @@ -4517,10 +4782,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.e EnableImportAddressFilter POWERPNT.EXE Payload @@ -4529,10 +4795,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.f EnableRopStackPivot POWERPNT.EXE Payload @@ -4541,10 +4808,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.g EnableRopCallerCheck POWERPNT.EXE Payload @@ -4553,10 +4821,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93355.h EnableRopSimExec POWERPNT.EXE Payload @@ -4565,10 +4834,11 @@ The PowerShell command produces a list of mitigations; only those with a require POWERPNT.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.a Enable PPTVIEW.EXE DEP @@ -4577,10 +4847,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.b ForceRelocateImages PPTVIEW.EXE ASLR @@ -4589,10 +4860,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.c EnableExportAddressFilter PPTVIEW.EXE Payload @@ -4601,10 +4873,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.d EnableExportAddressFilterPlus PPTVIEW.EXE Payload @@ -4613,10 +4886,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.e EnableImportAddressFilter PPTVIEW.EXE Payload @@ -4625,10 +4899,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.f EnableRopStackPivot PPTVIEW.EXE Payload @@ -4637,10 +4912,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.g EnableRopCallerCheck PPTVIEW.EXE Payload @@ -4649,10 +4925,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93357.h EnableRopSimExec PPTVIEW.EXE Payload @@ -4661,10 +4938,11 @@ The PowerShell command produces a list of mitigations; only those with a require PPTVIEW.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.a Enable VISIO.EXE DEP @@ -4673,10 +4951,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.b ForceRelocateImages VISIO.EXE ASLR @@ -4685,10 +4964,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.c EnableExportAddressFilter VISIO.EXE Payload @@ -4697,10 +4977,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.d EnableExportAddressFilterPlus VISIO.EXE Payload @@ -4709,10 +4990,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.e EnableImportAddressFilter VISIO.EXE Payload @@ -4721,10 +5003,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.f EnableRopStackPivot VISIO.EXE Payload @@ -4733,10 +5016,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.g EnableRopCallerCheck VISIO.EXE Payload @@ -4745,10 +5029,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93359.h EnableRopSimExec VISIO.EXE Payload @@ -4757,10 +5042,11 @@ The PowerShell command produces a list of mitigations; only those with a require VISIO.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.a Enable VPREVIEW.EXE DEP @@ -4769,10 +5055,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.b ForceRelocateImages VPREVIEW.EXE ASLR @@ -4781,10 +5068,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.c EnableExportAddressFilter VPREVIEW.EXE Payload @@ -4793,10 +5081,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.d EnableExportAddressFilterPlus VPREVIEW.EXE Payload @@ -4805,10 +5094,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.e EnableImportAddressFilter VPREVIEW.EXE Payload @@ -4817,10 +5107,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.f EnableRopStackPivot VPREVIEW.EXE Payload @@ -4829,10 +5120,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.g EnableRopCallerCheck VPREVIEW.EXE Payload @@ -4841,10 +5133,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93361.h EnableRopSimExec VPREVIEW.EXE Payload @@ -4853,10 +5146,11 @@ The PowerShell command produces a list of mitigations; only those with a require VPREVIEW.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.a Enable WINWORD.EXE DEP @@ -4865,10 +5159,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.b ForceRelocateImages WINWORD.EXE ASLR @@ -4877,10 +5172,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:ASLR:ForceRelocateImages:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.c EnableExportAddressFilter WINWORD.EXE Payload @@ -4889,10 +5185,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.d EnableExportAddressFilterPlus WINWORD.EXE Payload @@ -4901,10 +5198,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.e EnableImportAddressFilter WINWORD.EXE Payload @@ -4913,10 +5211,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.f EnableRopStackPivot WINWORD.EXE Payload @@ -4925,10 +5224,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.g EnableRopCallerCheck WINWORD.EXE Payload @@ -4937,10 +5237,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93363.h EnableRopSimExec WINWORD.EXE Payload @@ -4949,10 +5250,11 @@ The PowerShell command produces a list of mitigations; only those with a require WINWORD.EXE:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93365.a Enable wmplayer.exe DEP @@ -4961,10 +5263,11 @@ The PowerShell command produces a list of mitigations; only those with a require wmplayer.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93365.b EnableRopStackPivot wmplayer.exe Payload @@ -4973,10 +5276,11 @@ The PowerShell command produces a list of mitigations; only those with a require wmplayer.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93365.c EnableRopCallerCheck wmplayer.exe Payload @@ -4985,10 +5289,11 @@ The PowerShell command produces a list of mitigations; only those with a require wmplayer.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93365.d EnableRopSimExec wmplayer.exe Payload @@ -4997,10 +5302,11 @@ The PowerShell command produces a list of mitigations; only those with a require wmplayer.exe:Payload:EnableRopSimExec:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.a Enable wordpad.exe DEP @@ -5009,10 +5315,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:DEP:Enable:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.b EnableExportAddressFilter wordpad.exe Payload @@ -5021,10 +5328,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableExportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.c EnableExportAddressFilterPlus wordpad.exe Payload @@ -5033,10 +5341,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableExportAddressFilterPlus:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.d EnableImportAddressFilter wordpad.exe Payload @@ -5045,10 +5354,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableImportAddressFilter:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.e EnableRopStackPivot wordpad.exe Payload @@ -5057,10 +5367,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableRopStackPivot:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.f EnableRopCallerCheck wordpad.exe Payload @@ -5069,10 +5380,11 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableRopCallerCheck:ON - + <VulnDiscussion>Exploit protection provides a means of enabling additional mitigations against potential threats at the system and application level. Without these additional application protections, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93367.g EnableRopSimExec wordpad.exe Payload @@ -5081,34 +5393,89 @@ The PowerShell command produces a list of mitigations; only those with a require wordpad.exe:Payload:EnableRopSimExec:ON - - <VulnDiscussion>Exploit protection enables mitigations against potential threats at the system and application level. Several mitigations, including "Randomize memory allocations (Bottom-Up ASLR)", are enabled by default at the system level. Bottom-Up ASLR (address space layout randomization) randomizes locations for virtual memory allocations, including those for system structures. If this is turned off, Windows may be subject to various exploits.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + + + <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + Present False - BottomUp - System - ASLR - true + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93147 False - This is applicable to unclassified systems, for other systems this is NA. + If the following registry value does not exist or is not configured as specified, this is a finding: -The default configuration in Exploit Protection is "On by default" which meets this requirement. The PowerShell query results for this show as "NOTSET". +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Run "Windows PowerShell" with elevated privileges (run as administrator). +Value Name: LegalNoticeText -Enter "Get-ProcessMitigation -System". +Value Type: REG_SZ +Value: See message text below -If the status of "ASLR: BottomUp" is "OFF", this is a finding. +You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. -Values that would not be a finding include: +By using this IS (which includes any device attached to this IS), you consent to the following conditions: -ON -NOTSET (Default configuration) +-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. + 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. + LegalNoticeText + String - - - + + <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + +Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + Present + False + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93149 + True + '{0}' -match '^(DoD Notice and Consent Banner|US Department of Defense Warning Statement)$' + 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: LegalNoticeCaption + +Value Type: REG_SZ +Value: See message title options below + +"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. + +If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. + +Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required. + + LegalNoticeCaption + String + + <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. Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -5116,6 +5483,7 @@ Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPO Present False HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-92961 True '{0}' -le '900' -and '{0}' -gt '0' If the following registry value does not exist or is not configured as specified, this is a finding: @@ -5131,7 +5499,7 @@ Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled)InactivityTimeoutSecs Dword - + <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. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -5139,6 +5507,7 @@ Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion Present False HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-92971 False If the following registry value does not exist or is not configured as specified, this is a finding: @@ -5154,7 +5523,7 @@ Value: 0x00000001 (1) fEncryptRPCTraffic Dword - + <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. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -5162,6 +5531,7 @@ Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093</VulnDiscussion Present False HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-92973 False If the following registry value does not exist or is not configured as specified, this is a finding: @@ -5177,114 +5547,62 @@ Value: 0x00000003 (3) MinEncryptionLevel Dword - - <VulnDiscussion>The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Present - False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa - False - - This applies to member servers and standalone systems; it is NA for domain controllers. - -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\Lsa\ - -Value Name: RestrictRemoteSAM - -Value Type: REG_SZ -Value: O:BAG:BAD:(A;;RC;;;BA) - O:BAG:BAD:(A;;RC;;;BA) - RestrictRemoteSAM - String - - - <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + + <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. -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit + V-93173 False 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: LegalNoticeText - -Value Type: REG_SZ -Value: See message text below - -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. - 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. +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\ --This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. +Value Name: ProcessCreationIncludeCmdLine_Enabled --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. - LegalNoticeText - String +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + ProcessCreationIncludeCmdLine_Enabled + Dword - - <VulnDiscussion>Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. + + <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. -Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System - True - '{0}' -match '^(DoD Notice and Consent Banner|US Department of Defense Warning Statement)$' + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging + V-93175 + False + 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: LegalNoticeCaption - -Value Type: REG_SZ -Value: See message title options below - -"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. +Registry Path: \SOFTWARE\ Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\ -If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000150. +Value Name: EnableScriptBlockLogging -Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required. - - LegalNoticeCaption - String +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + EnableScriptBlockLogging + Dword - + <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></IAControls> Present False HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93151 False If the following registry value does not exist or is not configured as specified, this is a finding: @@ -5300,1912 +5618,1991 @@ Value: 0x00000001 (1) SCENoApplyLegacyAuditPolicy Dword - - <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. + + <VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. -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> +The cornerstone of the PKI is the private key used to encrypt or digitally sign information. + +If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. + +Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography + V-93493 False 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\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Cryptography\ -Value Name: ProcessCreationIncludeCmdLine_Enabled +Value Name: ForceKeyProtection -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - ProcessCreationIncludeCmdLine_Enabled +Type: REG_DWORD +Value: 0x00000002 (2) + 2 + ForceKeyProtection Dword - - <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 PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. 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> + + <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 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93467 False 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\PowerShell\ScriptBlockLogging\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: EnableScriptBlockLogging +Value Name: NoLMHash Value Type: REG_DWORD Value: 0x00000001 (1) 1 - EnableScriptBlockLogging + NoLMHash Dword - - <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> + + <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 determine 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\Application - True - '{0}' -ge '32768' - If the system is configured to write events directly to an audit server, this is NA. - -If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + V-93469 + False + + 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\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -Value Name: MaxSize +Value Name: EnablePlainTextPassword -Type: REG_DWORD -Value: 0x00008000 (32768) (or greater) - - MaxSize +Value Type: REG_DWORD +Value: 0x00000000 (0) + 0 + EnablePlainTextPassword Dword - - <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> + + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\Security - True - '{0}' -ge '196608' - If the system is configured to write events directly to an audit server, this is NA. + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters + V-93393 + False + + Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, 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\Windows\EventLog\Security\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\ -Value Name: MaxSize +Value Name: SMB1 Type: REG_DWORD -Value: 0x00030000 (196608) (or greater) - - MaxSize +Value: 0x00000000 (0) + 0 + SMB1 Dword - - <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> + + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\System - True - '{0}' -ge '32768' - If the system is configured to write events directly to an audit server, this is NA. + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mrxsmb10 + V-93395 + False + + Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. -If the following registry value does not exist or is not configured as specified, this is a finding: +If the following registry value is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\ +Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\ -Value Name: MaxSize +Value Name: Start Type: REG_DWORD -Value: 0x00008000 (32768) (or greater) - - MaxSize +Value: 0x00000004 (4) + 4 + Start Dword - - <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> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization + V-93399 False - If the following registry value does not exist or is not configured as specified, this is a finding: + 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\Installer\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\ -Value Name: EnableUserControl +Value Name: NoLockScreenSlideshow -Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EnableUserControl +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + NoLockScreenSlideshow Dword - - <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></IAControls> + + <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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is enforced.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest + V-93401 False 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\Installer\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\ -Value Name: AlwaysInstallElevated +Value Name: UseLogonCredential -Type: REG_DWORD -Value: 0x00000000 (0) +Type: REG_DWORD +Value: 0x00000000 (0) 0 - AlwaysInstallElevated + UseLogonCredential Dword - - <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></IAControls> + + <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 will prevent 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers + V-93403 False 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\Services\Tcpip6\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ -Value Name: DisableIPSourceRouting +Value Name: DisableWebPnPDownload Type: REG_DWORD -Value: 0x00000002 (2) - 2 - DisableIPSourceRouting +Value: 0x00000001 (1) + 1 + DisableWebPnPDownload Dword - - <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> + + <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 will prevent 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers + V-93405 False 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\Services\Tcpip\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\ -Value Name: DisableIPSourceRouting +Value Name: DisableHTTPPrinting -Value Type: REG_DWORD -Value: 0x00000002 (2) - 2 - DisableIPSourceRouting +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + DisableHTTPPrinting Dword - - <VulnDiscussion>Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via the 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> + + <VulnDiscussion>Enabling interaction with the network selection UI allows users to change connections to available networks without signing in to Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + V-93407 False - If the following registry value does not exist or is not configured as specified, this is a finding: + 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: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\ -Value Name: EnableICMPRedirect +Value Name: DontDisplayNetworkSelectionUI Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EnableICMPRedirect +Value: 0x00000001 (1) + 1 + DontDisplayNetworkSelectionUI Dword - - <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 will prevent 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AppCompat + V-93409 False 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\LanmanWorkstation\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\ -Value Name: AllowInsecureGuestAuth +Value Name: DisableInventory Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowInsecureGuestAuth +Value: 0x00000001 (1) + 1 + DisableInventory Dword - - <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - Present - False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths - False - - Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ -Value Type: REG_SZ -Value Name: \\*\NETLOGON -Value: RequireMutualAuthentication=1, RequireIntegrity=1 - RequireMutualAuthentication=1, RequireIntegrity=1 - \\*\NETLOGON - String - - - <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + V-93411 False - Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ -Value Type: REG_SZ -Value Name: \\*\SYSVOL -Value: RequireMutualAuthentication=1, RequireIntegrity=1 - RequireMutualAuthentication=1, RequireIntegrity=1 - \\*\SYSVOL - String + This is applicable to unclassified systems; for other systems, 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\Windows\System\ + +Value Name: EnableSmartScreen + +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + EnableSmartScreen + Dword - - <VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds + V-93413 False - If the following registry value does not exist or is not configured as specified, this is a finding: + The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ -Value Name: AllowProtectedCreds +Value Name: AllowBasicAuthInClear -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - AllowProtectedCreds +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) + 0 + AllowBasicAuthInClear Dword - - <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search + V-93415 False - Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ + 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\Windows Search\ + +Value Name: AllowIndexingEncryptedStoresOrItems + Value Type: REG_DWORD -Value Name: EnableVirtualizationBasedSecurity -Value: 0x00000001 (1) - 1 - EnableVirtualizationBasedSecurity +Value: 0x00000000 (0) + 0 + AllowIndexingEncryptedStoresOrItems Dword - - <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard - True - '{0}' -match '1|3' - Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ -Value Type: REG_DWORD -Value Name: RequirePlatformSecurityFeatures -Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) - - RequirePlatformSecurityFeatures + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + V-93419 + False + + This applies to member servers. For domain controllers and standalone systems, 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\Windows\System\ + +Value Name: EnumerateLocalUsers + +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + EnumerateLocalUsers Dword - - <VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls> + + <VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. + +Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\EarlyLaunch - True - '{0}' -match '1|3|8|ShouldBeAbsent' - The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000007 (7)", this is a finding. + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters + V-93495 + False + + 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\Policies\EarlyLaunch\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\ -Value Name: DriverLoadPolicy +Value Name: SupportedEncryptionTypes Value Type: REG_DWORD -Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) - -Possible values for this setting are: -8 - Good only -1 - Good and unknown -3 - Good, unknown and bad but critical -7 - All (which includes "bad" and would be a finding) - - DriverLoadPolicy +Value: 0x7ffffff8 (2147483640) + 2147483640 + SupportedEncryptionTypes Dword - - <VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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> + + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2} + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client + V-93503 False 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\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -Value Name: NoGPOListChanges +Value Name: AllowBasic Type: REG_DWORD Value: 0x00000000 (0) 0 - NoGPOListChanges + AllowBasic Dword - - <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> + + <VulnDiscussion>Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks. Disallowing Digest authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51 + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client + V-93505 False 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\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -Value Name: DCSettingIndex +Value Name: AllowDigest Type: REG_DWORD -Value: 0x00000001 (1) - 1 - DCSettingIndex +Value: 0x00000000 (0) + 0 + AllowDigest Dword - - <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> + + <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51 + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + V-93507 False 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\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -Value Name: ACSettingIndex +Value Name: AllowBasic Type: REG_DWORD -Value: 0x00000001 (1) - 1 - ACSettingIndex +Value: 0x00000000 (0) + 0 + AllowBasic Dword - - <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection - True - '{0}' -match '0|1' + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI + V-93517 + False + 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\DataCollection\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ -Value Name: AllowTelemetry +Value Name: EnumerateAdministrators Type: REG_DWORD -Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic) - - AllowTelemetry +Value: 0x00000000 (0) + 0 + EnumerateAdministrators Dword - - <VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 local 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization - True - '{0}' -match '0|1|2|99|100' - If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93519 + False + + This applies to member servers. For domain controllers and standalone systems, this is NA. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\ +If the following registry value does not exist or is not configured as specified, this is a finding: -Value Name: DODownloadMode +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Value Type: REG_DWORD -Value: 0x00000000 (0) - No peering (HTTP Only) -0x00000001 (1) - Peers on same NAT only (LAN) -0x00000002 (2) - Local Network / Private group peering (Group) -0x00000063 (99) - Simple download mode, no peering (Simple) -0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) +Value Name: LocalAccountTokenFilterPolicy -A value of 0x00000003 (3), Internet, is a finding. - - DODownloadMode +Type: REG_DWORD +Value: 0x00000000 (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. + 0 + LocalAccountTokenFilterPolicy Dword - - <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></IAControls> + + <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93521 False - The default behavior is for File Explorer heap termination on corruption to be enabled. - -If the registry Value Name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -If it exists and is configured with a value of "1", this is a finding. +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\Explorer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: NoHeapTerminationOnCorruption +Value Name: EnableUIADesktopToggle Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) +Value: 0x00000000 (0) 0 - NoHeapTerminationOnCorruption + EnableUIADesktopToggle Dword - - <VulnDiscussion>The shell protocol will limit the set of folders that 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> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer - False - - The default behavior is for shell protected mode to be turned on for File Explorer. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93523 + True + '{0}' -match '1|2' + UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). -If it exists and is configured with a value of "1", this is a finding. +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\Explorer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: PreXPSP2ShellProtocolBehavior +Value Name: ConsentPromptBehaviorAdmin Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - 0 - PreXPSP2ShellProtocolBehavior +Value: 0x00000002 (2) (Prompt for consent on the secure desktop) +0x00000001 (1) (Prompt for credentials on the secure desktop) + + ConsentPromptBehaviorAdmin Dword - - <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> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93525 False - If the following registry value does not exist or is not configured as specified, this is a finding: + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\Internet Explorer\Feeds\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: DisableEnclosureDownload +Value Name: EnableInstallerDetection -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DisableEnclosureDownload + EnableInstallerDetection Dword - - <VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93527 False - The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -If it exists and is configured with a value of "1", this is a finding. +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\Installer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: SafeForScripting +Value Name: EnableSecureUIAPaths Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - 0 - SafeForScripting +Value: 0x00000001 (1) + 1 + EnableSecureUIAPaths Dword - - <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> + + <VulnDiscussion>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></IAControls> Present False HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93529 False - Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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: DisableAutomaticRestartSignOn +Value Name: EnableVirtualization Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DisableAutomaticRestartSignOn + EnableVirtualization Dword - - <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> + + <VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon - True - '{0}' -le '4' - This applies to member servers. For domain controllers and standalone systems, this is NA. - -If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-93533 + False + + 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 NT\CurrentVersion\Winlogon\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Value Name: CachedLogonsCount +Value Name: fDisableCdm -Value Type: REG_SZ -Value: 4 (or less) - - CachedLogonsCount - String +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + fDisableCdm + Dword - - <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. This authentication information, which was stored in the Local Security Authority (LSA) in previous versions of Windows, is isolated from the rest of operating system and can only be accessed by privileged system software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93537 False - For domain controllers and standalone systems, this is NA. - -Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. - -Open "PowerShell" with elevated privileges (run as administrator). - -Enter the following: - -"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" - -If "SecurityServicesRunning" does not include a value of "1" (e.g., "{1, 2}"), this is a finding. - -Alternately: - -Run "System Information". - -Under "System Summary", verify the following: - -If "Device Guard Security Services Running" does not list "Credential Guard", this is a finding. - -The policy settings referenced in the Fix section will configure the following registry value. However, due to hardware requirements, the registry value alone does not ensure proper function. + 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\DeviceGuard\ - -Value Name: LsaCfgFlags -Value Type: REG_DWORD -Value: 0x00000001 (1) (Enabled with UEFI lock) +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -A Microsoft article on Credential Guard system requirement can be found at the following link: +Value Name: RestrictAnonymous -https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements +Value Type: REG_DWORD +Value: 0x00000001 (1) 1 - LsaCfgFlags + RestrictAnonymous Dword - - <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 does 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> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + V-93539 False 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\Lsa\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Value Name: LimitBlankPasswordUse +Value Name: RestrictNullSessAccess Value Type: REG_DWORD Value: 0x00000001 (1) 1 - LimitBlankPasswordUse + RestrictNullSessAccess Dword - - <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 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> + + <VulnDiscussion>The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters - True - '{0}' -le '30' -and '{0}' -gt '0' - This is the default configuration for this setting (30 days). + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93045 + False + + This applies to member servers and standalone systems; it is NA for domain controllers. 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: MaximumPasswordAge +Value Name: RestrictRemoteSAM -Value Type: REG_DWORD -Value: 0x0000001e (30) (or less, but not 0) - - MaximumPasswordAge - Dword +Value Type: REG_SZ +Value: O:BAG:BAD:(A;;RC;;;BA) + O:BAG:BAD:(A;;RC;;;BA) + RestrictRemoteSAM + String - - <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> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\Application + V-93177 True - '{0}' -match '1|2' - If the following registry value does not exist or is not configured as specified, this is a finding: + '{0}' -ge '32768' + If the system is configured to write events directly to an audit server, this is NA. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ +If the following registry value does not exist or is not configured as specified, this is a finding: -Value Name: scremoveoption +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Application\ -Value Type: REG_SZ -Value: 1 (Lock Workstation) or 2 (Force Logoff) +Value Name: MaxSize -If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO. +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater) - scremoveoption - String + MaxSize + Dword - - <VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa - False - - If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\Security + V-93179 + True + '{0}' -ge '196608' + If the system is configured to write events directly to an audit server, 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: \SYSTEM\CurrentControlSet\Control\Lsa\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\ -Value Name: RestrictAnonymousSAM +Value Name: MaxSize -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - RestrictAnonymousSAM +Type: REG_DWORD +Value: 0x00030000 (196608) (or greater) + + MaxSize Dword - - <VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa - False - - If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog\System + V-93181 + True + '{0}' -ge '32768' + If the system is configured to write events directly to an audit server, 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: \SYSTEM\CurrentControlSet\Control\Lsa\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\ -Value Name: EveryoneIncludesAnonymous +Value Name: MaxSize -Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EveryoneIncludesAnonymous +Type: REG_DWORD +Value: 0x00008000 (32768) (or greater) + + MaxSize Dword - - <VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + V-93199 False 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\LSA\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: UseMachineId +Value Name: EnableUserControl Type: REG_DWORD -Value: 0x00000001 (1) - 1 - UseMachineId +Value: 0x00000000 (0) + 0 + EnableUserControl Dword - - <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></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\MSV1_0 + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + V-93201 False 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\LSA\MSV1_0\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: allownullsessionfallback +Value Name: AlwaysInstallElevated Type: REG_DWORD Value: 0x00000000 (0) 0 - allownullsessionfallback + AlwaysInstallElevated Dword - - <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></IAControls> + + <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon as media is inserted into 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\pku2u + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + V-93373 False 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\LSA\pku2u\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -Value Name: AllowOnlineID +Value Name: NoAutoplayfornonVolume Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowOnlineID +Value: 0x00000001 (1) + 1 + NoAutoplayfornonVolume Dword - - <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 standalone 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></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + V-93375 False 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\Lsa\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ -Value Name: LmCompatibilityLevel +Value Name: NoAutorun -Value Type: REG_DWORD -Value: 0x00000005 (5) - 5 - LmCompatibilityLevel +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + NoAutorun Dword - - <VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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> + + <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon media is inserted into 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. Enabling this policy disables 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LDAP + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer + V-93377 False 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\Services\LDAP\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\ -Value Name: LDAPClientIntegrity +Value Name: NoDriveTypeAutoRun -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - LDAPClientIntegrity +Type: REG_DWORD +Value: 0x000000ff (255) + 255 + NoDriveTypeAutoRun Dword - - <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> + + <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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-93425 False 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\Lsa\MSV1_0\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Value Name: NTLMMinClientSec +Value Name: DisablePasswordSaving -Value Type: REG_DWORD -Value: 0x20080000 (537395200) - 537395200 - NTLMMinClientSec +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + DisablePasswordSaving Dword - - <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> + + <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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + V-93427 False 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\Lsa\MSV1_0\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ -Value Name: NTLMMinServerSec +Value Name: fPromptForPassword -Value Type: REG_DWORD -Value: 0x20080000 (537395200) - 537395200 - NTLMMinServerSec +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + fPromptForPassword Dword - - <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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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> + + <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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + V-93429 False 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\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -Value Name: ProtectionMode +Value Name: DisableRunAs -Value Type: REG_DWORD +Type: REG_DWORD Value: 0x00000001 (1) 1 - ProtectionMode + DisableRunAs Dword - - <VulnDiscussion>Attachments from outside sources may contain malicious code. 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> + + <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. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93431 False - The default behavior is for Windows to mark file attachments with their zone information. - -If the registry Value Name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000002 (2) (or if the Value Name does not exist)", this is not a finding. + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). -If it exists and is configured with a value of "1", this is a finding. +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\Microsoft\Windows\CurrentVersion\Policies\Attachments\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: SaveZoneInformation +Value Name: FilterAdministratorToken Value Type: REG_DWORD -Value: 0x00000002 (2) (or if the Value Name does not exist) - 2 - SaveZoneInformation +Value: 0x00000001 (1) + 1 + FilterAdministratorToken Dword - - <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon as media is inserted into 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></IAControls> + + <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93433 False - If the following registry value does not exist or is not configured as specified, this is a finding: + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\Explorer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: NoAutoplayfornonVolume +Value Name: ConsentPromptBehaviorUser -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - NoAutoplayfornonVolume +Value Type: REG_DWORD +Value: 0x00000000 (0) + 0 + ConsentPromptBehaviorUser Dword - - <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></IAControls> + + <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC. + +Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93435 False - If the following registry value does not exist or is not configured as specified, this is a finding: + UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + +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\Explorer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: NoAutorun +Value Name: EnableLUA -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000001 (1) 1 - NoAutorun + EnableLUA Dword - - <VulnDiscussion>Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon media is inserted into 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. Enabling this policy disables 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> + + <VulnDiscussion>Unauthenticated RPC clients may allow anonymous access to sensitive information. 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Rpc + V-93453 False - If the following registry value does not exist or is not configured as specified, this is a finding: + This applies to member servers and standalone systems, it is NA for domain controllers. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\ +If the following registry value does not exist or is not configured as specified, this is a finding: -Value Name: NoDriveTypeAutoRun +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Rpc\ -Type: REG_DWORD -Value: 0x000000ff (255) - 255 - NoDriveTypeAutoRun +Value Name: RestrictRemoteClients + +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + RestrictRemoteClients Dword - - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 the 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93455 False - Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\Services\LanmanServer\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: SMB1 +Value Name: DisablePasswordChange -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000000 (0) 0 - SMB1 + DisablePasswordChange Dword - - <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. + +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mrxsmb10 + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client + V-93499 False - Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA. - -If the following registry value is not configured as specified, this is a finding: + 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\Services\mrxsmb10\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\ -Value Name: Start +Value Name: AllowUnencryptedTraffic Type: REG_DWORD -Value: 0x00000004 (4) - 4 - Start +Value: 0x00000000 (0) + 0 + AllowUnencryptedTraffic Dword - - <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> + + <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. + +Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + V-93501 False - Verify the registry value below. - -If it does not exist or is not configured as specified, this is a finding. + 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\Personalization\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\ -Value Name: NoLockScreenSlideshow +Value Name: AllowUnencryptedTraffic -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - NoLockScreenSlideshow +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + AllowUnencryptedTraffic Dword - - <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. WDigest is disabled by default in Windows Server 2019. This setting ensures this is enforced.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 server's 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netbt\Parameters + V-93541 False 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netbt\Parameters\ -Value Name: UseLogonCredential +Value Name: NoNameReleaseOnDemand -Type: REG_DWORD -Value: 0x00000000 (0) - 0 - UseLogonCredential +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + NoNameReleaseOnDemand Dword - - <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 will prevent uncontrolled updates to the system. + + <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. -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> +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93547 False 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\Printers\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: DisableWebPnPDownload +Value Name: RequireSignOrSeal -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DisableWebPnPDownload + RequireSignOrSeal Dword - - <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 will prevent uncontrolled updates to the system. + + <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. -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> +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93549 False 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\Printers\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: DisableHTTPPrinting +Value Name: SealSecureChannel -Type: REG_DWORD +Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DisableHTTPPrinting + SealSecureChannel Dword - - <VulnDiscussion>Enabling interaction with the network selection UI allows users to change connections to available networks without signing in to Windows.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93551 False - Verify the registry value below. If it does not exist or is not configured as specified, this is a finding. + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: DontDisplayNetworkSelectionUI +Value Name: SignSecureChannel Value Type: REG_DWORD Value: 0x00000001 (1) 1 - DontDisplayNetworkSelectionUI + SignSecureChannel Dword - - <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 will prevent uncontrolled updates to the system. + + <VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. -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></IAControls> +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AppCompat + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93553 False 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\AppCompat\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: DisableInventory +Value Name: RequireStrongKey -Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_DWORD +Value: 0x00000001 (1) + +This setting may prevent a system from being joined to a domain if not configured consistently between systems. 1 - DisableInventory + RequireStrongKey Dword - - <VulnDiscussion>Windows Defender SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + V-93555 False - This is applicable to unclassified systems; for other systems, this is NA. - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -Value Name: EnableSmartScreen +Value Name: RequireSecuritySignature Value Type: REG_DWORD Value: 0x00000001 (1) 1 - EnableSmartScreen + RequireSecuritySignature Dword - - <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + V-93557 False - The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. + 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\Internet Explorer\Feeds\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ -Value Name: AllowBasicAuthInClear +Value Name: EnableSecuritySignature Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - 0 - AllowBasicAuthInClear +Value: 0x00000001 (1) + 1 + EnableSecuritySignature Dword - - <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></IAControls> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + V-93559 False 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\Windows Search\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Value Name: AllowIndexingEncryptedStoresOrItems +Value Name: RequireSecuritySignature Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowIndexingEncryptedStoresOrItems +Value: 0x00000001 (1) + 1 + RequireSecuritySignature Dword - - <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></IAControls> + + <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. + +Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + V-93561 False - This applies to member servers. For domain controllers and standalone systems, this is NA. - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ -Value Name: EnumerateLocalUsers +Value Name: EnableSecuritySignature -Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EnumerateLocalUsers +Value Type: REG_DWORD +Value: 0x00000001 (1) + 1 + EnableSecuritySignature Dword - - <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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Data Execution Prevention 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + V-93563 False - If the following registry value does not exist or is not configured as specified, this is a finding: + The default behavior is for Data Execution Prevention to be turned on for File Explorer. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -Value Name: DisablePasswordSaving +Value Name: NoDataExecutionPrevention -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - DisablePasswordSaving +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) + 0 + NoDataExecutionPrevention Dword - - <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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy + V-93511 False 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\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ -Value Name: fPromptForPassword +Value Name: Enabled -Type: REG_DWORD -Value: 0x00000001 (1) +Value Type: REG_DWORD +Value: 0x00000001 (1) + +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; otherwise. the browser will not be able to connect to a secure site. 1 - fPromptForPassword + Enabled Dword - - <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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters + V-93233 False 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\WinRM\Service\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ -Value Name: DisableRunAs +Value Name: DisableIPSourceRouting Type: REG_DWORD -Value: 0x00000001 (1) - 1 - DisableRunAs +Value: 0x00000002 (2) + 2 + DisableIPSourceRouting Dword - - <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. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters + V-93235 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ -Value Name: FilterAdministratorToken +Value Name: DisableIPSourceRouting Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - FilterAdministratorToken +Value: 0x00000002 (2) + 2 + DisableIPSourceRouting Dword - - <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via the 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters + V-93237 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ -Value Name: ConsentPromptBehaviorUser +Value Name: EnableICMPRedirect Value Type: REG_DWORD Value: 0x00000000 (0) 0 - ConsentPromptBehaviorUser + EnableICMPRedirect Dword - - <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC. - -Satisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper access.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation + V-93239 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation\ -Value Name: EnableLUA +Value Name: AllowInsecureGuestAuth -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - EnableLUA +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + AllowInsecureGuestAuth Dword - - <VulnDiscussion>Unauthenticated RPC clients may allow anonymous access to sensitive information. 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> + + <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Rpc + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths + V-93241.a False - This applies to member servers and standalone systems, it is NA for domain controllers. - -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\Rpc\ - -Value Name: RestrictRemoteClients - -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - RestrictRemoteClients - Dword + Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ +Value Type: REG_SZ +Value Name: \\*\NETLOGON +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + RequireMutualAuthentication=1, RequireIntegrity=1 + \\*\NETLOGON + String - - <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 the 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> + + <VulnDiscussion>Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths + V-93241.b False - 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\Services\Netlogon\Parameters\ - -Value Name: DisablePasswordChange - -Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - DisablePasswordChange - Dword + Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\ +Value Type: REG_SZ +Value Name: \\*\SYSVOL +Value: RequireMutualAuthentication=1, RequireIntegrity=1 + RequireMutualAuthentication=1, RequireIntegrity=1 + \\*\SYSVOL + String - - <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 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></IAControls> + + <VulnDiscussion>An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of non-exportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation + V-93243 False 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\Lsa\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\ -Value Name: NoLMHash +Value Name: AllowProtectedCreds -Value Type: REG_DWORD +Type: REG_DWORD Value: 0x00000001 (1) 1 - NoLMHash + AllowProtectedCreds Dword - - <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 determine 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> + + <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard + V-93245.a False - 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\Services\LanmanWorkstation\Parameters\ - -Value Name: EnablePlainTextPassword - -Value Type: REG_DWORD -Value: 0x00000000 (0) - 0 - EnablePlainTextPassword + Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ +Value Type: REG_DWORD +Value Name: EnableVirtualizationBasedSecurity +Value: 0x00000001 (1) + 1 + EnableVirtualizationBasedSecurity Dword - - <VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. - -The cornerstone of the PKI is the private key used to encrypt or digitally sign information. - -If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. - -Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography - False - - 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\Cryptography\ - -Value Name: ForceKeyProtection - -Type: REG_DWORD -Value: 0x00000002 (2) - 2 - ForceKeyProtection + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard + V-93245.b + True + '{0}' -match '1|3' + Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ +Value Type: REG_DWORD +Value Name: RequirePlatformSecurityFeatures +Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection) + + RequirePlatformSecurityFeatures Dword - - <VulnDiscussion>Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption. - -Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Compromised boot drivers can introduce malware prior to 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters - False - - If the following registry value does not exist or is not configured as specified, this is a finding: + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\EarlyLaunch + V-93249 + True + '{0}' -match '1|3|8|ShouldBeAbsent' + The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad"). + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000007 (7)", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\ -Value Name: SupportedEncryptionTypes +Value Name: DriverLoadPolicy Value Type: REG_DWORD -Value: 0x7ffffff8 (2147483640) - 2147483640 - SupportedEncryptionTypes +Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist) + +Possible values for this setting are: +8 - Good only +1 - Good and unknown +3 - Good, unknown and bad but critical +7 - All (which includes "bad" and would be a finding) + + DriverLoadPolicy Dword - - <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. - -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2} + V-93251 False 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\WinRM\Client\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\ -Value Name: AllowUnencryptedTraffic +Value Name: NoGPOListChanges Type: REG_DWORD Value: 0x00000000 (0) 0 - AllowUnencryptedTraffic + NoGPOListChanges Dword - - <VulnDiscussion>Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this. - -Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51 + V-93253 False 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\WinRM\Service\ +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ -Value Name: AllowUnencryptedTraffic +Value Name: DCSettingIndex Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowUnencryptedTraffic +Value: 0x00000001 (1) + 1 + DCSettingIndex Dword - - <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51 + V-93255 False 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\WinRM\Client\ +Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\ -Value Name: AllowBasic +Value Name: ACSettingIndex Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowBasic +Value: 0x00000001 (1) + 1 + ACSettingIndex Dword - - <VulnDiscussion>Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks. Disallowing Digest authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "Security" option for Telemetry configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and telemetry client settings. "Basic" sends basic diagnostic and usage data and may be required to support some Microsoft services.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Client - False - + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection + V-93257 + True + '{0}' -match '0|1' 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\WinRM\Client\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DataCollection\ -Value Name: AllowDigest +Value Name: AllowTelemetry Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowDigest +Value: 0x00000000 (0) (Security), 0x00000001 (1) (Basic) + + AllowTelemetry Dword - - <VulnDiscussion>Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the Internet. This is part of the Windows Update trusted process, however to minimize outside exposure, obtaining updates from or sending to systems on the Internet must be prevented.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WinRM\Service - False - + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization + V-93259 + True + '{0}' -match '0|1|2|99|100' 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\WinRM\Service\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\ -Value Name: AllowBasic +Value Name: DODownloadMode -Type: REG_DWORD -Value: 0x00000000 (0) - 0 - AllowBasic +Value Type: REG_DWORD +Value: 0x00000000 (0) - No peering (HTTP Only) +0x00000001 (1) - Peers on same NAT only (LAN) +0x00000002 (2) - Local Network / Private group peering (Group) +0x00000063 (99) - Simple download mode, no peering (Simple) +0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass) + +A value of 0x00000003 (3), Internet, is a finding. + + DODownloadMode Dword - - <VulnDiscussion>This setting ensures 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></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + V-93261 False - If the following registry value does not exist or is not configured as specified, this is a finding: + The default behavior is for File Explorer heap termination on corruption to be enabled. + +If the registry Value Name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\ -Value Name: Enabled +Value Name: NoHeapTerminationOnCorruption Value Type: REG_DWORD -Value: 0x00000001 (1) - -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; otherwise. the browser will not be able to connect to a secure site. - 1 - Enabled +Value: 0x00000000 (0) (or if the Value Name does not exist) + 0 + NoHeapTerminationOnCorruption Dword - - <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></IAControls> + + <VulnDiscussion>The shell protocol will limit the set of folders that 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + V-93263 False - If the following registry value does not exist or is not configured as specified, this is a finding: + The default behavior is for shell protected mode to be turned on for File Explorer. + +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\ -Value Name: EnumerateAdministrators +Value Name: PreXPSP2ShellProtocolBehavior -Type: REG_DWORD -Value: 0x00000000 (0) +Value Type: REG_DWORD +Value: 0x00000000 (0) (or if the Value Name does not exist) 0 - EnumerateAdministrators + PreXPSP2ShellProtocolBehavior Dword - - - <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 local 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></IAControls> + + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds + V-93265 False - This applies to member servers. For domain controllers and standalone systems, 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 + If the following registry value does not exist or is not configured as specified, this is a finding: -Value Name: LocalAccountTokenFilterPolicy +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\ -Type: REG_DWORD -Value: 0x00000000 (0) +Value Name: DisableEnclosureDownload -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. - 0 - LocalAccountTokenFilterPolicy +Type: REG_DWORD +Value: 0x00000001 (1) + 1 + DisableEnclosureDownload Dword - - <VulnDiscussion>User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer + V-93267 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system. -If the following registry value does not exist or is not configured as specified, this is a finding: +If the registry value name below does not exist, this is not a finding. + +If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\ -Value Name: EnableUIADesktopToggle +Value Name: SafeForScripting Value Type: REG_DWORD -Value: 0x00000000 (0) +Value: 0x00000000 (0) (or if the Value Name does not exist) 0 - EnableUIADesktopToggle + SafeForScripting Dword - - <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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon + V-93275 True - '{0}' -match '1|2' - UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience). + '{0}' -le '4' + This applies to member servers. For domain controllers and standalone systems, 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\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ -Value Name: ConsentPromptBehaviorAdmin +Value Name: CachedLogonsCount -Value Type: REG_DWORD -Value: 0x00000002 (2) (Prompt for consent on the secure desktop) -0x00000001 (1) (Prompt for credentials on the secure desktop) +Value Type: REG_SZ +Value: 4 (or less) - ConsentPromptBehaviorAdmin - Dword + CachedLogonsCount + String - - <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></IAControls> + + <VulnDiscussion>Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. This authentication information, which was stored in the Local Security Authority (LSA) in previous versions of Windows, is isolated from the rest of operating system and can only be accessed by privileged system software.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard + V-93277 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + For domain controllers and standalone systems, this is NA. -If the following registry value does not exist or is not configured as specified, this is a finding: +Current hardware and virtual environments may not support virtualization-based security features, including Credential Guard, due to specific supporting requirements, including a TPM, UEFI with Secure Boot, and the capability to run the Hyper-V feature within a virtual machine. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ +Open "PowerShell" with elevated privileges (run as administrator). -Value Name: EnableInstallerDetection +Enter the following: + +"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard" + +If "SecurityServicesRunning" does not include a value of "1" (e.g., "{1, 2}"), this is a finding. + +Alternately: + +Run "System Information". + +Under "System Summary", verify the following: + +If "Device Guard Security Services Running" does not list "Credential Guard", this is a finding. + +The policy settings referenced in the Fix section will configure the following registry value. However, due to hardware requirements, the registry value alone does not ensure proper function. + +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\ +Value Name: LsaCfgFlags Value Type: REG_DWORD -Value: 0x00000001 (1) +Value: 0x00000001 (1) (Enabled with UEFI lock) + +A Microsoft article on Credential Guard system requirement can be found at the following link: + +https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements 1 - EnableInstallerDetection + LsaCfgFlags Dword - - <VulnDiscussion>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> + + <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 does 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93279 False - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). - -If the following registry value does not exist or is not configured as specified, this is a finding: + 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\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: EnableSecureUIAPaths +Value Name: LimitBlankPasswordUse Value Type: REG_DWORD Value: 0x00000001 (1) 1 - EnableSecureUIAPaths + LimitBlankPasswordUse Dword - - <VulnDiscussion>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></IAControls> + + <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 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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System - False - - UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience). + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + V-93285 + True + '{0}' -le '30' -and '{0}' -gt '0' + This is the default configuration for this setting (30 days). 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\ +Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\ -Value Name: EnableVirtualization +Value Name: MaximumPasswordAge Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - EnableVirtualization +Value: 0x0000001e (30) (or less, but not 0) + + MaximumPasswordAge Dword - - <VulnDiscussion>Preventing users from sharing the local drives on their client computers with 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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services - False - + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon + V-93287 + True + '{0}' -match '1|2' 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\ +Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ -Value Name: fDisableCdm +Value Name: scremoveoption -Type: REG_DWORD -Value: 0x00000001 (1) - 1 - fDisableCdm - Dword +Value Type: REG_SZ +Value: 1 (Lock Workstation) or 2 (Force Logoff) + +If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the ISSO. + + scremoveoption + String - - <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></IAControls> + + <VulnDiscussion>Anonymous enumeration of SAM accounts allows anonymous logon 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></IAControls> Present False HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93291 False If the following registry value does not exist or is not configured as specified, this is a finding: @@ -7213,270 +7610,263 @@ Value: 0x00000001 (1) Registry Hive: HKEY_LOCAL_MACHINE Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: RestrictAnonymous +Value Name: RestrictAnonymousSAM Value Type: REG_DWORD Value: 0x00000001 (1) 1 - RestrictAnonymous + RestrictAnonymousSAM Dword - - <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></IAControls> + + <VulnDiscussion>Access by anonymous users must be restricted. If this setting is enabled, 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93293 False 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\Services\LanManServer\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: RestrictNullSessAccess +Value Name: EveryoneIncludesAnonymous Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - RestrictNullSessAccess +Value: 0x00000000 (0) + 0 + EveryoneIncludesAnonymous Dword - - <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 server's 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> + + <VulnDiscussion>Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netbt\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA + V-93295 False 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\Services\Netbt\Parameters\ +Registry Hive: HKEY_LOCAL_MACHINE +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\ -Value Name: NoNameReleaseOnDemand +Value Name: UseMachineId -Value Type: REG_DWORD -Value: 0x00000001 (1) +Type: REG_DWORD +Value: 0x00000001 (1) 1 - NoNameReleaseOnDemand + UseMachineId Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\MSV1_0 + V-93297 False 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\ -Value Name: RequireSignOrSeal +Value Name: allownullsessionfallback -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - RequireSignOrSeal +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + allownullsessionfallback Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\pku2u + V-93299 False 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\pku2u\ -Value Name: SealSecureChannel +Value Name: AllowOnlineID -Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - SealSecureChannel +Type: REG_DWORD +Value: 0x00000000 (0) + 0 + AllowOnlineID Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 standalone 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></IAControls> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa + V-93301 False 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\ -Value Name: SignSecureChannel +Value Name: LmCompatibilityLevel Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - SignSecureChannel +Value: 0x00000005 (5) + 5 + LmCompatibilityLevel Dword - - - <VulnDiscussion>A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + + <VulnDiscussion>This setting controls the signing requirements for LDAP clients. This 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LDAP + V-93303 False 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\Services\Netlogon\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Services\LDAP\ -Value Name: RequireStrongKey +Value Name: LDAPClientIntegrity Value Type: REG_DWORD -Value: 0x00000001 (1) - -This setting may prevent a system from being joined to a domain if not configured consistently between systems. +Value: 0x00000001 (1) 1 - RequireStrongKey + LDAPClientIntegrity Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 + V-93305 False 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\Services\LanmanWorkstation\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ -Value Name: RequireSecuritySignature +Value Name: NTLMMinClientSec Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - RequireSecuritySignature +Value: 0x20080000 (537395200) + 537395200 + NTLMMinClientSec Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 + V-93307 False 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\Services\LanmanWorkstation\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\ -Value Name: EnableSecuritySignature +Value Name: NTLMMinServerSec Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - EnableSecuritySignature +Value: 0x20080000 (537395200) + 537395200 + NTLMMinServerSec Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <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 Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing non-administrative users to read shared objects but not to modify shared objects 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager + V-93309 False 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\Services\LanManServer\Parameters\ +Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\ -Value Name: RequireSecuritySignature +Value Name: ProtectionMode Value Type: REG_DWORD Value: 0x00000001 (1) 1 - RequireSecuritySignature + ProtectionMode Dword - - <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. - -Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + + <VulnDiscussion>Attachments from outside sources may contain malicious code. 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> Present False - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters + HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments + V-93311 False - If the following registry value does not exist or is not configured as specified, this is a finding: + The default behavior is for Windows to mark file attachments with their zone information. -Registry Hive: HKEY_LOCAL_MACHINE -Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\ +If the registry Value Name below does not exist, this is not a finding. -Value Name: EnableSecuritySignature +If it exists and is configured with a value of "0x00000002 (2) (or if the Value Name does not exist)", this is not a finding. + +If it exists and is configured with a value of "1", this is a finding. + +Registry Hive: HKEY_CURRENT_USER +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\ + +Value Name: SaveZoneInformation Value Type: REG_DWORD -Value: 0x00000001 (1) - 1 - EnableSecuritySignature +Value: 0x00000002 (2) (or if the Value Name does not exist) + 2 + SaveZoneInformation Dword - - <VulnDiscussion>Data Execution Prevention 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></IAControls> + + <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> Present False - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Explorer + HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System + V-93269 False - The default behavior is for Data Execution Prevention to be turned on for File Explorer. - -If the registry value name below does not exist, this is not a finding. - -If it exists and is configured with a value of "0x00000000 (0) (or if the Value Name does not exist)", this is not a finding. - -If it exists and is configured with a value of "1", this is a finding. + 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\Explorer\ +Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ -Value Name: NoDataExecutionPrevention +Value Name: DisableAutomaticRestartSignOn Value Type: REG_DWORD -Value: 0x00000000 (0) (or if the Value Name does not exist) - 0 - NoDataExecutionPrevention +Value: 0x00000001 (1) + 1 + DisableAutomaticRestartSignOn Dword - + <VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. Organizations must disable the Windows Preview pane and Windows Detail pane.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -7484,6 +7874,7 @@ Organizations must disable the Windows Preview pane and Windows Detail pane.< Present False HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + V-102625.a False Registry Hive: HKEY_CURRENT_USER @@ -7495,7 +7886,7 @@ Value: 1 NoPreviewPane Dword - + <VulnDiscussion>A known vulnerability in Windows could allow the execution of malicious code by either opening a compromised document or viewing it in the Windows Preview pane. Organizations must disable the Windows Preview pane and Windows Detail pane.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -7503,6 +7894,7 @@ Organizations must disable the Windows Preview pane and Windows Detail pane.< Present False HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer + V-102625.b False Registry Hive: HKEY_CURRENT_USER @@ -7516,117 +7908,112 @@ Value: 1 - + DoD Root CA 2 <VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93487.a True location for DoD Root CA 2 certificate is present DoD Root CA 2,8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 8C941B34EA1EA6ED9AE2BC54CF687252B4C9B561 - + DoD Root CA 3 <VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93487.b True location for DoD Root CA 3 certificate is present DoD Root CA 3,D73CA91102A2204A36459ED32213B467D7CE97FB D73CA91102A2204A36459ED32213B467D7CE97FB - + DoD Root CA 4 <VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93487.c True location for DoD Root CA 4 certificate is present DoD Root CA 4,B8269F25DBD937ECAFD4C35A9838571723F2D026 B8269F25DBD937ECAFD4C35A9838571723F2D026 - + DoD Root CA 5 <VulnDiscussion>To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93487.d True location for DoD Root CA 5 certificate is present DoD Root CA 5,4ECB5CC3095670454DA1CBD410FC921F46B8564B 4ECB5CC3095670454DA1CBD410FC921F46B8564B - - DoD Interoperability Root CA 1 - <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. - -Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - - True - location for DoD Interoperability Root CA 1 certificate is present - DoD Interoperability Root CA 1,22BBE981F0694D246CC1472ED2B021DC8540A22F - 22BBE981F0694D246CC1472ED2B021DC8540A22F - - + DoD Interoperability Root CA 2 <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. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93489.a True location for DoD Interoperability Root CA 2 certificate is present - DoD Interoperability Root CA 2,FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4 - FCE1B1E25374DD94F5935BEB86CA643D8C8D1FF4 + DoD Interoperability Root CA 2,AC06108CA348CC03B53795C64BF84403C1DBD341 + AC06108CA348CC03B53795C64BF84403C1DBD341 - - DoD Interoperability Root CA 2 + + DoD Interoperability Root CA 1 <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. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93489.b True - location for DoD Interoperability Root CA 2 certificate is present - DoD Interoperability Root CA 2,FFAD03329B9E527A43EEC66A56F9CBB5393E6E13 - FFAD03329B9E527A43EEC66A56F9CBB5393E6E13 + location for DoD Interoperability Root CA 1 certificate is present + DoD Interoperability Root CA 1,A8C27332CCB4CA49554CE55D34062A7DD2850C02 + A8C27332CCB4CA49554CE55D34062A7DD2850C02 - - US DoD CCEB Interoperability Root CA 1 + + US DoD CCEB Interoperability Root CA 2 <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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93491.a True - location for US DoD CCEB Interoperability Root CA 1 certificate is present - US DoD CCEB Interoperability Root CA 1,DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3 - DA36FAF56B2F6FBA1604F5BE46D864C9FA013BA3 + location for US DoD CCEB Interoperability Root CA 2 certificate is present + US DoD CCEB Interoperability Root CA 2,AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 + AF132AC65DE86FC4FB3FE51FD637EBA0FF0B12A9 - + US DoD CCEB Interoperability Root CA 2 <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-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems. Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False + V-93491.b True location for US DoD CCEB Interoperability Root CA 2 certificate is present @@ -7635,10 +8022,11 @@ Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182</VulnDiscussion - + <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> False + V-93289 Network access: Allow anonymous SID/Name translation Disabled False @@ -7651,83 +8039,103 @@ Navigate to Local Computer Policy >> Computer Configuration >> Windo If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding. - - <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> + + <VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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> False - Accounts: Rename administrator account - - True - '{0}' -ne 'Administrator' + V-93497 + Accounts: Guest account status + Disabled + False + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. +If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. - - <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> + + <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> False - Accounts: Rename guest account + V-93281 + Accounts: Rename administrator account True - '{0}' -ne 'Guest' + '{0}' -ne 'Administrator' Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. +If the value for "Accounts: Rename administrator account" is not set to a value other than "Administrator", this is a finding. - - <VulnDiscussion>A system faces an increased vulnerability threat if the built-in guest account is not disabled. This 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> + + <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> False - Accounts: Guest account status - Disabled - False - + V-93283 + Accounts: Rename guest account + + True + '{0}' -ne 'Guest' Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options. -If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding. +If the value for "Accounts: Rename guest account" is not set to a value other than "Guest", this is a finding. - + <VulnDiscussion>Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Present False + V-93217 True ServiceName/StartupType is populated with correct AntiVirus service information Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution. -If there is no anti-virus solution installed on the system, this is a finding. +If there is no anti-virus solution installed on the system, this is a finding. + +Verify if Windows Defender is in use or enabled: + +Open "PowerShell". + +Enter “get-service | where {$_.DisplayName -Like "*Defender*"} | Select Status,DisplayName” + +Verify if third-party anti-virus is in use or enabled: + +Open "PowerShell". + +Enter "get-service | where {$_.DisplayName -Like "*mcafee*"} | Select Status,DisplayName” + +Enter "get-service | where {$_.DisplayName -Like "*symantec*"} | Select Status,DisplayName” + Running - + <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></IAControls> Present False + V-93571 True ServiceName/StartupType is populated with correct Firewall service information Determine if a host-based firewall is installed and enabled on the system. @@ -7743,45 +8151,34 @@ The configuration requirements will be determined by the applicable firewall STI - - SeDenyRemoteInteractiveLogonRight + + SeSecurityPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. -The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. - -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. +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. -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> - Deny log on through Remote Desktop Services +Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + Manage auditing and security log - False - Enterprise Admins,Domain Admins,Local account,Guests + True + Administrators False + V-93197 False - This applies to member servers and standalone systems. A separate version applies to domain controllers. - -Verify the effective setting in Local Group Policy Editor. + Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. -If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: - -Domain Systems Only: -- Enterprise Admins group -- Domain Admins group -- Local account (see Note below) +If any accounts or groups other than the following are granted the "Manage auditing and security log" user right, this is a finding. -All Systems: -- Guests group +- Administrators - + SeNetworkLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -7791,6 +8188,7 @@ Accounts with the "Access this computer from the network" user right may access True Administrators,Authenticated Users False + V-93007 False This applies to member servers and standalone systems. A separate version applies to domain controllers. @@ -7808,7 +8206,7 @@ If any accounts or groups other than the following are granted the "Access this - + SeDenyNetworkLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -7824,6 +8222,7 @@ The Guests group must be assigned this right to prevent unauthenticated access.& False False + V-93009 True '{0}' -match 'Enterprise Admins,Domain Admins,(Local account and member of Administrators group|Local account),Guests' This applies to member servers and standalone systems. A separate version applies to domain controllers. @@ -7846,7 +8245,7 @@ All Systems: - + SeDenyBatchLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -7860,6 +8259,7 @@ The Guests group must be assigned to prevent unauthenticated access.</VulnDis False Enterprise Admins,Domain Admins,Guests False + V-93011 False This applies to member servers and standalone systems. A separate version applies to domain controllers. @@ -7881,7 +8281,7 @@ All Systems: - + SeDenyServiceLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -7895,6 +8295,7 @@ Incorrect configurations could prevent services from starting and result in a de True Enterprise Admins,Domain Admins False + V-93013 False This applies to member servers and standalone systems. A separate version applies to domain controllers. @@ -7914,7 +8315,7 @@ If any accounts or groups are defined for the "Deny log on as a service" user ri - + SeDenyInteractiveLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -7928,6 +8329,7 @@ The Guests group must be assigned this right to prevent unauthenticated access.& False Enterprise Admins,Domain Admins,Guests False + V-93015 False This applies to member servers and standalone systems. A separate version applies to domain controllers. @@ -7949,7 +8351,7 @@ All Systems: - + SeInteractiveLogonRight <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -7959,6 +8361,7 @@ Accounts with the "Allow log on locally" user right can log on interactively to True Administrators False + V-93017 False Verify the effective setting in Local Group Policy Editor. @@ -7973,7 +8376,46 @@ If any accounts or groups other than the following are granted the "Allow log on - + + SeDenyRemoteInteractiveLogonRight + <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. + +The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services. + +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> + Deny log on through Remote Desktop Services + + False + Enterprise Admins,Domain Admins,Local account,Guests + False + V-92965 + False + + This applies to member servers and standalone systems. A separate version applies to domain controllers. + +Verify the effective setting in Local Group Policy Editor. + +Run "gpedit.msc". + +Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. + +If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding: + +Domain Systems Only: +- Enterprise Admins group +- Domain Admins group +- Local account (see Note below) + +All Systems: +- Guests group + + + + SeEnableDelegationPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -7983,6 +8425,7 @@ The "Enable computer and user accounts to be trusted for delegation" user right True NULL False + V-93047 False This applies to member servers and standalone systems. A separate version applies to domain controllers. @@ -7997,7 +8440,7 @@ If any accounts or groups are granted the "Enable computer and user accounts to - + SeTrustedCredManAccessPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8007,6 +8450,7 @@ Accounts with the "Access Credential Manager as a trusted caller" user right may True NULL False + V-93049 False Verify the effective setting in Local Group Policy Editor. @@ -8019,7 +8463,7 @@ If any accounts or groups are granted the "Access Credential Manager as a truste - + SeTcbPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8029,6 +8473,7 @@ Accounts with the "Act as part of the operating system" user right can assume th True NULL False + V-93051 False Verify the effective setting in Local Group Policy Editor. @@ -8041,7 +8486,7 @@ If any accounts or groups (to include administrators), are granted the "Act as p - + SeBackupPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8051,6 +8496,7 @@ Accounts with the "Back up files and directories" user right can circumvent file True Administrators False + V-93053 False Verify the effective setting in Local Group Policy Editor. @@ -8065,7 +8511,7 @@ If any accounts or groups other than the following are granted the "Back up file - + SeCreatePagefilePrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8075,6 +8521,7 @@ Accounts with the "Create a pagefile" user right can change the size of a pagefi True Administrators False + V-93055 False Verify the effective setting in Local Group Policy Editor. @@ -8089,7 +8536,7 @@ If any accounts or groups other than the following are granted the "Create a pag - + SeCreateTokenPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8099,6 +8546,7 @@ The "Create a token object" user right allows a process to create an access toke True NULL False + V-93057 False Verify the effective setting in Local Group Policy Editor. @@ -8111,7 +8559,7 @@ If any accounts or groups are granted the "Create a token object" user right, th - + SeCreateGlobalPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8121,6 +8569,7 @@ Accounts with the "Create global objects" user right can create objects that are True Administrators,Service,Local Service,Network Service False + V-93059 False Verify the effective setting in Local Group Policy Editor. @@ -8138,7 +8587,7 @@ If any accounts or groups other than the following are granted the "Create globa - + SeCreatePermanentPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8148,6 +8597,7 @@ Accounts with the "Create permanent shared objects" user right could expose sens True NULL False + V-93061 False Verify the effective setting in Local Group Policy Editor. @@ -8160,7 +8610,7 @@ If any accounts or groups are granted the "Create permanent shared objects" user - + SeCreateSymbolicLinkPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8170,6 +8620,7 @@ Accounts with the "Create symbolic links" user right can create pointers to othe True False + V-93063 True '{0}' -match '^(Administrators,NT Virtual Machine\\Virtual Machines|Administrators)$' Verify the effective setting in Local Group Policy Editor. @@ -8184,7 +8635,7 @@ If any accounts or groups other than the following are granted the "Create symbo - + SeDebugPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8194,6 +8645,7 @@ Accounts with the "Debug programs" user right can attach a debugger to any proce True Administrators False + V-93065 False Verify the effective setting in Local Group Policy Editor. @@ -8208,7 +8660,7 @@ If any accounts or groups other than the following are granted the "Debug progra - + SeRemoteShutdownPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8218,6 +8670,7 @@ Accounts with the "Force shutdown from a remote system" user right can remotely True Administrators False + V-93067 False Verify the effective setting in Local Group Policy Editor. @@ -8232,7 +8685,7 @@ If any accounts or groups other than the following are granted the "Force shutdo - + SeAuditPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8242,6 +8695,7 @@ The "Generate security audits" user right specifies users and processes that can True Local Service,Network Service False + V-93069 False Verify the effective setting in Local Group Policy Editor. @@ -8257,7 +8711,7 @@ If any accounts or groups other than the following are granted the "Generate sec - + SeImpersonatePrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8267,6 +8721,7 @@ The "Impersonate a client after authentication" user right allows a program to i True Administrators,Service,Local Service,Network Service False + V-93071 False Verify the effective setting in Local Group Policy Editor. @@ -8284,7 +8739,7 @@ If any accounts or groups other than the following are granted the "Impersonate - + SeIncreaseBasePriorityPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8294,6 +8749,7 @@ Accounts with the "Increase scheduling priority" user right can change a schedul True Administrators False + V-93073 False Verify the effective setting in Local Group Policy Editor. @@ -8308,7 +8764,7 @@ If any accounts or groups other than the following are granted the "Increase sch - + SeLoadDriverPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8318,6 +8774,7 @@ The "Load and unload device drivers" user right allows a user to load device dri True Administrators False + V-93075 False Verify the effective setting in Local Group Policy Editor. @@ -8332,7 +8789,7 @@ If any accounts or groups other than the following are granted the "Load and unl - + SeLockMemoryPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8342,6 +8799,7 @@ The "Lock pages in memory" user right allows physical memory to be assigned to p True NULL False + V-93077 False Verify the effective setting in Local Group Policy Editor. @@ -8354,7 +8812,7 @@ If any accounts or groups are granted the "Lock pages in memory" user right, thi - + SeSystemEnvironmentPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8364,6 +8822,7 @@ Accounts with the "Modify firmware environment values" user right can change har True Administrators False + V-93079 False Verify the effective setting in Local Group Policy Editor. @@ -8378,7 +8837,7 @@ If any accounts or groups other than the following are granted the "Modify firmw - + SeManageVolumePrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8388,6 +8847,7 @@ Accounts with the "Perform volume maintenance tasks" user right can manage volum True Administrators False + V-93081 False Verify the effective setting in Local Group Policy Editor. @@ -8402,7 +8862,7 @@ If any accounts or groups other than the following are granted the "Perform volu - + SeProfileSingleProcessPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8412,6 +8872,7 @@ Accounts with the "Profile single process" user right can monitor non-system pro True Administrators False + V-93083 False Verify the effective setting in Local Group Policy Editor. @@ -8426,7 +8887,7 @@ If any accounts or groups other than the following are granted the "Profile sing - + SeRestorePrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8436,6 +8897,7 @@ Accounts with the "Restore files and directories" user right can circumvent file True Administrators False + V-93085 False Verify the effective setting in Local Group Policy Editor. @@ -8450,7 +8912,7 @@ If any accounts or groups other than the following are granted the "Restore file - + SeTakeOwnershipPrivilege <VulnDiscussion>Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. @@ -8460,6 +8922,7 @@ Accounts with the "Take ownership of files or other objects" user right can take True Administrators False + V-93087 False Verify the effective setting in Local Group Policy Editor. @@ -8472,41 +8935,16 @@ If any accounts or groups other than the following are granted the "Take ownersh - Administrators - - - - SeSecurityPrivilege - <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. - -Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - Manage auditing and security log - - True - Administrators - False - False - - Verify the effective setting in Local Group Policy Editor. - -Run "gpedit.msc". - -Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> 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. - -- Administrators - - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93383 Fax False @@ -8518,11 +8956,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93385 PNRP False @@ -8534,11 +8973,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93387 Simple-TCPIP False @@ -8550,11 +8990,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93389 TFTP-Client False @@ -8566,11 +9007,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Absent False + V-93391 FS-SMB1 False @@ -8584,11 +9026,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Absent False + V-93397 PowerShell-v2 False @@ -8600,11 +9043,12 @@ If "Installed State" is "Installed", this is a finding. An Installed State of "Available" or "Removed" is not a finding. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> Absent False + V-93421 Web-Ftp-Service False @@ -8620,11 +9064,12 @@ An Installed State of "Available" or "Removed" is not a finding. If the system has the role of an FTP server, this must be documented with the ISSO. - + <VulnDiscussion>Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access 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> Absent False + V-93423 Telnet-Client False