{"stig":{"title":"Microsoft Windows Server 2019 Security Technical Implementation Guide","version":"3","release":"8"},"checks":[{"vulnId":"V-205624","ruleId":"SV-205624r958364_rule","severity":"medium","ruleTitle":"Windows Server 2019 must automatically remove or disable temporary user accounts after 72 hours.","description":"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.\n\nTemporary 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.\n\nIf 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.\n\nTo address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.","checkContent":"Review temporary user accounts for expiration dates.\n\nDetermine if temporary user accounts are used and identify any that exist. If none exist, this is NA.\n\nDomain Controllers:\n\nOpen \"PowerShell\".\n\nEnter \"Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate\".\n\nIf \"AccountExpirationDate\" has not been defined within 72 hours for any temporary user account, this is a finding.\n\nMember servers and standalone or nondomain-joined systems:\n\nOpen \"Command Prompt\".\n\nRun \"Net user [username]\", where [username] is the name of the temporary user account.\n\nIf \"Account expires\" has not been defined within 72 hours for any temporary user account, this is a finding.","fixText":"Configure temporary user accounts to automatically expire within 72 hours.\n\nDomain accounts can be configured with an account expiration date, under \"Account\" properties.\n\nLocal 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.\n\nDelete any temporary user accounts that are no longer necessary.","ccis":["CCI-000016"]},{"vulnId":"V-205625","ruleId":"SV-205625r958368_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Account Management - Security Group Management successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSecurity Group Management records events such as creating, deleting, or changing security groups, including changes in group members.\n\nSatisfies: 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","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nAccount Management >> Security Group Management - Success","fixText":"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.","ccis":["CCI-000018","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-002130"]},{"vulnId":"V-205626","ruleId":"SV-205626r958368_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Account Management - User Account Management successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nUser Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.\n\nSatisfies: 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","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nAccount Management >> User Account Management - Success","fixText":"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.","ccis":["CCI-000018","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-002130"]},{"vulnId":"V-205627","ruleId":"SV-205627r958368_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Account Management - User Account Management failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nUser Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.\n\nSatisfies: 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","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nAccount Management >> User Account Management - Failure","fixText":"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.","ccis":["CCI-000018","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-002130"]},{"vulnId":"V-205628","ruleId":"SV-205628r958368_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Account Management - Computer Account Management successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nComputer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts.\n\nSatisfies: 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","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nSecurity Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nAccount Management >> Computer Account Management - Success","fixText":"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.","ccis":["CCI-000018","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-002130"]},{"vulnId":"V-205629","ruleId":"SV-205629r958388_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the number of allowed bad logon attempts configured to three or less.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy.\n\nIf the \"Account lockout threshold\" is \"0\" or more than \"3\" attempts, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"LockoutBadCount\" equals \"0\" or is greater than \"3\" in the file, this is a finding.","fixText":"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).","ccis":["CCI-000044"]},{"vulnId":"V-205630","ruleId":"SV-205630r958388_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.","description":"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.\n\nSatisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy.\n\nIf the \"Reset account lockout counter after\" value is less than \"15\" minutes, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"ResetLockoutCount\" is less than \"15\" in the file, this is a finding.","fixText":"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.","ccis":["CCI-000044","CCI-002238"]},{"vulnId":"V-205631","ruleId":"SV-205631r958390_rule","severity":"medium","ruleTitle":"Windows Server 2019 required legal notice must be configured to display before console logon.","description":"Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.\n\nSatisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, SRG-OS-000228-GPOS-00088","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: LegalNoticeText\n\nValue Type: REG_SZ\nValue: See message text below\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.","fixText":"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:\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-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.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-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.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-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.","ccis":["CCI-000048","CCI-000050","CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-205632","ruleId":"SV-205632r958390_rule","severity":"low","ruleTitle":"Windows Server 2019 title for legal banner dialog box must be configured with the appropriate text.","description":"Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.\n\nSatisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: LegalNoticeCaption\n\nValue Type: REG_SZ\nValue: Refer to message title options below\n\n\"DoD Notice and Consent Banner\", \"US Department of Defense Warning Statement\", or an organization-defined equivalent. \n\nIf an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN19-SO-000130.\n\nAutomated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required.","fixText":"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. \n\nIf an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN19-SO-000130.","ccis":["CCI-000048","CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-205633","ruleId":"SV-205633r958400_rule","severity":"medium","ruleTitle":"Windows Server 2019 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver.","description":"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.\n\nSatisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: InactivityTimeoutSecs\n\nValue Type: REG_DWORD\nValue: 0x00000384 (900) (or less, excluding \"0\" which is effectively disabled)","fixText":"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.","ccis":["CCI-000056","CCI-000057","CCI-000060"]},{"vulnId":"V-205634","ruleId":"SV-205634r958406_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit logon successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nLogon 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.\n\nSatisfies: 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","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nLogon/Logoff >> Logon - Success","fixText":"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.","ccis":["CCI-000067","CCI-000172"]},{"vulnId":"V-205635","ruleId":"SV-205635r958406_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit logon failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nLogon 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.\n\nSatisfies: 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","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nLogon/Logoff >> Logon - Failure","fixText":"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.","ccis":["CCI-000067","CCI-000172"]},{"vulnId":"V-205636","ruleId":"SV-205636r958408_rule","severity":"medium","ruleTitle":"Windows Server 2019 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.","description":"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.\n\nSatisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows NT\\Terminal Services\\\n\nValue Name: fEncryptRPCTraffic\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000068","CCI-001453"]},{"vulnId":"V-205637","ruleId":"SV-205637r958408_rule","severity":"medium","ruleTitle":"Windows Server 2019 Remote Desktop Services must be configured with the client connection encryption set to High Level.","description":"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.\n\nSatisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows NT\\Terminal Services\\\n\nValue Name: MinEncryptionLevel\n\nType: REG_DWORD\nValue: 0x00000003 (3)","fixText":"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.","ccis":["CCI-000068","CCI-001453"]},{"vulnId":"V-205638","ruleId":"SV-205638r958422_rule","severity":"medium","ruleTitle":"Windows Server 2019 command line data must be included in process creation events.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nEnabling \"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Audit\\\n\nValue Name: ProcessCreationIncludeCmdLine_Enabled\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Audit Process Creation >> \"Include command line in process creation events\" to \"Enabled\".","ccis":["CCI-000135"]},{"vulnId":"V-205639","ruleId":"SV-205639r958422_rule","severity":"medium","ruleTitle":"Windows Server 2019 PowerShell script block logging must be enabled.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nEnabling 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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\PowerShell\\ScriptBlockLogging\\\n\nValue Name: EnableScriptBlockLogging\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> \"Turn on PowerShell Script Block Logging\" to \"Enabled\".","ccis":["CCI-000135"]},{"vulnId":"V-205640","ruleId":"SV-205640r958434_rule","severity":"medium","ruleTitle":"Windows Server 2019 permissions for the Application event log must prevent access by non-privileged accounts.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have 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.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029","checkContent":"Navigate to the Application event log file.\n\nThe default location is the \"%SystemRoot%\\System32\\winevt\\Logs\" folder. However, the logs may have been moved to another folder.\n\nIf the permissions for the \"Application.evtx\" file are not as restrictive as the default permissions listed below, this is a finding:\n\nEventlog - Full Control\nSYSTEM - Full Control\nAdministrators - Full Control","fixText":"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:\n\nEventlog - Full Control\nSYSTEM - Full Control\nAdministrators - Full Control\n\nThe default location is the \"%SystemRoot%\\System32\\winevt\\Logs\" folder.\n\nIf the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as \"NT Service\\Eventlog\".","ccis":["CCI-000162","CCI-000163","CCI-000164"]},{"vulnId":"V-205641","ruleId":"SV-205641r958434_rule","severity":"medium","ruleTitle":"Windows Server 2019 permissions for the Security event log must prevent access by non-privileged accounts.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have 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.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029","checkContent":"Navigate to the Security event log file.\n\nThe default location is the \"%SystemRoot%\\System32\\winevt\\Logs\" folder. However, the logs may have been moved to another folder.\n\nIf the permissions for the \"Security.evtx\" file are not as restrictive as the default permissions listed below, this is a finding:\n\nEventlog - Full Control\nSYSTEM - Full Control\nAdministrators - Full Control","fixText":"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:\n\nEventlog - Full Control\nSYSTEM - Full Control\nAdministrators - Full Control\n\nThe default location is the \"%SystemRoot%\\System32\\winevt\\Logs\" folder.\n\nIf the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as \"NT Service\\Eventlog\".","ccis":["CCI-000162","CCI-000163","CCI-000164"]},{"vulnId":"V-205642","ruleId":"SV-205642r958434_rule","severity":"medium","ruleTitle":"Windows Server 2019 permissions for the System event log must prevent access by non-privileged accounts.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have 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.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029","checkContent":"Navigate to the System event log file.\n\nThe default location is the \"%SystemRoot%\\System32\\winevt\\Logs\" folder. However, the logs may have been moved to another folder.\n\nIf the permissions for the \"System.evtx\" file are not as restrictive as the default permissions listed below, this is a finding:\n\nEventlog - Full Control\nSYSTEM - Full Control\nAdministrators - Full Control","fixText":"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:\n\nEventlog - Full Control\nSYSTEM - Full Control\nAdministrators - Full Control\n\nThe default location is the \"%SystemRoot%\\System32\\winevt\\Logs\" folder.\n\nIf the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as \"NT Service\\Eventlog\".","ccis":["CCI-000162","CCI-000163","CCI-000164"]},{"vulnId":"V-205643","ruleId":"SV-205643r958434_rule","severity":"medium","ruleTitle":"Windows Server 2019 Manage auditing and security log user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts 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.\n\nSatisfies: 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","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Manage auditing and security log\" user right, this is a finding.\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeSecurityPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\n\nIf the organization has an Auditors group, the assignment of this group to the user right would not be a finding.\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators","ccis":["CCI-000162","CCI-000163","CCI-000164","CCI-000171","CCI-001914"]},{"vulnId":"V-205644","ruleId":"SV-205644r958442_rule","severity":"medium","ruleTitle":"Windows Server 2019 must force audit policy subcategory settings to override audit policy category settings.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. \nThis setting allows administrators to enable more precise auditing capabilities.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\\n\nValue Name: SCENoApplyLegacyAuditPolicy\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000169"]},{"vulnId":"V-205645","ruleId":"SV-205645r958448_rule","severity":"medium","ruleTitle":"Windows Server 2019 domain controllers must have a PKI server certificate.","description":"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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nRun \"MMC\".\n\nSelect \"Add/Remove Snap-in\" from the \"File\" menu.\n\nSelect \"Certificates\" in the left pane and click the \"Add >\" button.\n\nSelect \"Computer Account\" and click \"Next\".\n\nSelect the appropriate option for \"Select the computer you want this snap-in to manage\" and click \"Finish\".\n\nClick \"OK\".\n\nSelect and expand the Certificates (Local Computer) entry in the left pane.\n\nSelect and expand the Personal entry in the left pane.\n\nSelect the Certificates entry in the left pane.\n\nIf no certificate for the domain controller exists in the right pane, this is a finding.","fixText":"Obtain a server certificate for the domain controller.","ccis":["CCI-000185"]},{"vulnId":"V-205646","ruleId":"SV-205646r1153437_rule","severity":"high","ruleTitle":"Windows Server 2019 domain controller PKI certificates must be issued by the DOD PKI or an approved External Certificate Authority (ECA).","description":"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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nRun \"MMC\".\n\nSelect \"Add/Remove Snap-in\" from the \"File\" menu.\n\nSelect \"Certificates\" in the left pane, and then click \"Add >\".\n\nSelect \"Computer Account\", and then click \"Next\".\n\nSelect the appropriate option for \"Select the computer you want this snap-in to manage\", and then click \"Finish\".\n\nClick \"OK\".\n\nSelect and expand the \"Certificates (Local Computer)\" entry in the left pane.\n\nSelect and expand the \"Personal\" entry in the left pane.\n\nSelect the \"Certificates\" entry in the left pane.\n\nIn the right pane, examine the \"Issued By\" field for the certificate to determine the issuing CA.\n\nIf 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.\n\nIf the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding.\n\nThere are multiple sources from which lists of valid DOD CAs and approved ECAs can be obtained: \n\nThe Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil.\n\nDOD 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 Cyber Exchange:\nhttps://www.cyber.mil/pki-pke/tools-configuration-files.","fixText":"Obtain a server certificate for the domain controller issued by the DOD PKI or an approved ECA.","ccis":["CCI-000185"]},{"vulnId":"V-205647","ruleId":"SV-205647r958448_rule","severity":"high","ruleTitle":"Windows Server 2019 PKI certificates associated with user accounts must be issued by a DoD PKI or an approved External Certificate Authority (ECA).","description":"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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview user account mappings to PKI certificates.\n\nOpen \"Windows PowerShell\".\n\nEnter \"Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled\".\n\nExclude disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account.\n\nIf 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.\n\nFor standard NIPRNet certificates, the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI).\n\nAlt Tokens and other certificates may use a different UPN format than the EDI-PI which vary by organization. Verified these with the organization.\n\nNIPRNet Example:\n\nName - User Principal Name\nUser1 - 1234567890@mil\n\nSee PKE documentation for other network domain suffixes.\n\nIf the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding.","fixText":"Map user accounts to PKI certificates using the appropriate User Principal Name (UPN) for the network. See PKE documentation for details.","ccis":["CCI-000185"]},{"vulnId":"V-205648","ruleId":"SV-205648r958448_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the DoD Root Certificate Authority (CA) certificates installed in the Trusted Root Store.","description":"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.\n\nSatisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182","checkContent":"Certificates and thumbprints referenced below apply to unclassified systems; refer to PKE documentation for other networks.\n\nOpen \"Windows PowerShell\" as an administrator.\n\nExecute the following command:\n\nGet-ChildItem -Path Cert:Localmachine\\root | Where Subject -Like \"*DoD*\" | FL Subject, Thumbprint, NotAfter\n\nIf the following certificate \"Subject\" and \"Thumbprint\" information is not displayed, this is a finding. \n\nSubject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US\nThumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB\nNotAfter: 12/30/2029\n\nSubject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US\nThumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026\nNotAfter: 7/25/2032\n\nSubject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US\nThumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B\nNotAfter: 6/14/2041\n\nSubject: CN=DoD Root CA 6, OU=PKI, OU=DoD, O=U.S. Government, C=US \nThumbprint: D37ECF61C0B4ED88681EF3630C4E2FC787B37AEF\nNotAfter: 1/24/2053 11:36:17 AM\n\nAlternately, use the Certificates MMC snap-in:\n\nRun \"MMC\".\n\nSelect \"File\", \"Add/Remove Snap-in\".\n\nSelect \"Certificates\" and click \"Add\".\n\nSelect \"Computer account\" and click \"Next\".\n\nSelect \"Local computer: (the computer this console is running on)\" and click \"Finish\".\n\nClick \"OK\".\n\nExpand \"Certificates\" and navigate to \"Trusted Root Certification Authorities >> Certificates\".\n\nExpand \"Certificates\" and navigate to \"Trusted Root Certification Authorities >> Certificates\".\n\nFor each of the DoD Root CA certificates noted below:\n\nRight-click on the certificate and select \"Open\".\n\nSelect the \"Details\" tab.\n\nScroll to the bottom and select \"Thumbprint\".\n\nIf the DoD Root CA certificates below are not listed or the value for the \"Thumbprint\" field is not as noted, this is a finding.\n\nDoD Root CA 3\nThumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB\nValid to: Sunday, December 30, 2029\n\nDoD Root CA 4\nThumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026\nValid to: Sunday, July 25, 2032\n\nDoD Root CA 5\nThumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B\nValid to: Friday, June 14, 2041\n\nDoD Root CA 6\nThumbprint: D37ECF61C0B4ED88681EF3630C4E2FC787B37AEFB\nValid to: Friday, January 24, 2053","fixText":"Install the DoD Root CA certificates:\nDoD Root CA 3\nDoD Root CA 4\nDoD Root CA 5\nDoD Root CA 6\n\nThe InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. Certificate bundles published by the PKI can be found at https://crl.gds.disa.mil/.","ccis":["CCI-000185","CCI-002470"]},{"vulnId":"V-205649","ruleId":"SV-205649r958448_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates installed in the Untrusted Certificates Store on unclassified systems.","description":"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.\n\nSatisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182","checkContent":"This is applicable to unclassified systems. It is NA for others.\n\nOpen \"PowerShell\" as an administrator.\n\nExecute the following command:\n\nGet-ChildItem -Path Cert:Localmachine\\disallowed | Where {$_.Issuer -Like \"*DoD Interoperability*\" -and $_.Subject -Like \"*DoD*\"} | FL Subject, Issuer, Thumbprint, NotAfter\n\nIf the following certificate \"Subject\", \"Issuer\", and \"Thumbprint\" information is not displayed, this is a finding. \n\nSubject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US\nIssuer: CN=DoD Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US\nThumbprint: 49CBE933151872E17C8EAE7F0ABA97FB610F6477\nNotAfter: 11/16/2024 9:57:16 AM\n\nAlternately, use the Certificates MMC snap-in:\n\nRun \"MMC\".\n\nSelect \"File\", \"Add/Remove Snap-in\".\n\nSelect \"Certificates\" and click \"Add\".\n\nSelect \"Computer account\" and click \"Next\".\n\nSelect \"Local computer: (the computer this console is running on)\" and click \"Finish\".\n\nClick \"OK\".\n\nExpand \"Certificates\" and navigate to Untrusted Certificates >> Certificates.\n\nFor each certificate with \"DoD Root CA...\" under \"Issued To\" and \"DoD Interoperability Root CA...\" under \"Issued By\":\n\nRight-click on the certificate and select \"Open\".\n\nSelect the \"Details\" tab.\n\nScroll to the bottom and select \"Thumbprint\".\n\nIf the certificate below is not listed or the value for the \"Thumbprint\" field is not as noted, this is a finding. \n\nIssued to: DoD Root CA 3\nIssued By: DoD Interoperability Root CA 2\nThumbprint: 49CBE933151872E17C8EAE7F0ABA97FB610F6477\nValid to:  11/16/2024 9:57:16 AM","fixText":"Install the DoD Interoperability Root CA cross-certificates on unclassified systems.\n\nIssued To - Issued By - Thumbprint\n\nDoD Root CA 3 - DoD Interoperability Root CA 2 - 49CBE933151872E17C8EAE7F0ABA97FB610F6477\n\nAdministrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user.\n\nThe FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files.","ccis":["CCI-000185","CCI-002470"]},{"vulnId":"V-205650","ruleId":"SV-205650r1107646_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the US DoD CCEB Interoperability Root CA cross-certificates in the Untrusted Certificates Store on unclassified systems.","description":"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.\n\nSatisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182","checkContent":"This is applicable to unclassified systems. It is NA for others.\n\nOpen \"PowerShell\" as an administrator.\n\nExecute the following command:\n\nGet-ChildItem -Path Cert:Localmachine\\disallowed | Where Issuer -Like \"*CCEB Interoperability*\" | FL Subject, Issuer, Thumbprint, NotAfter\n\nIf the following certificate \"Subject\", \"Issuer\", and \"Thumbprint\" information is not displayed, this is a finding. \n\nSubject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US\nIssuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US\nThumbprint: 9B74964506C7ED9138070D08D5F8B969866560C8\nNotAfter: 7/18/2025 9:56:22 AM     \n\nSubject: CN=DoD Root CA 6, OU=PKI, OU=DoD, O=U.S. Government, C=US\nIssuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US\nThumbprint: D471CA32F7A692CE6CBB6196BD3377FE4DBCD106\nNotAfter: 7/18/2026 12:15:05 PM                                                                                                                                                                                                                                                 \nAlternately, use the Certificates MMC snap-in:\n\nRun \"MMC\".\n\nSelect \"File\", \"Add/Remove Snap-in\".\n\nSelect \"Certificates\" and click \"Add\".\n\nSelect \"Computer account\" and click \"Next\".\n\nSelect \"Local computer: (the computer this console is running on)\" and click \"Finish\".\n\nClick \"OK\".\n\nExpand \"Certificates\" and navigate to Untrusted Certificates >> Certificates.\n\nFor each certificate with \"US DoD CCEB Interoperability Root CA ...\" under \"Issued By\":\n\nRight-click on the certificate and select \"Open\".\n\nSelect the \"Details\" tab.\n\nScroll to the bottom and select \"Thumbprint\".\n\nIf the certificate below is not listed or the value for the \"Thumbprint\" field is not as noted, this is a finding.\n\nSubject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US\nIssuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US\nThumbprint: 9B74964506C7ED9138070D08D5F8B969866560C8\nNotAfter: 7/18/2025 9:56:22 AM\n\nSubject: CN=DoD Root CA 6, OU=PKI, OU=DoD, O=U.S. Government, C=US\nIssuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US\nThumbprint: D471CA32F7A692CE6CBB6196BD3377FE4DBCD106\nNotAfter: 7/18/2026 12:15:05 PM","fixText":"Install the US DoD CCEB Interoperability Root CA cross-certificate on unclassified systems.\n\nIssued To - Issued By - Thumbprint\n\nDoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - 9B74964506C7ED9138070D08D5F8B969866560C8                 \nDoD Root CA 6 - US DOD CCEB Interoperability Root CA 2 -D471CA32F7A692CE6CBB6196BD3377FE4DBCD106              \n\nAdministrators should run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user.\n\nThe FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://dl.cyber.mil/pki-pke/msi/InstallRoot_5.6x32.msi. Certificate bundles published by the PKI can be found at https://crl.gds.disa.mil/.","ccis":["CCI-000185","CCI-002470"]},{"vulnId":"V-205651","ruleId":"SV-205651r958450_rule","severity":"medium","ruleTitle":"Windows Server 2019 users must be required to enter a password to access private keys stored on the computer.","description":"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.\n\nThe cornerstone of the PKI is the private key used to encrypt or digitally sign information.\n\nIf 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.\n\nBoth 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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive:  HKEY_LOCAL_MACHINE\nRegistry Path:  \\SOFTWARE\\Policies\\Microsoft\\Cryptography\\\n\nValue Name:  ForceKeyProtection\n\nType:  REG_DWORD\nValue:  0x00000002 (2)","fixText":"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\".","ccis":["CCI-000186"]},{"vulnId":"V-205652","ruleId":"SV-205652r1051061_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the built-in Windows password complexity policy enabled.","description":"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.\n\nSatisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy.\n\nIf the value for \"Password must meet complexity requirements\" is not set to \"Enabled\", this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"PasswordComplexity\" equals \"0\" in the file, this is a finding.\n\nNote: 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.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> \"Password must meet complexity requirements\" to \"Enabled\".","ccis":["CCI-004066","CCI-000192","CCI-000193","CCI-000194","CCI-001619"]},{"vulnId":"V-205653","ruleId":"SV-205653r1051062_rule","severity":"high","ruleTitle":"Windows Server 2019 reversible password encryption must be disabled.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy.\n\nIf the value for \"Store passwords using reversible encryption\" is not set to \"Disabled\", this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"ClearTextPassword\" equals \"1\" in the file, this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> \"Store passwords using reversible encryption\" to \"Disabled\".","ccis":["CCI-004062","CCI-000196"]},{"vulnId":"V-205654","ruleId":"SV-205654r1051063_rule","severity":"high","ruleTitle":"Windows Server 2019 must be configured to prevent the storage of the LAN Manager hash of passwords.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\\n\nValue Name: NoLMHash\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-004062","CCI-000196"]},{"vulnId":"V-205655","ruleId":"SV-205655r987796_rule","severity":"medium","ruleTitle":"Windows Server 2019 unencrypted passwords must not be sent to third-party Server Message Block (SMB) servers.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive:  HKEY_LOCAL_MACHINE\nRegistry Path:  \\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters\\\n\nValue Name:  EnablePlainTextPassword\n\nValue Type:  REG_DWORD\nValue:  0x00000000 (0)","fixText":"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\".","ccis":["CCI-000197"]},{"vulnId":"V-205656","ruleId":"SV-205656r1051064_rule","severity":"medium","ruleTitle":"Windows Server 2019 minimum password age must be configured to at least one day.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy.\n\nIf the value for the \"Minimum password age\" is set to \"0\" days (\"Password can be changed immediately\"), this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"MinimumPasswordAge\" equals \"0\" in the file, this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> \"Minimum password age\" to at least \"1\" day.","ccis":["CCI-004066","CCI-000198"]},{"vulnId":"V-205657","ruleId":"SV-205657r1153431_rule","severity":"medium","ruleTitle":"Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days.","description":"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 might not be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure.\n\nFor domain-joined systems, Windows LAPS must be used to change the built-in Administrator account password.","checkContent":"If there are no enabled local Administrator accounts, this is Not Applicable.\n\nReview the password last set date for the enabled local Administrator account.\n\nOn the stand alone or domain-joined server:\n\nOpen \"PowerShell\".\n\nEnter \"Get-LocalUser | Where-Object {$_.SID -like \"*500\"} | ForEach-Object ($_.PasswordLastSet){\"$($_.Name) password is: $([int]((Get-Date) - $_.PasswordLastSet).TotalDays) days old\"}\".\n\nIf the \"PasswordLastSet\" date is greater than \"60\" days old for the local Administrator account for administering the computer, this is a finding.\n\nVerify LAPS is configured and operational.\n\nIf the system is a stand alone member server, the LAPS portion of this requirement is Not Applicable.\n\nNavigate to Local Computer Policy >> Computer Configuration >> Administrative Templates >> System >> LAPS >> Password Settings >> Set to enabled. Password Complexity, large letters + small letters + numbers + special, Password Length 14, Password Age 60. If not configured as shown, this is a finding.\n\nVerify LAPS Operational logs >> Event Viewer >> Applications and Services Logs >> Microsoft >> Windows >> LAPS >> Operational. Verify LAPS policy process is completing. If it is not, this is a finding.","fixText":"Change the enabled local Administrator account password at least every 60 days. For domain-joined systems, Windows LAPS must be used to change the built-in Administrator account password.\n\nMore information is available at:\nhttps://techcommunity.microsoft.com/t5/windows-it-pro-blog/by-popular-demand-windows-laps-available-now/ba-p/3788747\nhttps://learn.microsoft.com/en-us/windows-server/identity/laps/laps-overview#windows-laps-supported-platforms-and-azure-ad-laps-preview-status","ccis":["CCI-004066","CCI-000199"]},{"vulnId":"V-205658","ruleId":"SV-205658r1051066_rule","severity":"medium","ruleTitle":"Windows Server 2019 passwords must be configured to expire.","description":"Passwords that do not expire or are reused increase the exposure of a password with greater probability of being discovered or cracked.","checkContent":"Review the password never expires status for enabled user accounts.\n\nOpen \"PowerShell\".\n\nDomain Controllers:\n\nEnter \"Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled\".\n\nExclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account.\n\nIf any enabled user accounts are returned with a \"PasswordNeverExpires\" status of \"True\", this is a finding.\n\nMember servers and standalone or nondomain-joined systems:\n\nEnter 'Get-CimInstance -Class Win32_Useraccount -Filter \"PasswordExpires=False and LocalAccount=True\" | FT Name, PasswordExpires, Disabled, LocalAccount'.\n\nExclude application accounts and disabled accounts (e.g., DefaultAccount, Guest).\n\nIf any enabled user accounts are returned with a \"PasswordExpires\" status of \"False\", this is a finding.","fixText":"Configure all enabled user account passwords to expire.\n\nUncheck \"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 or nondomain-joined systems. Document any exceptions with the ISSO.","ccis":["CCI-004066","CCI-000199"]},{"vulnId":"V-205659","ruleId":"SV-205659r1051067_rule","severity":"medium","ruleTitle":"Windows Server 2019 maximum password age must be configured to 60 days or less.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy.\n\nIf the value for the \"Maximum password age\" is greater than \"60\" days, this is a finding.\n\nIf the value is set to \"0\" (never expires), this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"MaximumPasswordAge\" is greater than \"60\" or equal to \"0\" in the file, this is a finding.","fixText":"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).","ccis":["CCI-004066","CCI-000199"]},{"vulnId":"V-205660","ruleId":"SV-205660r1000129_rule","severity":"medium","ruleTitle":"Windows Server 2019 password history must be configured to 24 passwords remembered.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy.\n\nIf the value for \"Enforce password history\" is less than \"24\" passwords remembered, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"PasswordHistorySize\" is less than \"24\" in the file, this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> \"Enforce password history\" to \"24\" passwords remembered.","ccis":["CCI-004061"]},{"vulnId":"V-205661","ruleId":"SV-205661r1051068_rule","severity":"medium","ruleTitle":"Windows Server 2019 manually managed application account passwords must be at least 14 characters in length.","description":"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 14 characters in length.","checkContent":"Determine if manually managed application/service accounts exist. If none exist, this is NA.\n\nVerify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 14 characters in length.\n\nIf such a policy does not exist or has not been implemented, this is a finding.","fixText":"Establish a policy that requires application/service account passwords that are manually managed to be at least 14 characters in length. Ensure the policy is enforced.","ccis":["CCI-004066","CCI-000205"]},{"vulnId":"V-205662","ruleId":"SV-205662r1051069_rule","severity":"medium","ruleTitle":"Windows Server 2019 minimum password length must be configured to 14 characters.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy.\n\nIf the value for the \"Minimum password length,\" is less than \"14\" characters, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"MinimumPasswordLength\" is less than \"14\" in the file, this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Password Policy >> \"Minimum password length\" to \"14\" characters.","ccis":["CCI-004066","CCI-000205"]},{"vulnId":"V-205663","ruleId":"SV-205663r1137691_rule","severity":"high","ruleTitle":"Windows Server 2019 local volumes must use a format that supports NTFS attributes.","description":"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.","checkContent":"Open \"Computer Management\".\n\nSelect \"Disk Management\" under \"Storage\".\n\nFor each local volume, if the file system does not indicate \"NTFS\", this is a finding.\n\nResilient file system (ReFS) and Cluster Shared Volumes (CSV) are also acceptable and are not findings. \n\nThis does not apply to system partitions such the Recovery and EFI System Partition.","fixText":"Format volumes to use NTFS, ReFS, or CSV.","ccis":["CCI-000213"]},{"vulnId":"V-205664","ruleId":"SV-205664r1137691_rule","severity":"low","ruleTitle":"Windows Server 2019 non-administrative accounts or groups must only have print permissions on printer shares.","description":"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.","checkContent":"Open \"Printers & scanners\" in \"Settings\".\n\nIf there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.)\n\nFor each printer:\n\nSelect the printer and \"Manage\". \n\nSelect \"Printer Properties\". \n\nSelect the \"Sharing\" tab. \n\nIf \"Share this printer\" is checked, select the \"Security\" tab.\n\nIf any standard user accounts or groups have permissions other than \"Print\", this is a finding.\n\nThe default is for the \"Everyone\" group to be given \"Print\" permission.\n\n\"All APPLICATION PACKAGES\" and \"CREATOR OWNER\" are not standard user accounts.","fixText":"Configure the permissions on shared printers to restrict standard users to only have Print permissions.","ccis":["CCI-000213"]},{"vulnId":"V-205665","ruleId":"SV-205665r1137691_rule","severity":"medium","ruleTitle":"Windows Server 2019 Access this computer from the network user right must only be assigned to the Administrators, Authenticated Users, and \nEnterprise Domain Controllers groups on domain controllers.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts 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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Access this computer from the network\" right, this is a finding.\n\n- Administrators\n- Authenticated Users\n- Enterprise Domain Controllers\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeNetworkLogonRight\" user right, this is a finding.\n\nS-1-5-32-544 (Administrators)\nS-1-5-11 (Authenticated Users)\nS-1-5-9 (Enterprise Domain Controllers)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators\n- Authenticated Users\n- Enterprise Domain Controllers","ccis":["CCI-000213"]},{"vulnId":"V-205666","ruleId":"SV-205666r1137691_rule","severity":"medium","ruleTitle":"Windows Server 2019 Allow log on through Remote Desktop Services user right must only be assigned to the Administrators group on domain controllers.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Allow log on through Remote Desktop Services\" user right can access a system through Remote Desktop.","checkContent":"This applies to domain controllers, it is NA for other systems.\n\nVerify the effective setting in Local Group Policy Editor.\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Allow log on through Remote Desktop Services\" user right, this is a finding.\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeRemoteInteractiveLogonRight\" user right, this is a finding.\n\nS-1-5-32-544 (Administrators)","fixText":"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:\n\n- Administrators","ccis":["CCI-000213"]},{"vulnId":"V-205667","ruleId":"SV-205667r1137691_rule","severity":"medium","ruleTitle":"Windows Server 2019 Deny access to this computer from the network user right on domain controllers must be configured to prevent unauthenticated access.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny access to this computer from the network\" user right defines the accounts that are prevented from logging on from the network.\n\nThe Guests group must be assigned this right to prevent unauthenticated access.","checkContent":"This applies to domain controllers. A separate version applies to other systems.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf the following accounts or groups are not defined for the \"Deny access to this computer from the network\" user right, this is a finding:\n\n- Guests Group\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf the following SIDs are not defined for the \"SeDenyNetworkLogonRight\" user right, this is a finding.\n\nS-1-5-32-546 (Guests)","fixText":"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:\n\n- Guests Group","ccis":["CCI-000213"]},{"vulnId":"V-205668","ruleId":"SV-205668r1137691_rule","severity":"medium","ruleTitle":"Windows Server 2019 Deny log on as a batch job user right on domain controllers must be configured to prevent unauthenticated access.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"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.\n\nThe Guests group must be assigned to prevent unauthenticated access.","checkContent":"This applies to domain controllers. A separate version applies to other systems.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf the following accounts or groups are not defined for the \"Deny log on as a batch job\" user right, this is a finding:\n\n- Guests Group\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf the following SID(s) are not defined for the \"SeDenyBatchLogonRight\" user right, this is a finding:\n\nS-1-5-32-546 (Guests)","fixText":"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:\n\n- Guests Group","ccis":["CCI-000213"]},{"vulnId":"V-205669","ruleId":"SV-205669r1137691_rule","severity":"medium","ruleTitle":"Windows Server 2019 Deny log on as a service user right must be configured to include no accounts or groups (blank) on domain controllers.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on as a service\" user right defines accounts that are denied logon as a service.\n\nIncorrect configurations could prevent services from starting and result in a denial of service.","checkContent":"This applies to domain controllers. A separate version applies to other systems.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups are defined for the \"Deny log on as a service\" user right, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs are granted the \"SeDenyServiceLogonRight\" user right, this is a finding.","fixText":"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).","ccis":["CCI-000213"]},{"vulnId":"V-205670","ruleId":"SV-205670r1137691_rule","severity":"medium","ruleTitle":"Windows Server 2019 Deny log on locally user right on domain controllers must be configured to prevent unauthenticated access.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on locally\" user right defines accounts that are prevented from logging on interactively.\n\nThe Guests group must be assigned this right to prevent unauthenticated access.","checkContent":"This applies to domain controllers. A separate version applies to other systems.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf the following accounts or groups are not defined for the \"Deny log on locally\" user right, this is a finding:\n\n- Guests Group\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf the following SID(s) are not defined for the \"SeDenyInteractiveLogonRight\" user right, this is a finding:\n\nS-1-5-32-546 (Guests)","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> \"Deny log on locally\" to include the following:\n\n- Guests Group","ccis":["CCI-000213"]},{"vulnId":"V-205671","ruleId":"SV-205671r1137691_rule","severity":"medium","ruleTitle":"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 or nondomain-joined systems.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts 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.","checkContent":"This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Access this computer from the network\" user right, this is a finding:\n\n- Administrators\n- Authenticated Users\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeNetworkLogonRight\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\nS-1-5-11 (Authenticated Users)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators\n- Authenticated Users","ccis":["CCI-000213"]},{"vulnId":"V-205672","ruleId":"SV-205672r1137691_rule","severity":"medium","ruleTitle":"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.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny access to this computer from the network\" user right defines the accounts that are prevented from logging on from the network.\n\nIn 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.\n\nLocal accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks.\n\nThe Guests group must be assigned this right to prevent unauthenticated access.","checkContent":"This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf the following accounts or groups are not defined for the \"Deny access to this computer from the network\" user right, this is a finding:\n\nDomain Systems Only:\n- Enterprise Admins group\n- Domain Admins group\n- \"Local account and member of Administrators group\" or \"Local account\" (see Note below)\n\nAll Systems:\n- Guests group\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf the following SIDs are not defined for the \"SeDenyNetworkLogonRight\" user right, this is a finding.\n\nDomain Systems Only:\nS-1-5-root domain-519 (Enterprise Admins)\nS-1-5-domain-512 (Domain Admins)\nS-1-5-114 (\"Local account and member of Administrators group\") or S-1-5-113 (\"Local account\")\n\nAll Systems:\nS-1-5-32-546 (Guests)\n\nNote: These are built-in security groups. \"Local account\" is more restrictive but may cause issues on servers such as systems that provide failover clustering.","fixText":"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:\n\nDomain Systems Only:\n- Enterprise Admins group\n- Domain Admins group\n- \"Local account and member of Administrators group\" or \"Local account\" (see Note below)\n\nAll Systems:\n- Guests group\n\nNote: These are built-in security groups. \"Local account\" is more restrictive but may cause issues on servers such as systems that provide failover clustering.","ccis":["CCI-000213"]},{"vulnId":"V-205673","ruleId":"SV-205673r1137691_rule","severity":"medium","ruleTitle":"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.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"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.\n\nIn 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.\n\nThe Guests group must be assigned to prevent unauthenticated access.","checkContent":"This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf the following accounts or groups are not defined for the \"Deny log on as a batch job\" user right, this is a finding:\n\nDomain Systems Only:\n- Enterprise Admins Group\n- Domain Admins Group\n\nAll Systems:\n- Guests Group\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf the following SIDs are not defined for the \"SeDenyBatchLogonRight\" user right, this is a finding.\n\nDomain Systems Only:\nS-1-5-root domain-519 (Enterprise Admins)\nS-1-5-domain-512 (Domain Admins)\n\nAll Systems:\nS-1-5-32-546 (Guests)","fixText":"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:\n\nDomain Systems Only:\n- Enterprise Admins Group\n- Domain Admins Group\n\nAll Systems:\n- Guests Group","ccis":["CCI-000213"]},{"vulnId":"V-205674","ruleId":"SV-205674r1137691_rule","severity":"medium","ruleTitle":"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.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on as a service\" user right defines accounts that are denied logon as a service.\n\nIn 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.\n\nIncorrect configurations could prevent services from starting and result in a denial of service.","checkContent":"This applies to member servers only. A separate version applies to domain controllers.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf 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:\n\n- Enterprise Admins Group\n- Domain Admins Group\n\nIf any accounts or groups are defined for the \"Deny log on as a service\" user right on nondomain-joined systems, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf the following SIDs are not defined for the \"SeDenyServiceLogonRight\" user right on domain-joined systems, this is a finding:\n\nS-1-5-root domain-519 (Enterprise Admins)\nS-1-5-domain-512 (Domain Admins)\n\nIf any SIDs are defined for the user right, this is a finding.","fixText":"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:\n\nDomain systems:\n- Enterprise Admins Group\n- Domain Admins Group","ccis":["CCI-000213"]},{"vulnId":"V-205675","ruleId":"SV-205675r1137691_rule","severity":"medium","ruleTitle":"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.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on locally\" user right defines accounts that are prevented from logging on interactively.\n\nIn 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.\n\nThe Guests group must be assigned this right to prevent unauthenticated access.","checkContent":"This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf the following accounts or groups are not defined for the \"Deny log on locally\" user right, this is a finding:\n\nDomain Systems Only:\n- Enterprise Admins Group\n- Domain Admins Group\n\nAll Systems:\n- Guests Group\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf the following SIDs are not defined for the \"SeDenyInteractiveLogonRight\" user right, this is a finding:\n\nDomain Systems Only:\nS-1-5-root domain-519 (Enterprise Admins)\nS-1-5-domain-512 (Domain Admins)\n\nAll Systems:\nS-1-5-32-546 (Guests)","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> \"Deny log on locally\" to include the following:\n\nDomain Systems Only:\n- Enterprise Admins Group\n- Domain Admins Group\n\nAll Systems:\n- Guests Group","ccis":["CCI-000213"]},{"vulnId":"V-205676","ruleId":"SV-205676r1137691_rule","severity":"medium","ruleTitle":"Windows Server 2019 Allow log on locally user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Allow log on locally\" user right can log on interactively to a system.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Allow log on locally\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeInteractiveLogonRight\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators","ccis":["CCI-000213"]},{"vulnId":"V-205677","ruleId":"SV-205677r1186380_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the roles and features required by the system documented.","description":"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.","checkContent":"Required roles and features will vary based on the function of the individual system.\n\nRoles and features specifically required to be disabled per the STIG are identified in separate requirements.\n\nIf the organization has not documented the roles and features required for the system(s), this is a finding.\n\nThe PowerShell command \"Get-WindowsFeature | Where-Object {$_. installstate -eq \"Installed\"} | Format-List Displayname, Name, Featuretype\" will list all roles and features with an \"Installed\" state.","fixText":"Document the roles and features required for the system to operate. Uninstall any that are not required.","ccis":["CCI-000381"]},{"vulnId":"V-205678","ruleId":"SV-205678r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must not have the Fax Server role installed.","description":"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.","checkContent":"Open \"PowerShell\".\n\nEnter \"Get-WindowsFeature | Where Name -eq Fax\".\n\nIf \"Installed State\" is \"Installed\", this is a finding.\n\nAn Installed State of \"Available\" or \"Removed\" is not a finding.","fixText":"Uninstall the \"Fax Server\" role.\n\nStart \"Server Manager\".\n\nSelect the server with the role.\n\nScroll down to \"ROLES AND FEATURES\" in the right pane.\n\nSelect \"Remove Roles and Features\" from the drop-down \"TASKS\" list.\n\nSelect the appropriate server on the \"Server Selection\" page and click \"Next\".\n\nDeselect \"Fax Server\" on the \"Roles\" page.\n\nClick \"Next\" and \"Remove\" as prompted.","ccis":["CCI-000381"]},{"vulnId":"V-205679","ruleId":"SV-205679r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must not have the Peer Name Resolution Protocol installed.","description":"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.","checkContent":"Open \"PowerShell\".\n\nEnter \"Get-WindowsFeature | Where Name -eq PNRP\".\n\nIf \"Installed State\" is \"Installed\", this is a finding.\n\nAn Installed State of \"Available\" or \"Removed\" is not a finding.","fixText":"Uninstall the \"Peer Name Resolution Protocol\" feature.\n\nStart \"Server Manager\".\n\nSelect the server with the feature.\n\nScroll down to \"ROLES AND FEATURES\" in the right pane.\n\nSelect \"Remove Roles and Features\" from the drop-down \"TASKS\" list.\n\nSelect the appropriate server on the \"Server Selection\" page and click \"Next\".\n\nDeselect \"Peer Name Resolution Protocol\" on the \"Features\" page.\n\nClick \"Next\" and \"Remove\" as prompted.","ccis":["CCI-000381"]},{"vulnId":"V-205680","ruleId":"SV-205680r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must not have Simple TCP/IP Services installed.","description":"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.","checkContent":"Open \"PowerShell\".\n\nEnter \"Get-WindowsFeature | Where Name -eq Simple-TCPIP\".\n\nIf \"Installed State\" is \"Installed\", this is a finding.\n\nAn Installed State of \"Available\" or \"Removed\" is not a finding.","fixText":"Uninstall the \"Simple TCP/IP Services\" feature.\n\nStart \"Server Manager\".\n\nSelect the server with the feature.\n\nScroll down to \"ROLES AND FEATURES\" in the right pane.\n\nSelect \"Remove Roles and Features\" from the drop-down \"TASKS\" list.\n\nSelect the appropriate server on the \"Server Selection\" page and click \"Next\".\n\nDeselect \"Simple TCP/IP Services\" on the \"Features\" page.\n\nClick \"Next\" and \"Remove\" as prompted.","ccis":["CCI-000381"]},{"vulnId":"V-205681","ruleId":"SV-205681r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must not have the TFTP Client installed.","description":"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.","checkContent":"Open \"PowerShell\".\n\nEnter \"Get-WindowsFeature | Where Name -eq TFTP-Client\".\n\nIf \"Installed State\" is \"Installed\", this is a finding.\n\nAn Installed State of \"Available\" or \"Removed\" is not a finding.","fixText":"Uninstall the \"TFTP Client\" feature.\n\nStart \"Server Manager\".\n\nSelect the server with the feature.\n\nScroll down to \"ROLES AND FEATURES\" in the right pane.\n\nSelect \"Remove Roles and Features\" from the drop-down \"TASKS\" list.\n\nSelect the appropriate server on the \"Server Selection\" page and click \"Next\".\n\nDeselect \"TFTP Client\" on the \"Features\" page.\n\nClick \"Next\" and \"Remove\" as prompted.","ccis":["CCI-000381"]},{"vulnId":"V-205682","ruleId":"SV-205682r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must not have the Server Message Block (SMB) v1 protocol installed.","description":"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.","checkContent":"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.\n\nOpen \"Windows PowerShell\" with elevated privileges (run as administrator).\n\nEnter \"Get-WindowsFeature -Name FS-SMB1\".\n\nIf \"Installed State\" is \"Installed\", this is a finding.\n\nAn Installed State of \"Available\" or \"Removed\" is not a finding.","fixText":"Uninstall the SMBv1 protocol.\n\nOpen \"Windows PowerShell\" with elevated privileges (run as administrator).\n\nEnter \"Uninstall-WindowsFeature -Name FS-SMB1 -Restart\".\n(Omit the Restart parameter if an immediate restart of the system cannot be done.)\n\nAlternately:\n\nStart \"Server Manager\".\n\nSelect the server with the feature.\n\nScroll down to \"ROLES AND FEATURES\" in the right pane.\n\nSelect \"Remove Roles and Features\" from the drop-down \"TASKS\" list.\n\nSelect the appropriate server on the \"Server Selection\" page and click \"Next\".\n\nDeselect \"SMB 1.0/CIFS File Sharing Support\" on the \"Features\" page.\n\nClick \"Next\" and \"Remove\" as prompted.","ccis":["CCI-000381"]},{"vulnId":"V-205683","ruleId":"SV-205683r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server.","description":"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.","checkContent":"Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\LanmanServer\\Parameters\\\n\nValue Name: SMB1\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> \"Configure SMBv1 Server\" to \"Disabled\".\n\nThe system must be restarted for the change to take effect.\n\nThis 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.","ccis":["CCI-000381"]},{"vulnId":"V-205684","ruleId":"SV-205684r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client.","description":"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.","checkContent":"Different methods are available to disable SMBv1 on Windows Server 2019, if WN19-00-000380 is configured, this is NA.\n\nIf the following registry value is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\mrxsmb10\\\n\nValue Name: Start\n\nType: REG_DWORD\nValue: 0x00000004 (4)","fixText":"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\".\n\nThe system must be restarted for the changes to take effect.\n\nThis 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.","ccis":["CCI-000381"]},{"vulnId":"V-205685","ruleId":"SV-205685r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must not have Windows PowerShell 2.0 installed.","description":"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.","checkContent":"Open \"PowerShell\".\n\nEnter \"Get-WindowsFeature | Where Name -eq PowerShell-v2\".\n\nIf \"Installed State\" is \"Installed\", this is a finding.\n\nAn Installed State of \"Available\" or \"Removed\" is not a finding.","fixText":"Uninstall the \"Windows PowerShell 2.0 Engine\".\n\nStart \"Server Manager\".\n\nSelect the server with the feature.\n\nScroll down to \"ROLES AND FEATURES\" in the right pane.\n\nSelect \"Remove Roles and Features\" from the drop-down \"TASKS\" list.\n\nSelect the appropriate server on the \"Server Selection\" page and click \"Next\".\n\nDeselect \"Windows PowerShell 2.0 Engine\" under \"Windows PowerShell\" on the \"Features\" page.\n\nClick \"Next\" and \"Remove\" as prompted.","ccis":["CCI-000381"]},{"vulnId":"V-205686","ruleId":"SV-205686r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must prevent the display of slide shows on the lock screen.","description":"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.","checkContent":"Verify the registry value below. \n\nIf it does not exist or is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\Personalization\\\n\nValue Name: NoLockScreenSlideshow\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Control Panel >> Personalization >> \"Prevent enabling lock screen slide show\" to \"Enabled\".","ccis":["CCI-000381"]},{"vulnId":"V-205687","ruleId":"SV-205687r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have WDigest Authentication disabled.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive:  HKEY_LOCAL_MACHINE\nRegistry Path:  \\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\Wdigest\\\n\nValue Name:  UseLogonCredential\n\nType:  REG_DWORD\nValue:  0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> \"WDigest Authentication (disabling may require KB2871997)\" to \"Disabled\".\n\nThis 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.","ccis":["CCI-000381"]},{"vulnId":"V-205688","ruleId":"SV-205688r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 downloading print driver packages over HTTP must be turned off.","description":"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. \n\nThis setting prevents the computer from downloading print driver packages over HTTP.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows NT\\Printers\\\n\nValue Name: DisableWebPnPDownload\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000381"]},{"vulnId":"V-205689","ruleId":"SV-205689r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 printing over HTTP must be turned off.","description":"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.\n\nThis 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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows NT\\Printers\\\n\nValue Name: DisableHTTPPrinting\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Internet Communication Management >> Internet Communication settings >> \"Turn off printing over HTTP\" to \"Enabled\".","ccis":["CCI-000381"]},{"vulnId":"V-205690","ruleId":"SV-205690r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 network selection user interface (UI) must not be displayed on the logon screen.","description":"Enabling interaction with the network selection UI allows users to change connections to available networks without signing in to Windows.","checkContent":"Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\\n\nValue Name: DontDisplayNetworkSelectionUI\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> \"Do not display network selection UI\" to \"Enabled\".","ccis":["CCI-000381"]},{"vulnId":"V-205691","ruleId":"SV-205691r958478_rule","severity":"low","ruleTitle":"Windows Server 2019 Application Compatibility Program Inventory must be prevented from collecting data and sending the information to Microsoft.","description":"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.\n\nThis setting will prevent the Program Inventory from collecting data about a system and sending the information to Microsoft.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\AppCompat\\\n\nValue Name: DisableInventory\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Application Compatibility >> \"Turn off Inventory Collector\" to \"Enabled\".","ccis":["CCI-000381"]},{"vulnId":"V-205692","ruleId":"SV-205692r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 Windows Defender SmartScreen must be enabled.","description":"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.","checkContent":"This is applicable to unclassified systems; for other systems, this is NA.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\\n\nValue Name: EnableSmartScreen\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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.\n\nWindows 2019 includes duplicate policies for this setting. It can also be configured under Computer Configuration >> Administrative Templates >> Windows Components >> Windows Defender SmartScreen >> Explorer.","ccis":["CCI-000381"]},{"vulnId":"V-205693","ruleId":"SV-205693r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must disable Basic authentication for RSS feeds over HTTP.","description":"Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.","checkContent":"The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections.\n\nIf the registry value name below does not exist, this is not a finding.\n\nIf it exists and is configured with a value of \"0\", this is not a finding.\n\nIf it exists and is configured with a value of \"1\", this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Internet Explorer\\Feeds\\\n\nValue Name: AllowBasicAuthInClear\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0) (or if the Value Name does not exist)","fixText":"The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections.\n\nIf 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\".","ccis":["CCI-000381"]},{"vulnId":"V-205694","ruleId":"SV-205694r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 must prevent Indexing of encrypted files.","description":"Indexing of encrypted files may expose sensitive data. This setting prevents encrypted files from being indexed.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\Windows Search\\\n\nValue Name: AllowIndexingEncryptedStoresOrItems\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Search >> \"Allow indexing of encrypted files\" to \"Disabled\".","ccis":["CCI-000381"]},{"vulnId":"V-205695","ruleId":"SV-205695r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 domain controllers must run on a machine dedicated to that function.","description":"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. \n\nSome 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.","checkContent":"This applies to domain controllers, it is NA for other systems.\n\nReview the installed roles the domain controller is supporting.\n\nStart \"Server Manager\".\n\nSelect \"AD DS\" in the left pane and the server name under \"Servers\" to the right.\n\nSelect \"Add (or Remove) Roles and Features\" from \"Tasks\" in the \"Roles and Features\" section. (Cancel before any changes are made.)\n\nDetermine if any additional server roles are installed. A basic domain controller setup will include the following:\n\n- Active Directory Domain Services\n- DNS Server\n- File and Storage Services\n\nIf any roles not requiring installation on a domain controller are installed, this is a finding. \n\nA 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.\n\nRun \"Programs and Features\".\n\nReview installed applications.\n\nIf any applications are installed that are not required for the domain controller, this is a finding.","fixText":"Remove additional roles or applications such as web, database, and email from the domain controller.","ccis":["CCI-000381"]},{"vulnId":"V-205696","ruleId":"SV-205696r958478_rule","severity":"medium","ruleTitle":"Windows Server 2019 local users on domain-joined member servers must not be enumerated.","description":"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.","checkContent":"This applies to member servers. For domain controllers and standalone or nondomain-joined systems, this is NA.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\System\\\n\nValue Name: EnumerateLocalUsers\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Logon >> \"Enumerate local users on domain-joined computers\" to \"Disabled\".","ccis":["CCI-000381"]},{"vulnId":"V-205697","ruleId":"SV-205697r958480_rule","severity":"medium","ruleTitle":"Windows Server 2019 must not have the Microsoft FTP service installed unless required by the organization.","description":"Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.","checkContent":"If the server has the role of an FTP server, this is NA.\n\nOpen \"PowerShell\".\n\nEnter \"Get-WindowsFeature | Where Name -eq Web-Ftp-Service\".\n\nIf \"Installed State\" is \"Installed\", this is a finding.\n\nAn Installed State of \"Available\" or \"Removed\" is not a finding.\n\nIf the system has the role of an FTP server, this must be documented with the ISSO.","fixText":"Uninstall the \"FTP Server\" role.\n\nStart \"Server Manager\".\n\nSelect the server with the role.\n\nScroll down to \"ROLES AND FEATURES\" in the right pane.\n\nSelect \"Remove Roles and Features\" from the drop-down \"TASKS\" list.\n\nSelect the appropriate server on the \"Server Selection\" page and click \"Next\".\n\nDeselect \"FTP Server\" under \"Web Server (IIS)\" on the \"Roles\" page.\n\nClick \"Next\" and \"Remove\" as prompted.","ccis":["CCI-000382"]},{"vulnId":"V-205698","ruleId":"SV-205698r958480_rule","severity":"medium","ruleTitle":"Windows Server 2019 must not have the Telnet Client installed.","description":"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.","checkContent":"Open \"PowerShell\".\n\nEnter \"Get-WindowsFeature | Where Name -eq Telnet-Client\".\n\nIf \"Installed State\" is \"Installed\", this is a finding.\n\nAn Installed State of \"Available\" or \"Removed\" is not a finding.","fixText":"Uninstall the \"Telnet Client\" feature.\n\nStart \"Server Manager\".\n\nSelect the server with the feature.\n\nScroll down to \"ROLES AND FEATURES\" in the right pane.\n\nSelect \"Remove Roles and Features\" from the drop-down \"TASKS\" list.\n\nSelect the appropriate server on the \"Server Selection\" page and click \"Next\".\n\nDeselect \"Telnet Client\" on the \"Features\" page.\n\nClick \"Next\" and \"Remove\" as prompted.","ccis":["CCI-000382"]},{"vulnId":"V-205699","ruleId":"SV-205699r958482_rule","severity":"medium","ruleTitle":"Windows Server 2019 shared user accounts must not be permitted.","description":"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.","checkContent":"Determine whether any shared accounts exist. If no shared accounts exist, this is NA.\n\nShared 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.\n\nIf unapproved shared accounts exist, this is a finding.","fixText":"Remove unapproved shared accounts from the system.\n\nDocument 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.","ccis":["CCI-000764"]},{"vulnId":"V-205700","ruleId":"SV-205700r958482_rule","severity":"medium","ruleTitle":"Windows Server 2019 accounts must require passwords.","description":"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.","checkContent":"Review the password required status for enabled user accounts.\n\nOpen \"PowerShell\".\n\nDomain Controllers:\n\nEnter \"Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled\".\n\nExclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs).\n\nIf \"Passwordnotrequired\" is \"True\" or blank for any enabled user account, this is a finding.\n\nMember servers and standalone or nondomain-joined systems:\n\nEnter 'Get-CimInstance -Class Win32_Useraccount -Filter \"PasswordRequired=False and LocalAccount=True\" | FT Name, PasswordRequired, Disabled, LocalAccount'.\n\nExclude disabled accounts (e.g., DefaultAccount, Guest).\n\nIf any enabled user accounts are returned with a \"PasswordRequired\" status of \"False\", this is a finding.","fixText":"Configure all enabled accounts to require passwords.\n\nThe 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.","ccis":["CCI-000764"]},{"vulnId":"V-205701","ruleId":"SV-205701r1051070_rule","severity":"medium","ruleTitle":"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.","description":"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.\n\nSatisfies: 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","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nOpen \"PowerShell\".\n\nEnter the following:\n\n\"Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name\"\n(\"DistinguishedName\" may be substituted for \"Name\" for more detailed output.)\n\nIf any user accounts, including administrators, are listed, this is a finding.\n\n\nAlternately:\n\nTo view sample accounts in \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\"):\n\nSelect 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.)\n\nRight-click the sample user account and select \"Properties\".\n\nSelect the \"Account\" tab.\n\nIf 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.","fixText":"Configure all user accounts, including administrator accounts, in Active Directory to enable the option \"Smart card is required for interactive logon\".\n\nRun \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\"):\n\nSelect the OU where the user accounts are located. (By default this is the Users node; however, accounts may be under other organization-defined OUs.)\n\nRight-click the user account and select \"Properties\".\n\nSelect the \"Account\" tab.\n\nCheck \"Smart card is required for interactive logon\" in the \"Account Options\" area.","ccis":["CCI-000767","CCI-000768","CCI-001948"]},{"vulnId":"V-205702","ruleId":"SV-205702r1051071_rule","severity":"medium","ruleTitle":"Windows Server 2019 Kerberos user logon restrictions must be enforced.","description":"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.\n\nSatisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nVerify the following is configured in the Default Domain Policy:\n\nOpen \"Group Policy Management\".\n\nNavigate to \"Group Policy Objects\" in the Domain being reviewed (Forest >> Domains >> Domain). \n\nRight-click on the \"Default Domain Policy\".\n\nSelect \"Edit\".\n\nNavigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy.\n\nIf the \"Enforce user logon restrictions\" is not set to \"Enabled\", this is a finding.","fixText":"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\".","ccis":["CCI-001942"]},{"vulnId":"V-205703","ruleId":"SV-205703r1051072_rule","severity":"medium","ruleTitle":"Windows Server 2019 Kerberos service ticket maximum lifetime must be limited to 600 minutes or less.","description":"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.\n\nSatisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nVerify the following is configured in the Default Domain Policy:\n\nOpen \"Group Policy Management\".\n\nNavigate to \"Group Policy Objects\" in the Domain being reviewed (Forest >> Domains >> Domain). \n\nRight-click on the \"Default Domain Policy\".\n\nSelect \"Edit\".\n\nNavigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy.\n\nIf the value for \"Maximum lifetime for service ticket\" is \"0\" or greater than \"600\" minutes, this is a finding.","fixText":"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\".","ccis":["CCI-001941","CCI-001942"]},{"vulnId":"V-205704","ruleId":"SV-205704r1051073_rule","severity":"medium","ruleTitle":"Windows Server 2019 Kerberos user ticket lifetime must be limited to 10 hours or less.","description":"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.\n\nSatisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nVerify the following is configured in the Default Domain Policy:\n\nOpen \"Group Policy Management\".\n\nNavigate to \"Group Policy Objects\" in the Domain being reviewed (Forest >> Domains >> Domain).\n\nRight-click on the \"Default Domain Policy\".\n\nSelect \"Edit\".\n\nNavigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy.\n\nIf the value for \"Maximum lifetime for user ticket\" is \"0\" or greater than \"10\" hours, this is a finding.","fixText":"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\".","ccis":["CCI-001941","CCI-001942"]},{"vulnId":"V-205705","ruleId":"SV-205705r1051074_rule","severity":"medium","ruleTitle":"Windows Server 2019 Kerberos policy user ticket renewal maximum lifetime must be limited to seven days or less.","description":"This setting determines the period of time (in days) during which a user's TGT may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access.\n\nSatisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nVerify the following is configured in the Default Domain Policy:\n\nOpen \"Group Policy Management\".\n\nNavigate to \"Group Policy Objects\" in the Domain being reviewed (Forest >> Domains >> Domain).\n \nRight-click on the \"Default Domain Policy\".\n\nSelect \"Edit\".\n\nNavigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy.\n\nIf the \"Maximum lifetime for user ticket renewal\" is greater than \"7\" days, this is a finding.","fixText":"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.","ccis":["CCI-001941","CCI-001942"]},{"vulnId":"V-205706","ruleId":"SV-205706r1051075_rule","severity":"medium","ruleTitle":"Windows Server 2019 computer clock synchronization tolerance must be limited to five minutes or less.","description":"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. 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.\n\nSatisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nVerify the following is configured in the Default Domain Policy:\n\nOpen \"Group Policy Management\".\n\nNavigate to \"Group Policy Objects\" in the Domain being reviewed (Forest >> Domains >> Domain).\n \nRight-click on the \"Default Domain Policy\".\n\nSelect \"Edit\".\n\nNavigate to Computer Configuration >> Policies >> Windows Settings >> Security Settings >> Account Policies >> Kerberos Policy.\n\nIf the \"Maximum tolerance for computer clock synchronization\" is greater than \"5\" minutes, this is a finding.","fixText":"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.","ccis":["CCI-001941","CCI-001942"]},{"vulnId":"V-205707","ruleId":"SV-205707r1051076_rule","severity":"medium","ruleTitle":"Windows Server 2019 outdated or unused accounts must be removed or disabled.","description":"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.","checkContent":"Open \"Windows PowerShell\".\n\nDomain Controllers:\n\nEnter \"Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00\"\n\nThis will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate.\n\nMember servers and standalone or nondomain-joined systems:\n\nCopy 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.)\n\n\"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach {\n $user = ([ADSI]$_.Path)\n $lastLogin = $user.Properties.LastLogin.Value\n $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2\n if ($lastLogin -eq $null) {\n $lastLogin = 'Never'\n }\n Write-Host $user.Name $lastLogin $enabled \n}\"\n\nThis will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False).\nFor example: User1 10/31/2015 5:49:56 AM True\n\nReview the list of accounts returned by the above queries to determine the finding validity for each account reported.\n\nExclude the following accounts:\n\n- Built-in administrator account (Renamed, SID ending in 500)\n- Built-in guest account (Renamed, Disabled, SID ending in 501)\n- Application accounts\n\nIf any enabled accounts have not been logged on to within the past 35 days, this is a finding.\n\nInactive accounts that have been reviewed and deemed to be required must be documented with the information system security officer (ISSO).","fixText":"Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days.","ccis":["CCI-003627","CCI-000795"]},{"vulnId":"V-205708","ruleId":"SV-205708r971535_rule","severity":"medium","ruleTitle":"Windows Server 2019 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites.","description":"Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption.\n\nNote: 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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\Parameters\\\n\nValue Name: SupportedEncryptionTypes\n\nValue Type: REG_DWORD\nValue: 0x7ffffff8 (2147483640)","fixText":"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:\n\nAES128_HMAC_SHA1\nAES256_HMAC_SHA1\nFuture encryption types\n\nNote: 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.","ccis":["CCI-000803"]},{"vulnId":"V-205709","ruleId":"SV-205709r958504_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have the built-in guest account disabled.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options.\n\nIf the value for \"Accounts: Guest account status\" is not set to \"Disabled\", this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"EnableGuestAccount\" equals \"1\" in the file, this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> \"Accounts: Guest account status\" to \"Disabled\".","ccis":["CCI-000804"]},{"vulnId":"V-205710","ruleId":"SV-205710r958508_rule","severity":"medium","ruleTitle":"Windows Server 2019 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours.","description":"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.\n\nEmergency 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.\n\nTo address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.","checkContent":"Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA.\n\nIf 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.\n\nIf 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.\n\nDomain Controllers:\n\nOpen \"PowerShell\".\n\nEnter \"Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate\".\n\nIf \"AccountExpirationDate\" has been defined and is not within 72 hours for an emergency administrator account, this is a finding.\n\nMember servers and standalone or nondomain-joined systems:\n\nOpen \"Command Prompt\".\n\nRun \"Net user [username]\", where [username] is the name of the emergency account.\n\nIf \"Account expires\" has been defined and is not within 72 hours for an emergency administrator account, this is a finding.","fixText":"Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours.\n\nDomain accounts can be configured with an account expiration date, under \"Account\" properties.\n\nLocal 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.","ccis":["CCI-001682"]},{"vulnId":"V-205711","ruleId":"SV-205711r958510_rule","severity":"high","ruleTitle":"Windows Server 2019 Windows Remote Management (WinRM) client must not use Basic authentication.","description":"Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\WinRM\\Client\\\n\nValue Name: AllowBasic\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Client >> \"Allow Basic authentication\" to \"Disabled\".","ccis":["CCI-000877"]},{"vulnId":"V-205712","ruleId":"SV-205712r958510_rule","severity":"medium","ruleTitle":"Windows Server 2019 Windows Remote Management (WinRM) client must not use Digest authentication.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\WinRM\\Client\\\n\nValue Name: AllowDigest\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Client >> \"Disallow Digest authentication\" to \"Enabled\".","ccis":["CCI-000877"]},{"vulnId":"V-205713","ruleId":"SV-205713r958510_rule","severity":"high","ruleTitle":"Windows Server 2019 Windows Remote Management (WinRM) service must not use Basic authentication.","description":"Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\WinRM\\Service\\\n\nValue Name: AllowBasic\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Service >> \"Allow Basic authentication\" to \"Disabled\".","ccis":["CCI-000877"]},{"vulnId":"V-205714","ruleId":"SV-205714r958518_rule","severity":"medium","ruleTitle":"Windows Server 2019 administrator accounts must not be enumerated during elevation.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\CredUI\\\n\nValue Name: EnumerateAdministrators\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Credential User Interface >> \"Enumerate administrator accounts on elevation\" to \"Disabled\".","ccis":["CCI-001084"]},{"vulnId":"V-205715","ruleId":"SV-205715r958518_rule","severity":"medium","ruleTitle":"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.","description":"A compromised local administrator account can provide means for an attacker to move laterally between domain systems.\n\nWith 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.","checkContent":"This applies to member servers. For domain controllers and standalone or nondomain-joined systems, this is NA.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive:  HKEY_LOCAL_MACHINE\nRegistry Path:  \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\n\nValue Name:  LocalAccountTokenFilterPolicy\n\nType:  REG_DWORD\nValue: 0x00000000 (0)\n\nThis 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.","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> MS Security Guide >> \"Apply UAC restrictions to local accounts on network logons\" to \"Enabled\".\n\nThis 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.","ccis":["CCI-001084"]},{"vulnId":"V-205716","ruleId":"SV-205716r958518_rule","severity":"medium","ruleTitle":"Windows Server 2019 UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.","description":"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.","checkContent":"UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience).\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: EnableUIADesktopToggle\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0)","fixText":"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\".","ccis":["CCI-001084"]},{"vulnId":"V-205717","ruleId":"SV-205717r958518_rule","severity":"medium","ruleTitle":"Windows Server 2019 User Account Control must, at a minimum, prompt administrators for consent on the secure desktop.","description":"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.","checkContent":"UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2019 versus Server with Desktop Experience).\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: ConsentPromptBehaviorAdmin\n\nValue Type: REG_DWORD\nValue: 0x00000002 (2) (Prompt for consent on the secure desktop)\n0x00000001 (1) (Prompt for credentials on the secure desktop)","fixText":"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\".\n\nThe more secure option for this setting, \"Prompt for credentials on the secure desktop\", would also be acceptable.","ccis":["CCI-001084"]},{"vulnId":"V-205718","ruleId":"SV-205718r958518_rule","severity":"medium","ruleTitle":"Windows Server 2019 User Account Control must be configured to detect application installations and prompt for elevation.","description":"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.","checkContent":"UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience).\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: EnableInstallerDetection\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-001084"]},{"vulnId":"V-205719","ruleId":"SV-205719r958518_rule","severity":"medium","ruleTitle":"Windows Server 2019 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.","description":"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.","checkContent":"UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience).\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: EnableSecureUIAPaths\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-001084"]},{"vulnId":"V-205720","ruleId":"SV-205720r958518_rule","severity":"medium","ruleTitle":"Windows Server 2019 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.","description":"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.","checkContent":"UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience).\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: EnableVirtualization\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-001084"]},{"vulnId":"V-205721","ruleId":"SV-205721r1137695_rule","severity":"medium","ruleTitle":"Windows Server 2019 non-system-created file shares must limit access to groups that require it.","description":"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.","checkContent":"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.)\n\nRun \"Computer Management\".\n\nNavigate to System Tools >> Shared Folders >> Shares.\n\nRight-click any non-system-created shares.\n\nSelect \"Properties\".\n\nSelect the \"Share Permissions\" tab.\n\nIf the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding.\n\nSelect the \"Security\" tab.\n\nIf the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding.","fixText":"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.\n\nRemove any unnecessary non-system-created shares.","ccis":["CCI-001090"]},{"vulnId":"V-205722","ruleId":"SV-205722r1137695_rule","severity":"medium","ruleTitle":"Windows Server 2019 Remote Desktop Services must prevent drive redirection.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows NT\\Terminal Services\\\n\nValue Name: fDisableCdm\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-001090"]},{"vulnId":"V-205723","ruleId":"SV-205723r1137695_rule","severity":"medium","ruleTitle":"Windows Server 2019 data files owned by users must be on a different logical partition from the directory server data files.","description":"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. \n\nThe 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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nRun \"Regedit\".\n\nNavigate to \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\NTDS\\Parameters\".\n\nNote the directory locations in the values for \"DSA Database file\".\n\nOpen \"Command Prompt\".\n\nEnter \"net share\".\n\nNote the logical drive(s) or file system partition for any organization-created data shares.\n\nIgnore system shares (e.g., NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) should not be ignored.\n\nIf user shares are located on the same logical partition as the directory server data files, this is a finding.","fixText":"Move shares used to store files owned by users to a different logical partition than the directory server data files.","ccis":["CCI-001090"]},{"vulnId":"V-205724","ruleId":"SV-205724r1137695_rule","severity":"high","ruleTitle":"Windows Server 2019 must not allow anonymous enumeration of shares.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\\n\nValue Name: RestrictAnonymous\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-001090"]},{"vulnId":"V-205725","ruleId":"SV-205725r1137695_rule","severity":"high","ruleTitle":"Windows Server 2019 must restrict anonymous access to Named Pipes and Shares.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\LanManServer\\Parameters\\\n\nValue Name: RestrictNullSessAccess\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-001090"]},{"vulnId":"V-205726","ruleId":"SV-205726r970703_rule","severity":"low","ruleTitle":"Windows Server 2019 directory service must be configured to terminate LDAP-based network connections to the directory server after five minutes of inactivity.","description":"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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nOpen an elevated \"Command Prompt\" (run as administrator).\n\nEnter \"ntdsutil\".\n\nAt the \"ntdsutil:\" prompt, enter \"LDAP policies\".\n\nAt the \"ldap policy:\" prompt, enter \"connections\".\n\nAt the \"server connections:\" prompt, enter \"connect to server [host-name]\"\n(where [host-name] is the computer name of the domain controller).\n\nAt the \"server connections:\" prompt, enter \"q\".\n\nAt the \"ldap policy:\" prompt, enter \"show values\". \n\nIf the value for MaxConnIdleTime is greater than \"300\" (5 minutes) or is not specified, this is a finding.\n\nEnter \"q\" at the \"ldap policy:\" and \"ntdsutil:\" prompts to exit.\n\nAlternately, Dsquery can be used to display MaxConnIdleTime:\n\nOpen \"Command Prompt (Admin)\".\nEnter the following command (on a single line).\n\ndsquery * \"cn=Default Query Policy,cn=Query-Policies,cn=Directory Service, cn=Windows NT,cn=Services,cn=Configuration,dc=[forest-name]\" -attr LDAPAdminLimits \n\nThe quotes are required and dc=[forest-name] is the fully qualified LDAP name of the domain being reviewed (e.g., dc=disaost,dc=mil).\n\nIf the results do not specify a \"MaxConnIdleTime\" or it has a value greater than \"300\" (5 minutes), this is a finding.","fixText":"Configure the directory service to terminate LDAP-based network connections to the directory server after 5 minutes of inactivity.\n\nOpen an elevated \"Command prompt\" (run as administrator).\n\nEnter \"ntdsutil\".\n\nAt the \"ntdsutil:\" prompt, enter \"LDAP policies\".\n\nAt the \"ldap policy:\" prompt, enter \"connections\".\n\nAt the \"server connections:\" prompt, enter \"connect to server [host-name]\" (where [host-name] is the computer name of the domain controller).\n\nAt the \"server connections:\" prompt, enter \"q\".\n\nAt the \"ldap policy:\" prompt, enter \"Set MaxConnIdleTime to 300\".\n\nEnter \"Commit Changes\" to save.\n\nEnter \"Show values\" to verify changes.\n\nEnter \"q\" at the \"ldap policy:\" and \"ntdsutil:\" prompts to exit.","ccis":["CCI-001133"]},{"vulnId":"V-205727","ruleId":"SV-205727r958552_rule","severity":"high","ruleTitle":"Windows Server 2019 systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.","description":"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.\n\nSelection 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).\n\nSatisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184","checkContent":"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.\n\nIf they do not, this is a finding.","fixText":"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.","ccis":["CCI-001199","CCI-002475","CCI-002476"]},{"vulnId":"V-205730","ruleId":"SV-205730r991552_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Logon/Logoff - Account Lockout failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAccount Lockout events can be used to identify potentially malicious logon attempts.\n\nSatisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nLogon/Logoff >> Account Lockout - Failure","fixText":"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.","ccis":["CCI-000172","CCI-001404"]},{"vulnId":"V-205731","ruleId":"SV-205731r991558_rule","severity":"medium","ruleTitle":"Windows Server 2019 Event Viewer must be protected from unauthorized modification and deletion.","description":"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.\n\nOperating 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.\n\nSatisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099","checkContent":"This is not applicable for Windows Core Editions\n\nNavigate to \"%SystemRoot%\\System32\".\n\nView the permissions on \"Eventvwr.exe\".\n\nIf any groups or accounts other than TrustedInstaller have \"Full control\" or \"Modify\" permissions, this is a finding.\n\nThe default permissions below satisfy this requirement:\n\nTrustedInstaller - Full Control\nAdministrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute","fixText":"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:\n\nTrustedInstaller - Full Control\nAdministrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read & Execute\n\nThe default location is the \"%SystemRoot%\\System32\" folder.","ccis":["CCI-001494","CCI-001495"]},{"vulnId":"V-205732","ruleId":"SV-205732r958672_rule","severity":"medium","ruleTitle":"Windows Server 2019 Deny log on through Remote Desktop Services user right on domain controllers must be configured to prevent unauthenticated access.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on through Remote Desktop Services\" user right defines the accounts that are prevented from logging on using Remote Desktop Services.\n\nThe Guests group must be assigned this right to prevent unauthenticated access.","checkContent":"This applies to domain controllers. A separate version applies to other systems.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf the following accounts or groups are not defined for the \"Deny log on through Remote Desktop Services\" user right, this is a finding:\n\n- Guests Group\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf the following SID(s) are not defined for the \"SeDenyRemoteInteractiveLogonRight\" user right, this is a finding.\n\nS-1-5-32-546 (Guests)","fixText":"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:\n\n- Guests Group","ccis":["CCI-002314"]},{"vulnId":"V-205733","ruleId":"SV-205733r958672_rule","severity":"medium","ruleTitle":"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.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on through Remote Desktop Services\" user right defines the accounts that are prevented from logging on using Remote Desktop Services.\n\nIn 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.\n\nLocal accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks.\n\nThe Guests group must be assigned this right to prevent unauthenticated access.","checkContent":"This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf the following accounts or groups are not defined for the \"Deny log on through Remote Desktop Services\" user right, this is a finding:\n\nDomain Systems Only:\n- Enterprise Admins group\n- Domain Admins group\n- Local account (see Note below)\n\nAll Systems:\n- Guests group\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf the following SIDs are not defined for the \"SeDenyRemoteInteractiveLogonRight\" user right, this is a finding.\n\nDomain Systems Only:\nS-1-5-root domain-519 (Enterprise Admins)\nS-1-5-domain-512 (Domain Admins)\nS-1-5-113 (\"Local account\")\n\nAll Systems:\nS-1-5-32-546 (Guests)\n\nNote: \"Local account\" is referring to the Windows built-in security group.","fixText":"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:\n\nDomain Systems Only:\n- Enterprise Admins group\n- Domain Admins group\n- Local account (see Note below)\n\nAll Systems:\n- Guests group\n\nNote: \"Local account\" is referring to the Windows built-in security group.","ccis":["CCI-002314"]},{"vulnId":"V-205734","ruleId":"SV-205734r958702_rule","severity":"medium","ruleTitle":"Windows Server 2019 permissions for the system drive root directory (usually C:\\) must conform to minimum requirements.","description":"Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.\n\nThe default permissions are adequate when the Security Option \"Network access: Let Everyone permissions apply to anonymous users\" is set to \"Disabled\" (WN19-SO-000240).\n\nSatisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124","checkContent":"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).\n\nReview 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.\n\nIf permissions are not as restrictive as the default permissions listed below, this is a finding.\n\nViewing in File Explorer:\n\nView the Properties of the system drive's root directory.\n\nSelect the \"Security\" tab, and the \"Advanced\" button.\n\nDefault permissions:\nC:\\\nType - \"Allow\" for all\nInherited from - \"None\" for all\n\nPrincipal - Access - Applies to\n\nSYSTEM - Full control - This folder, subfolders, and files\nAdministrators - Full control - This folder, subfolders, and files\nUsers - Read & execute - This folder, subfolders, and files\nUsers - Create folders/append data - This folder and subfolders\nUsers - Create files/write data - Subfolders only\nCREATOR OWNER - Full Control - Subfolders and files only\n\nAlternately, use icacls:\n\nOpen \"Command Prompt (Admin)\".\n\nEnter \"icacls\" followed by the directory:\n\n\"icacls c:\\\"\n\nThe following results should be displayed:\n\nc:\\\nNT AUTHORITY\\SYSTEM:(OI)(CI)(F)\nBUILTIN\\Administrators:(OI)(CI)(F)\nBUILTIN\\Users:(OI)(CI)(RX)\nBUILTIN\\Users:(CI)(AD)\nBUILTIN\\Users:(CI)(IO)(WD)\nCREATOR OWNER:(OI)(CI)(IO)(F)\nSuccessfully processed 1 files; Failed processing 0 files","fixText":"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).\n\nDefault Permissions\nC:\\\nType - \"Allow\" for all\nInherited from - \"None\" for all\n\nPrincipal - Access - Applies to\n\nSYSTEM - Full control - This folder, subfolders, and files\nAdministrators - Full control - This folder, subfolders, and files\nUsers - Read & execute - This folder, subfolders, and files\nUsers - Create folders/append data - This folder and subfolders\nUsers - Create files/write data - Subfolders only\nCREATOR OWNER - Full Control - Subfolders and files only","ccis":["CCI-002165"]},{"vulnId":"V-205735","ruleId":"SV-205735r958702_rule","severity":"medium","ruleTitle":"Windows Server 2019 permissions for program file directories must conform to minimum requirements.","description":"Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.\n\nThe default permissions are adequate when the Security Option \"Network access: Let Everyone permissions apply to anonymous users\" is set to \"Disabled\" (WN19-SO-000240).\n\nSatisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124","checkContent":"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).\n\nReview 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.\n\nIf permissions are not as restrictive as the default permissions listed below, this is a finding.\n\nViewing in File Explorer:\n\nFor each folder, view the Properties.\n\nSelect the \"Security\" tab, and the \"Advanced\" button.\n\nDefault permissions:\n\\Program Files and \\Program Files (x86)\nType - \"Allow\" for all\nInherited from - \"None\" for all\n\nPrincipal - Access - Applies to\n\nTrustedInstaller - Full control - This folder and subfolders\nSYSTEM - Modify - This folder only\nSYSTEM - Full control - Subfolders and files only\nAdministrators - Modify - This folder only\nAdministrators - Full control - Subfolders and files only\nUsers - Read & execute - This folder, subfolders and files\nCREATOR OWNER - Full control - Subfolders and files only\nALL APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files\nALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files\n\nAlternately, use icacls:\n\nOpen a Command prompt (admin).\n\nEnter \"icacls\" followed by the directory:\n\n'icacls \"c:\\program files\"'\n'icacls \"c:\\program files (x86)\"'\n\nThe following results should be displayed for each when entered:\n\nc:\\program files (c:\\program files (x86))\nNT SERVICE\\TrustedInstaller:(F)\nNT SERVICE\\TrustedInstaller:(CI)(IO)(F)\nNT AUTHORITY\\SYSTEM:(M)\nNT AUTHORITY\\SYSTEM:(OI)(CI)(IO)(F)\nBUILTIN\\Administrators:(M)\nBUILTIN\\Administrators:(OI)(CI)(IO)(F)\nBUILTIN\\Users:(RX)\nBUILTIN\\Users:(OI)(CI)(IO)(GR,GE)\nCREATOR OWNER:(OI)(CI)(IO)(F)\nAPPLICATION PACKAGE AUTHORITY\\ALL APPLICATION PACKAGES:(RX)\nAPPLICATION PACKAGE AUTHORITY\\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)\nAPPLICATION PACKAGE AUTHORITY\\ALL RESTRICTED APPLICATION PACKAGES:(RX)\nAPPLICATION PACKAGE AUTHORITY\\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)\nSuccessfully processed 1 files; Failed processing 0 files","fixText":"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).\n\nDefault permissions:\n\\Program Files and \\Program Files (x86)\nType - \"Allow\" for all\nInherited from - \"None\" for all\n\nPrincipal - Access - Applies to\n\nTrustedInstaller - Full control - This folder and subfolders\nSYSTEM - Modify - This folder only\nSYSTEM - Full control - Subfolders and files only\nAdministrators - Modify - This folder only\nAdministrators - Full control - Subfolders and files only\nUsers - Read & execute - This folder, subfolders, and files\nCREATOR OWNER - Full control - Subfolders and files only\nALL APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files\nALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files","ccis":["CCI-002165"]},{"vulnId":"V-205736","ruleId":"SV-205736r1016383_rule","severity":"medium","ruleTitle":"Windows Server 2019 permissions for the Windows installation directory must conform to minimum requirements.","description":"Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.\n\nThe default permissions are adequate when the Security Option \"Network access: Let Everyone permissions apply to anonymous users\" is set to \"Disabled\" (WN19-SO-000240).\n\nSatisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124","checkContent":"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).\n\nReview 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.\n\nIf permissions are not as restrictive as the default permissions listed below, this is a finding:\n\n\nFor each folder, view the Properties.\n\nSelect the \"Security\" tab and the \"Advanced\" button.\n\nDefault permissions:\n\\Windows\nType - \"Allow\" for all\nInherited from - \"None\" for all\n\nPrincipal - Access - Applies to\n\nTrustedInstaller - Full control - This folder and subfolders\nSYSTEM - Modify - This folder only\nSYSTEM - Full control - Subfolders and files only\nAdministrators - Modify - This folder only\nAdministrators - Full control - Subfolders and files only\nUsers - Read & execute - This folder, subfolders, and files\nCREATOR OWNER - Full control - Subfolders and files only\nALL APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files\nALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files\n\nAlternately, use icacls:\n\nOpen a Command prompt (admin).\n\nEnter \"icacls\" followed by the directory:\n\n\"icacls c:\\windows\"\n\nThe following results should be displayed for each when entered:\n\nc:\\windows\nNT SERVICE\\TrustedInstaller:(F)\nNT SERVICE\\TrustedInstaller:(CI)(IO)(F)\nNT AUTHORITY\\SYSTEM:(M)\nNT AUTHORITY\\SYSTEM:(OI)(CI)(IO)(F)\nBUILTIN\\Administrators:(M)\nBUILTIN\\Administrators:(OI)(CI)(IO)(F)\nBUILTIN\\Users:(RX)\nBUILTIN\\Users:(OI)(CI)(IO)(GR,GE)\nCREATOR OWNER:(OI)(CI)(IO)(F)\nAPPLICATION PACKAGE AUTHORITY\\ALL APPLICATION PACKAGES:(RX)\nAPPLICATION PACKAGE AUTHORITY\\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)\nAPPLICATION PACKAGE AUTHORITY\\ALL RESTRICTED APPLICATION PACKAGES:(RX)\nAPPLICATION PACKAGE AUTHORITY\\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)\nSuccessfully processed 1 files; Failed processing 0 files","fixText":"Maintain the default file ACLs and configure the Security Option \"Network access: Let Everyone permissions apply to anonymous users\" to \"Disabled\" (WN19-SO-000240).\n\nDefault permissions:\nType - \"Allow\" for all\nInherited from - \"None\" for all\n\nPrincipal - Access - Applies to\n\nTrustedInstaller - Full control - This folder and subfolders\nSYSTEM - Modify - This folder only\nSYSTEM - Full control - Subfolders and files only\nAdministrators - Modify - This folder only\nAdministrators - Full control - Subfolders and files only\nUsers - Read & execute - This folder, subfolders, and files\nCREATOR OWNER - Full control - Subfolders and files only\nALL APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files\nALL RESTRICTED APPLICATION PACKAGES - Read & execute - This folder, subfolders, and files","ccis":["CCI-002165"]},{"vulnId":"V-205737","ruleId":"SV-205737r1153434_rule","severity":"medium","ruleTitle":"Windows Server 2019 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained.","description":"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.","checkContent":"Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below.\n\nIf any nonprivileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding.\n\nIf permissions are not as restrictive as the default permissions listed below, this is a finding:\n\nRun \"Regedit\".\n\nRight-click on the registry areas noted below.\n\nSelect \"Permissions\" and \"Advanced\".\n\nHKEY_LOCAL_MACHINE\\SECURITY\n\nType - \"Allow\" for all\nInherited from - \"None\" for all\nPrincipal - Access - Applies to\nSYSTEM - Full Control - This key and subkeys\nAdministrators - Special - This key and subkeys\n\nHKEY_LOCAL_MACHINE\\SOFTWARE\n\nType - \"Allow\" for all\nInherited from - \"None\" for all\nPrincipal - Access - Applies to\nUsers - Read - This key and subkeys\nAdministrators - Full Control - This key and subkeys\nSYSTEM - Full Control - This key and subkeys\nCREATOR OWNER - Full Control - This key and subkeys\nALL APPLICATION PACKAGES - Read - This key and subkeys\n\nHKEY_LOCAL_MACHINE\\SYSTEM\n\nType - \"Allow\" for all\nInherited from - \"None\" for all\nPrincipal - Access - Applies to\nAuthenticated Users - Read - This key and subkeys\nAdministrators - Full Control - This key and subkeys\nSYSTEM - Full Control - This key and subkeys\nCREATOR OWNER - Full Control - Subkeys only\nALL APPLICATION PACKAGES - Read - This key and subkeys\nServer Operators – Read – This Key and subkeys    (Domain controllers only)\n\nOther examples under the noted keys may also be sampled. There may be some instances where non-privileged groups have greater than Read permission.\n\nMicrosoft 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.\nS-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681\n\nIf the defaults have not been changed, these are not a finding.","fixText":"Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive.\n\nThe default permissions of the higher-level keys are noted below.\n\nHKEY_LOCAL_MACHINE\\SECURITY\n\nType - \"Allow\" for all\nInherited from - \"None\" for all\nPrincipal - Access - Applies to\nSYSTEM - Full Control - This key and subkeys\nAdministrators - Special - This key and subkeys\n\nHKEY_LOCAL_MACHINE\\SOFTWARE\n\nType - \"Allow\" for all\nInherited from - \"None\" for all\nPrincipal - Access - Applies to\nUsers - Read - This key and subkeys\nAdministrators - Full Control - This key and subkeys\nSYSTEM - Full Control - This key and subkeys\nCREATOR OWNER - Full Control - This key and subkeys\nALL APPLICATION PACKAGES - Read - This key and subkeys\n\nHKEY_LOCAL_MACHINE\\SYSTEM\n\nType - \"Allow\" for all\nInherited from - \"None\" for all\nPrincipal - Access - Applies to\nAuthenticated Users - Read - This key and subkeys\nAdministrators - Full Control - This key and subkeys\nSYSTEM - Full Control - This key and subkeys\nCREATOR OWNER - Full Control - Subkeys only\nALL APPLICATION PACKAGES - Read - This key and subkeys\nServer Operators – Read – This Key and subkeys    (Domain controllers only)\n\nMicrosoft has also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2019 to the following SID:\nS-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681","ccis":["CCI-002235"]},{"vulnId":"V-205738","ruleId":"SV-205738r958726_rule","severity":"high","ruleTitle":"Windows Server 2019 must only allow administrators responsible for the domain controller to have Administrator rights on the system.","description":"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.\n\nSystem administrators must log on to systems using only accounts with the minimum level of authority necessary. \n\nStandard user accounts must not be members of the built-in Administrators group.","checkContent":"This applies to domain controllers. A separate version applies to other systems.\n\nReview the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group.\n\nStandard user accounts must not be members of the local administrator group.\n\nIf prohibited accounts are members of the local administrators group, this is a finding.\n\nIf the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.","fixText":"Configure the Administrators group to include only administrator groups or accounts that are responsible for the system.\n\nRemove any standard user accounts.","ccis":["CCI-002235"]},{"vulnId":"V-205739","ruleId":"SV-205739r958726_rule","severity":"high","ruleTitle":"Windows Server 2019 permissions on the Active Directory data files must only allow System and Administrators access.","description":"Improper access permissions for directory data-related files could allow unauthorized users to read, modify, or delete directory data or audit trails.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nRun \"Regedit\".\n\nNavigate to \"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\NTDS\\Parameters\".\n\nNote the directory locations in the values for:\n\nDatabase log files path\nDSA Database file\n\nBy default, they will be \\Windows\\NTDS.\n\nIf the locations are different, the following will need to be run for each.\n\nOpen \"Command Prompt (Admin)\".\n\nNavigate to the NTDS directory (\\Windows\\NTDS by default).\n\nRun \"icacls *.*\".\n\nIf the permissions on each file are not as restrictive as the following, this is a finding:\n\nNT AUTHORITY\\SYSTEM:(I)(F)\nBUILTIN\\Administrators:(I)(F)\n\n(I) - permission inherited from parent container\n(F) - full access","fixText":"Maintain the permissions on NTDS database and log files as follows:\n\nNT AUTHORITY\\SYSTEM:(I)(F)\nBUILTIN\\Administrators:(I)(F)\n\n(I) - permission inherited from parent container\n(F) - full access","ccis":["CCI-002235"]},{"vulnId":"V-205740","ruleId":"SV-205740r958726_rule","severity":"high","ruleTitle":"Windows Server 2019 Active Directory SYSVOL directory must have the proper access control permissions.","description":"Improper access permissions for directory data files could allow unauthorized users to read, modify, or delete directory data.\n\nThe 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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nOpen a command prompt.\n\nRun \"net share\".\n\nMake note of the directory location of the SYSVOL share.\n\nBy default, this will be \\Windows\\SYSVOL\\sysvol. For this requirement, permissions will be verified at the first SYSVOL directory level.\n\nIf any standard user accounts or groups have greater than \"Read & execute\" permissions, this is a finding. \n\nThe default permissions noted below meet this requirement:\n\nOpen \"Command Prompt\".\n\nRun \"icacls c:\\Windows\\SYSVOL\".\n\nThe following results should be displayed:\n\nNT AUTHORITY\\Authenticated Users:(RX)\nNT AUTHORITY\\Authenticated Users:(OI)(CI)(IO)(GR,GE)\nBUILTIN\\Server Operators:(RX)\nBUILTIN\\Server Operators:(OI)(CI)(IO)(GR,GE)\nBUILTIN\\Administrators:(M,WDAC,WO)\nBUILTIN\\Administrators:(OI)(CI)(IO)(F)\nNT AUTHORITY\\SYSTEM:(F)\nNT AUTHORITY\\SYSTEM:(OI)(CI)(IO)(F)\nCREATOR OWNER:(OI)(CI)(IO)(F)\n\n(RX) - Read & execute \n\nRun \"icacls /help\" to view definitions of other permission codes.","fixText":"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:\n\nC:\\Windows\\SYSVOL\nType - \"Allow\" for all\nInherited from - \"None\" for all\n\nPrincipal - Access - Applies to\n\nAuthenticated Users - Read & execute - This folder, subfolder, and files\nServer Operators - Read & execute- This folder, subfolder, and files\nAdministrators - Special - This folder only (Special = Basic Permissions: all selected except Full control)\nCREATOR OWNER - Full control - Subfolders and files only\nAdministrators - Full control - Subfolders and files only\nSYSTEM - Full control - This folder, subfolders, and files","ccis":["CCI-002235"]},{"vulnId":"V-205741","ruleId":"SV-205741r1081998_rule","severity":"high","ruleTitle":"Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions.","description":"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.\n\nFor 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).","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the permissions on Group Policy objects.\n\nOpen \"Group Policy Management\" (available from various menus or run \"gpmc.msc\").\n\nNavigate to \"Group Policy Objects\" in the domain being reviewed (Forest >> Domains >> Domain).\n\nFor each Group Policy object:\n\nSelect the Group Policy object item in the left pane.\n\nSelect the \"Delegation\" tab in the right pane.\n\nSelect \"Advanced\".\n\nSelect each Group or user name.\n\nView the permissions.\n\nIf any standard user accounts or groups have \"Allow\" permissions greater than \"Read\" and \"Apply group policy\", this is a finding.\n\nOther access permissions that allow the objects to be updated are considered findings unless specifically documented by the ISSO.\n\nThe default permissions noted below satisfy this requirement. \n\nThe permissions shown are at the summary level. To view more detailed permissions, select the next \"Advanced\" button, the desired Permission entry, and then click \"Edit\".\n\nAuthenticated Users - Read, Apply group policy, Special permissions\n\nThe 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.\n\nThe special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties:\n\nCREATOR OWNER - Special permissions\nSYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions\nDomain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions\nEnterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions\nENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions","fixText":"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:\n\nAuthenticated Users - Read, Apply group policy, Special permissions\n\nThe special permissions for Authenticated Users are for Read-type Properties.\n\nCREATOR OWNER - Special permissions\nSYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions\nDomain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions\nEnterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions\nENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions\n\nDocument any other access permissions that allow the objects to be updated with the ISSO.","ccis":["CCI-002235"]},{"vulnId":"V-205742","ruleId":"SV-205742r958726_rule","severity":"high","ruleTitle":"Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions.","description":"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.\n\nThe 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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the permissions on the Domain Controllers OU.\n\nOpen \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nSelect \"Advanced Features\" in the \"View\" menu if not previously selected.\n\nSelect the \"Domain Controllers\" OU (folder in folder icon).\n\nRight-click and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nIf the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding.\n\nThe default permissions listed below satisfy this requirement.\n\nDomains 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.\n\nThe 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.\n\nExcept where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement.\n\nCREATOR OWNER - Special permissions\n\nSELF - Special permissions\n\nAuthenticated Users - Read, Special permissions\n\nThe special permissions for Authenticated Users are Read types.\n\nIf detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding.\n\nSYSTEM - Full Control\n\nDomain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions\n\nEnterprise Admins - Full Control\n\nKey Admins - Special permissions\n\nEnterprise Key Admins - Special permissions\n\nAdministrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions\n\nPre-Windows 2000 Compatible Access - Special permissions\n\nThe Special permissions for Pre-Windows 2000 Compatible Access are Read types.\n\nIf detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding.\n\nENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions","fixText":"Limit the permissions on the Domain Controllers OU to restrict changes to System, Domain Admins, Enterprise Admins and Administrators.\n\nThe default permissions listed below satisfy this requirement.\n\nDomains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU.  These may include some change related permissions.\n\nCREATOR OWNER - Special permissions\n\nSELF - Special permissions\n\nAuthenticated Users - Read, Special permissions\n\nThe special permissions for Authenticated Users are Read types.\n\nSYSTEM - Full Control\n\nDomain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions\n\nEnterprise Admins - Full Control\n\nKey Admins - Special permissions\n\nEnterprise Key Admins - Special permissions\n\nAdministrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions\n\nPre-Windows 2000 Compatible Access - Special permissions\n\nThe special permissions for Pre-Windows 2000 Compatible Access are Read types.\n\nENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions","ccis":["CCI-002235"]},{"vulnId":"V-205743","ruleId":"SV-205743r958726_rule","severity":"high","ruleTitle":"Windows Server 2019 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions.","description":"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.\n\nFor 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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the permissions on domain-defined OUs.\n\nOpen \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nFor each OU that is defined (folder in folder icon) excluding the Domain Controllers OU:\n\nRight-click the OU and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nIf the Allow type permissions on the OU are not at least as restrictive as those below, this is a finding.\n\nThe 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.\n\nExcept where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement.\n\nCREATOR OWNER - Special permissions\n\nSelf - Special permissions\n\nAuthenticated Users - Read, Special permissions\n\nThe 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.\n\nSYSTEM - Full Control\n\nDomain Admins - Full Control\n\nEnterprise Admins - Full Control\n\nKey Admins - Special permissions\n\nEnterprise Key Admins - Special permissions\n\nAdministrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions\n\nPre-Windows 2000 Compatible Access - Special permissions\n\nThe 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.\n\nENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions\n\nIf 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.\n\nIf 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).\n\nIf 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).","fixText":"Maintain the Allow type permissions on domain-defined OUs to be at least as restrictive as the defaults below.\n\nDocument any additional permissions above Read with the ISSO if an approved distributed administration model (help desk or other user support staff) is implemented.\n\nCREATOR OWNER - Special permissions\n\nSelf - Special permissions\n\nAuthenticated Users - Read, Special permissions\n\nThe special permissions for Authenticated Users are Read type.\n\nSYSTEM - Full Control\n\nDomain Admins - Full Control\n\nEnterprise Admins - Full Control\n\nKey Admins - Special permissions\n\nEnterprise Key Admins - Special permissions\n\nAdministrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions\n\nPre-Windows 2000 Compatible Access - Special permissions\n\nThe special permissions for Pre-Windows 2000 Compatible Access are for Read types.\n\nENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions","ccis":["CCI-002235"]},{"vulnId":"V-205744","ruleId":"SV-205744r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Add workstations to domain user right must only be assigned to the Administrators group on domain controllers.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts 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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Add workstations to domain\" right, this is a finding.\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeMachineAccountPrivilege\" user right, this is a finding.\n\nS-1-5-32-544 (Administrators)","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205745","ruleId":"SV-205745r958726_rule","severity":"medium","ruleTitle":"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.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"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.","checkContent":"This applies to domain controllers. A separate version applies to other systems.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf 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.\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeEnableDelegationPrivilege\" user right, this is a finding.\n\nS-1-5-32-544 (Administrators)","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205746","ruleId":"SV-205746r958726_rule","severity":"high","ruleTitle":"Windows Server 2019 must only allow Administrators responsible for the member server or standalone or nondomain-joined system to have Administrator rights on the system.","description":"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.\n\nSystem administrators must log on to systems using only accounts with the minimum level of authority necessary.\n\nFor domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group (refer to AD.0003 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.\n\nStandard user accounts must not be members of the built-in Administrators group.","checkContent":"This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.\n\nOpen \"Computer Management\".\n\nNavigate to \"Groups\" under \"Local Users and Groups\".\n\nReview the local \"Administrators\" group.\n\nOnly administrator groups or accounts responsible for administration of the system may be members of the group.\n\nFor domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group.\n\nStandard user accounts must not be members of the local Administrator group.\n\nIf accounts that do not have responsibility for administration of the system are members of the local Administrators group, this is a finding.\n\nIf the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.","fixText":"Configure the local \"Administrators\" group to include only administrator groups or accounts responsible for administration of the system.\n\nFor domain-joined member servers, replace the Domain Admins group with a domain member server administrator group. \n\nRemove any standard user accounts.","ccis":["CCI-002235"]},{"vulnId":"V-205747","ruleId":"SV-205747r1106518_rule","severity":"medium","ruleTitle":"Windows Server 2019 must restrict remote calls to the Security Account Manager (SAM) to Administrators on domain-joined member servers and standalone or nondomain-joined systems.","description":"The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.","checkContent":"This applies to member servers and standalone or nondomain-joined systems. It is NA for domain controllers.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\\n\nValue Name: RestrictRemoteSAM\n\nValue Type: REG_SZ\nValue: O:BAG:BAD:(A;;RC;;;BA)","fixText":"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\". \n\nSelect \"Edit Security\" to configure the \"Security descriptor:\".\n\nAdd \"Administrators\" in \"Group or user names:\" if it is not already listed (this is the default).\n\nSelect \"Administrators\" in \"Group or user names:\".\n\nSelect \"Allow\" for \"Remote Access\" in \"Permissions for \"Administrators\".\n\nClick \"OK\".\n\nThe \"Security descriptor:\" must be populated with \"O:BAG:BAD:(A;;RC;;;BA) for the policy to be enforced. If an application requires this user right, this is not a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented and approved by the information system security officer (ISSO).","ccis":["CCI-002235"]},{"vulnId":"V-205748","ruleId":"SV-205748r958726_rule","severity":"medium","ruleTitle":"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 or nondomain-joined systems.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"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.","checkContent":"This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups are granted the \"Enable computer and user accounts to be trusted for delegation\" user right, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs are granted the \"SeEnableDelegationPrivilege\" user right, this is a finding.","fixText":"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).","ccis":["CCI-002235"]},{"vulnId":"V-205749","ruleId":"SV-205749r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Access Credential Manager as a trusted caller\" user right may be able to retrieve the credentials of other accounts from Credential Manager.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups are granted the \"Access Credential Manager as a trusted caller\" user right, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs are granted the \"SeTrustedCredManAccessPrivilege\" user right, this is a finding.","fixText":"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).","ccis":["CCI-002235"]},{"vulnId":"V-205750","ruleId":"SV-205750r958726_rule","severity":"high","ruleTitle":"Windows Server 2019 Act as part of the operating system user right must not be assigned to any groups or accounts.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts 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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups (to include administrators), are granted the \"Act as part of the operating system\" user right, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs are granted the \"SeTcbPrivilege\" user right, this is a finding.\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).\n\nPasswords for accounts with this user right must be protected as highly privileged accounts.","fixText":"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).","ccis":["CCI-002235"]},{"vulnId":"V-205751","ruleId":"SV-205751r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Back up files and directories user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Back up files and directories\" user right can circumvent file and directory permissions and could allow access to sensitive data.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Back up files and directories\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeBackupPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205752","ruleId":"SV-205752r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Create a pagefile user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Create a pagefile\" user right can change the size of a pagefile, which could affect system performance.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Create a pagefile\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeCreatePagefilePrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205753","ruleId":"SV-205753r958726_rule","severity":"high","ruleTitle":"Windows Server 2019 Create a token object user right must not be assigned to any groups or accounts.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups are granted the \"Create a token object\" user right, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs are granted the \"SeCreateTokenPrivilege\" user right, this is a finding.\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).\n\nPasswords for application accounts with this user right must be protected as highly privileged accounts.","fixText":"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).","ccis":["CCI-002235"]},{"vulnId":"V-205754","ruleId":"SV-205754r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Create global objects user right must only be assigned to Administrators, Service, Local Service, and Network Service.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Create global objects\" user right can create objects that are available to all sessions, which could affect processes in other users' sessions.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Create global objects\" user right, this is a finding:\n\n- Administrators\n- Service\n- Local Service\n- Network Service\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeCreateGlobalPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\nS-1-5-6 (Service)\nS-1-5-19 (Local Service)\nS-1-5-20 (Network Service)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators\n- Service\n- Local Service\n- Network Service","ccis":["CCI-002235"]},{"vulnId":"V-205755","ruleId":"SV-205755r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Create permanent shared objects user right must not be assigned to any groups or accounts.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Create permanent shared objects\" user right could expose sensitive data by creating shared objects.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups are granted the \"Create permanent shared objects\" user right, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs are granted the \"SeCreatePermanentPrivilege\" user right, this is a finding.","fixText":"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).","ccis":["CCI-002235"]},{"vulnId":"V-205756","ruleId":"SV-205756r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Create symbolic links user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Create symbolic links\" user right can create pointers to other objects, which could expose the system to attack.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Create symbolic links\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeCreateSymbolicLinkPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\n\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.","fixText":"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:\n\n- Administrators\n\nSystems 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\".","ccis":["CCI-002235"]},{"vulnId":"V-205757","ruleId":"SV-205757r958726_rule","severity":"high","ruleTitle":"Windows Server 2019 Debug programs: user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts 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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Debug programs\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeDebugPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).\n\nPasswords for application accounts with this user right must be protected as highly privileged accounts.","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205758","ruleId":"SV-205758r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Force shutdown from a remote system user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Force shutdown from a remote system\" user right can remotely shut down a system, which could result in a denial of service.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Force shutdown from a remote system\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeRemoteShutdownPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205759","ruleId":"SV-205759r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Generate security audits user right must only be assigned to Local Service and Network Service.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Generate security audits\" user right, this is a finding:\n\n- Local Service\n- Network Service\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeAuditPrivilege\" user right, this is a finding:\n\nS-1-5-19 (Local Service)\nS-1-5-20 (Network Service)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Local Service\n- Network Service","ccis":["CCI-002235"]},{"vulnId":"V-205760","ruleId":"SV-205760r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Impersonate a client after authentication user right must only be assigned to Administrators, Service, Local Service, and Network Service.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Impersonate a client after authentication\" user right, this is a finding:\n\n- Administrators\n- Service\n- Local Service\n- Network Service\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeImpersonatePrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\nS-1-5-6 (Service)\nS-1-5-19 (Local Service)\nS-1-5-20 (Network Service)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators\n- Service\n- Local Service\n- Network Service","ccis":["CCI-002235"]},{"vulnId":"V-205761","ruleId":"SV-205761r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Increase scheduling priority: user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Increase scheduling priority\" user right can change a scheduling priority, causing performance issues or a denial of service.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Increase scheduling priority\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeIncreaseBasePriorityPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205762","ruleId":"SV-205762r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Load and unload device drivers user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Load and unload device drivers\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeLoadDriverPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205763","ruleId":"SV-205763r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Lock pages in memory user right must not be assigned to any groups or accounts.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Lock pages in memory\" user right allows physical memory to be assigned to processes, which could cause performance issues or a denial of service.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups are granted the \"Lock pages in memory\" user right, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs are granted the \"SeLockMemoryPrivilege\" user right, this is a finding.\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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).","ccis":["CCI-002235"]},{"vulnId":"V-205764","ruleId":"SV-205764r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Modify firmware environment values user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts 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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Modify firmware environment values\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeSystemEnvironmentPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205765","ruleId":"SV-205765r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Perform volume maintenance tasks user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts 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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Perform volume maintenance tasks\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeManageVolumePrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205766","ruleId":"SV-205766r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Profile single process user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Profile single process\" user right can monitor non-system processes performance. An attacker could use this to identify processes to attack.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Profile single process\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeProfileSingleProcessPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205767","ruleId":"SV-205767r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Restore files and directories user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts 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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Restore files and directories\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeRestorePrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205768","ruleId":"SV-205768r958726_rule","severity":"medium","ruleTitle":"Windows Server 2019 Take ownership of files or other objects user right must only be assigned to the Administrators group.","description":"Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Take ownership of files or other objects\" user right can take ownership of objects and make changes.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nIf any accounts or groups other than the following are granted the \"Take ownership of files or other objects\" user right, this is a finding:\n\n- Administrators\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas User_Rights /cfg c:\\path\\filename.txt\n\nReview the text file.\n\nIf any SIDs other than the following are granted the \"SeTakeOwnershipPrivilege\" user right, this is a finding:\n\nS-1-5-32-544 (Administrators)\n\nIf an application requires this user right, this would not be a finding.\n\nVendor documentation must support the requirement for having the user right.\n\nThe requirement must be documented with the ISSO.\n\nThe application account must meet requirements for application account passwords, such as length (WN19-00-000050) and required frequency of changes (WN19-00-000060).","fixText":"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:\n\n- Administrators","ccis":["CCI-002235"]},{"vulnId":"V-205769","ruleId":"SV-205769r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Account Management - Other Account Management Events successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nOther Account Management Events records events such as the access of a password hash or the Password Policy Checking API being called.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding:\n\nAccount Management >> Other Account Management Events - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205770","ruleId":"SV-205770r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Detailed Tracking - Process Creation successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nProcess Creation records events related to the creation of a process and the source.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nDetailed Tracking >> Process Creation - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205771","ruleId":"SV-205771r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Policy Change - Audit Policy Change successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Policy Change records events related to changes in audit policy.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nPolicy Change >> Audit Policy Change - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205772","ruleId":"SV-205772r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Policy Change - Audit Policy Change failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Policy Change records events related to changes in audit policy.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nPolicy Change >> Audit Policy Change - Failure","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205773","ruleId":"SV-205773r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Policy Change - Authentication Policy Change successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAuthentication Policy Change records events related to changes in authentication policy, including Kerberos policy and Trust changes.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nPolicy Change >> Authentication Policy Change - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205774","ruleId":"SV-205774r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Policy Change - Authorization Policy Change successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAuthorization Policy Change records events related to changes in user rights, such as \"Create a token object\".\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nPolicy Change >> Authorization Policy Change - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205775","ruleId":"SV-205775r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Privilege Use - Sensitive Privilege Use successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSensitive Privilege Use records events related to use of sensitive privileges, such as \"Act as part of the operating system\" or \"Debug programs\".\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nPrivilege Use >> Sensitive Privilege Use - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205776","ruleId":"SV-205776r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Privilege Use - Sensitive Privilege Use failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSensitive Privilege Use records events related to use of sensitive privileges, such as \"Act as part of the operating system\" or \"Debug programs\".\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nPrivilege Use >> Sensitive Privilege Use - Failure","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205777","ruleId":"SV-205777r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit System - IPsec Driver successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nIPsec Driver records events related to the IPsec Driver, such as dropped packets.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nSystem >> IPsec Driver - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205778","ruleId":"SV-205778r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit System - IPsec Driver failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nIPsec Driver records events related to the IPsec Driver, such as dropped packets.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nSystem >> IPsec Driver - Failure","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205779","ruleId":"SV-205779r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit System - Other System Events successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Other System Events records information related to cryptographic key operations and the Windows Firewall service.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nSystem >> Other System Events - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205780","ruleId":"SV-205780r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit System - Other System Events failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Other System Events records information related to cryptographic key operations and the Windows Firewall service.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nSystem >> Other System Events - Failure","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205781","ruleId":"SV-205781r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit System - Security State Change successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSecurity State Change records events related to changes in the security state, such as startup and shutdown of the system.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nSystem >> Security State Change - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205782","ruleId":"SV-205782r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit System - Security System Extension successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSecurity System Extension records events related to extension code being loaded by the security subsystem.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nSystem >> Security System Extension - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205783","ruleId":"SV-205783r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit System - System Integrity successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSystem Integrity records events related to violations of integrity to the security subsystem.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nSystem >> System Integrity - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205784","ruleId":"SV-205784r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit System - System Integrity failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSystem Integrity records events related to violations of integrity to the security subsystem.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nSystem >> System Integrity - Failure","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205785","ruleId":"SV-205785r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 Active Directory Group Policy objects must be configured with proper audit settings.","description":"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. \n\nFor 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.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the auditing configuration for all Group Policy objects.\n\nOpen \"Group Policy Management\" (available from various menus or run \"gpmc.msc\").\n\nNavigate to \"Group Policy Objects\" in the domain being reviewed (Forest >> Domains >> Domain).\n\nFor each Group Policy object:\n\nSelect the Group Policy object item in the left pane.\n\nSelect the \"Delegation\" tab in the right pane.\n\nSelect the \"Advanced\" button.\n\nSelect the \"Advanced\" button again and then the \"Auditing\" tab.\n\nIf the audit settings for any Group Policy object are not at least as inclusive as those below, this is a finding:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nApplies to - This object and all descendant objects or Descendant groupPolicyContainer objects\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special (Permissions: Write all properties, Modify permissions; Properties: all \"Write\" type selected)\nInherited from - Parent Object\nApplies to - Descendant groupPolicyContainer objects\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions)\nInherited from - Parent Object\nApplies to - Descendant Organization Unit Objects","fixText":"Configure the audit settings for Group Policy objects to include the following:\n\nThis can be done at the Policy level in Active Directory to apply to all group policies.\n\nOpen \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nSelect \"Advanced Features\" from the \"View\" Menu.\n\nNavigate to [Domain] >> System >> Policies in the left panel.\n\nRight click \"Policies\", select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button.\n\nSelect the \"Auditing\" tab.\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nApplies to - This object and all descendant objects or Descendant groupPolicyContainer objects\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special (Permissions: Write all properties, Modify permissions; Properties: all \"Write\" type selected)\nInherited from - Parent Object\nApplies to - Descendant groupPolicyContainer objects\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions)\nInherited from - Parent Object\nApplies to - Descendant Organization Unit Objects","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205786","ruleId":"SV-205786r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 Active Directory Domain object must be configured with proper audit settings.","description":"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. \n\nFor 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.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the auditing configuration for the Domain object.\n\nOpen \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect the domain being reviewed in the left pane.\n\nRight-click the domain name and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nIf the audit settings on the Domain object are not at least as inclusive as those below, this is a finding:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\nApplies to - This object only\n\nThe 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.\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - None\nApplies to - Special\n\nType - Success\nPrincipal - Domain Users\nAccess - All extended rights\nInherited from - None\nApplies to - This object only\n\nType - Success\nPrincipal - Administrators\nAccess - All extended rights\nInherited from - None\nApplies to - This object only\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\nApplies to - This object only\n(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner)","fixText":"Open \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect the domain being reviewed in the left pane.\n\nRight-click the domain name and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nConfigure the audit settings for Domain object to include the following:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\nApplies to - This object only\n\nThe 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.\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - None\nApplies to - Special\n\nType - Success\nPrincipal - Domain Users\nAccess - All extended rights\nInherited from - None\nApplies to - This object only\n\nType - Success\nPrincipal - Administrators\nAccess - All extended rights\nInherited from - None\nApplies to - This object only\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\nApplies to - This object only\n(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner.)","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205787","ruleId":"SV-205787r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 Active Directory Infrastructure object must be configured with proper audit settings.","description":"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. \n\nFor 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.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the auditing configuration for Infrastructure object.\n\nOpen \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect the domain being reviewed in the left pane.\n\nRight-click the \"Infrastructure\" object in the right pane and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nIf the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\n(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master)\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - (CN of domain)","fixText":"Open \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect the domain being reviewed in the left pane.\n\nRight-click the \"Infrastructure\" object in the right pane and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nConfigure the audit settings for Infrastructure object to include the following:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\n(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master)\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - (CN of domain)","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205788","ruleId":"SV-205788r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 Active Directory Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings.","description":"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. \n\nFor 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.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the auditing configuration for the Domain Controller OU object.\n\nOpen \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect the \"Domain Controllers OU\" under the domain being reviewed in the left pane.\n\nRight-click the \"Domain Controllers OU\" object and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nIf the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\nApplies to - This object and all descendant objects\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\nApplies to - This object only\n(Access - Special = Permissions: all create, delete and modify permissions)\n\nType - Success\nPrincipal - Everyone\nAccess - Write all properties\nInherited from - None\nApplies to - This object and all descendant objects\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - (CN of domain)\nApplies to - Descendant Organizational Unit objects","fixText":"Open \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect the \"Domain Controllers OU\" under the domain being reviewed in the left pane.\n\nRight-click the \"Domain Controllers OU\" object and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nConfigure the audit settings for Domain Controllers OU object to include the following:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\nApplies to - This object only\n(Access - Special = Permissions: all create, delete and modify permissions)\n\nType - Success\nPrincipal - Everyone\nAccess - Write all properties\nInherited from - None\nApplies to - This object and all descendant objects\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - (CN of domain)\nApplies to - Descendant Organizational Unit objects","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205789","ruleId":"SV-205789r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 Active Directory AdminSDHolder object must be configured with proper audit settings.","description":"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. \n\nFor 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.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the auditing configuration for the \"AdminSDHolder\" object.\n\nOpen \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect \"System\" under the domain being reviewed in the left pane.\n\nRight-click the \"AdminSDHolder\" object in the right pane and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nIf the audit settings on the \"AdminSDHolder\" object are not at least as inclusive as those below, this is a finding:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\nApplies to - This object only\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\nApplies to - This object only\n(Access - Special = Write all properties, Modify permissions, Modify owner)\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - (CN of domain)\nApplies to - Descendant Organizational Unit objects","fixText":"Open \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect \"System\" under the domain being reviewed in the left pane.\n\nRight-click the \"AdminSDHolder\" object in the right pane and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nConfigure the audit settings for AdminSDHolder object to include the following:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\nApplies to - This object only\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\nApplies to - This object only\n(Access - Special = Write all properties, Modify permissions, Modify owner)\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - (CN of domain)\nApplies to - Descendant Organizational Unit objects","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205790","ruleId":"SV-205790r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 Active Directory RID Manager$ object must be configured with proper audit settings.","description":"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. \n\nFor 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.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the auditing configuration for the \"RID Manager$\" object.\n\nOpen \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect \"System\" under the domain being reviewed in the left pane.\n\nRight-click the \"RID Manager$\" object in the right pane and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nIf the audit settings on the \"RID Manager$\" object are not at least as inclusive as those below, this is a finding:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\n (Access - Special = Write all properties, All extended rights, Change RID master)\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - (CN of domain)","fixText":"Open \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nEnsure \"Advanced Features\" is selected in the \"View\" menu.\n\nSelect \"System\" under the domain being reviewed in the left pane.\n\nRight-click the \"RID Manager$\" object in the right pane and select \"Properties\".\n\nSelect the \"Security\" tab.\n\nSelect the \"Advanced\" button and then the \"Auditing\" tab.\n\nConfigure the audit settings for RID Manager$ object to include the following:\n\nType - Fail\nPrincipal - Everyone\nAccess - Full Control\nInherited from - None\n\nThe 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.\n\nType - Success\nPrincipal - Everyone\nAccess - Special\nInherited from - None\n (Access - Special = Write all properties, All extended rights, Change RID master)\n\nTwo instances with the following summary information will be listed:\n\nType - Success\nPrincipal - Everyone\nAccess - (blank)\nInherited from - (CN of domain)","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205791","ruleId":"SV-205791r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit DS Access - Directory Service Access successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Directory Service Access records events related to users accessing an Active Directory object.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nSecurity Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nDS Access >> Directory Service Access - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205792","ruleId":"SV-205792r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit DS Access - Directory Service Access failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Directory Service Access records events related to users accessing an Active Directory object.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nSecurity Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nDS Access >> Directory Service Access - Failure","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205793","ruleId":"SV-205793r958732_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit DS Access - Directory Service Changes successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Directory Service Changes records events related to changes made to objects in Active Directory Domain Services.\n\nSatisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nSecurity Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nDS Access >> Directory Service Changes - Success","fixText":"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.","ccis":["CCI-000172","CCI-002234"]},{"vulnId":"V-205795","ruleId":"SV-205795r958736_rule","severity":"medium","ruleTitle":"Windows Server 2019 account lockout duration must be configured to 15 minutes or greater.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy.\n\nIf the \"Account lockout duration\" is less than \"15\" minutes (excluding \"0\"), this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"LockoutDuration\" is less than \"15\" (excluding \"0\") in the file, this is a finding.\n\nConfiguring this to \"0\", requiring an administrator to unlock the account, is more restrictive and is not a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy >> \"Account lockout duration\" to \"15\" minutes or greater.\n\nA value of \"0\" is also acceptable, requiring an administrator to unlock the account.","ccis":["CCI-002238"]},{"vulnId":"V-205796","ruleId":"SV-205796r958752_rule","severity":"medium","ruleTitle":"Windows Server 2019 Application event log size must be configured to 32768 KB or greater.","description":"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.","checkContent":"If the system is configured to write events directly to an audit server, this is NA.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\EventLog\\Application\\\n\nValue Name: MaxSize\n\nType: REG_DWORD\nValue: 0x00008000 (32768) (or greater)","fixText":"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.","ccis":["CCI-001849"]},{"vulnId":"V-205797","ruleId":"SV-205797r1186384_rule","severity":"medium","ruleTitle":"Windows Server 2019 security event log size must be configured to a value that holds at least one week's worth of audit records.","description":"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. System administrators (SAs) must monitor the volume of security event audit records and increase the registry value for the log size as needed.","checkContent":"If the system is configured to write events directly to an audit server, this is not applicable.\n\nThe registry configuration setting below must be set (at least) to a value equal to the size needed to contain one week's worth of audit records in the security event log. The value used below is an example that assumes a typical week’s log size of 5GB.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nNote: The following registry entry is an example; the value must equal at least one week's worth of records.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\EventLog\\Security\\\n\nValue Name: MaxSize\n\nType: REG_DWORD\nValue:0x49960800 (5120000) (or greater)","fixText":"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 a value that will contain one week of audit records or greater.","ccis":["CCI-001849"]},{"vulnId":"V-205798","ruleId":"SV-205798r958752_rule","severity":"medium","ruleTitle":"Windows Server 2019 System event log size must be configured to 32768 KB or greater.","description":"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.","checkContent":"If the system is configured to write events directly to an audit server, this is NA.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\EventLog\\System\\\n\nValue Name: MaxSize\n\nType: REG_DWORD\nValue: 0x00008000 (32768) (or greater)","fixText":"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.","ccis":["CCI-001849"]},{"vulnId":"V-205799","ruleId":"SV-205799r958754_rule","severity":"medium","ruleTitle":"Windows Server 2019 audit records must be backed up to a different system or media than the system being audited.","description":"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.","checkContent":"Determine if a process to back up log data to a different system or media than the system being audited has been implemented.\n\nIf it has not, this is a finding.","fixText":"Establish and implement a process for backing up log data to another system or media other than the system being audited.","ccis":["CCI-001851"]},{"vulnId":"V-205800","ruleId":"SV-205800r1051077_rule","severity":"low","ruleTitle":"The Windows Server 2019 time service must synchronize with an appropriate DOD time source.","description":"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.","checkContent":"Review the Windows time service configuration.\n\nOpen an elevated \"Command Prompt\" (run as administrator).\n\nEnter \"W32tm /query /configuration\".\n\nDomain-joined systems (excluding the domain controller with the PDC emulator role):\n\nIf the value for \"Type\" under \"NTP Client\" is not \"NT5DS\", this is a finding.\n\nOther systems:\n\nIf systems are configured with a \"Type\" of \"NTP\", including standalone or nondomain-joined 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.\n\nTo determine the domain controller with the PDC Emulator role:\n\nOpen \"PowerShell\".\n\nEnter \"Get-ADDomain | FT PDCEmulator\".","fixText":"Configure the system to synchronize time with an appropriate DOD time source.\n\nDomain-joined systems use NT5DS to synchronize time from other systems in the domain by default.\n\nIf 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.\n\nThe US Naval Observatory operates stratum 1 time servers, which are identified at:\nhttps://www.cnmoc.usff.navy.mil/Our-Commands/United-States-Naval-Observatory/Precise-Time-Department/Network-Time-Protocol-NTP/\n\nTime 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.","ccis":["CCI-004923","CCI-001891"]},{"vulnId":"V-205801","ruleId":"SV-205801r1051078_rule","severity":"medium","ruleTitle":"Windows Server 2019 must prevent users from changing installation options.","description":"Installation options for applications are typically controlled by administrators. This setting prevents users from changing installation options that may bypass security features.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\Installer\\\n\nValue Name: EnableUserControl\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> \"Allow user control over installs\" to \"Disabled\".","ccis":["CCI-003980","CCI-001812"]},{"vulnId":"V-205802","ruleId":"SV-205802r1051079_rule","severity":"high","ruleTitle":"Windows Server 2019 must disable the Windows Installer Always install with elevated privileges option.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\Installer\\\n\nValue Name: AlwaysInstallElevated\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Installer >> \"Always install with elevated privileges\" to \"Disabled\".","ccis":["CCI-003980","CCI-001812"]},{"vulnId":"V-205803","ruleId":"SV-205803r958794_rule","severity":"medium","ruleTitle":"Windows Server 2019 system files must be monitored for unauthorized changes.","description":"Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code on a system.","checkContent":"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.\n\nIf system files are not monitored for unauthorized changes, this is a finding.\n\nAn approved and properly configured solution will contain both a list of baselines that includes all system file locations and a file comparison task that is scheduled to run at least weekly.","fixText":"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.","ccis":["CCI-001744"]},{"vulnId":"V-205804","ruleId":"SV-205804r958804_rule","severity":"high","ruleTitle":"Windows Server 2019 Autoplay must be turned off for non-volume devices.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\Explorer\\\n\nValue Name: NoAutoplayfornonVolume\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> \"Disallow Autoplay for non-volume devices\" to \"Enabled\".","ccis":["CCI-001764"]},{"vulnId":"V-205805","ruleId":"SV-205805r958804_rule","severity":"high","ruleTitle":"Windows Server 2019 default AutoRun behavior must be configured to prevent AutoRun commands.","description":"Allowing AutoRun commands to execute may introduce malicious code to a system. Configuring this setting prevents AutoRun commands from executing.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\\n\nValue Name: NoAutorun\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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.","ccis":["CCI-001764"]},{"vulnId":"V-205806","ruleId":"SV-205806r958804_rule","severity":"high","ruleTitle":"Windows Server 2019 AutoPlay must be disabled for all drives.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path:  \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\policies\\Explorer\\\n\nValue Name: NoDriveTypeAutoRun\n\nType: REG_DWORD\nValue: 0x000000ff (255)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> AutoPlay Policies >> \"Turn off AutoPlay\" to \"Enabled\" with \"All Drives\" selected.","ccis":["CCI-001764"]},{"vulnId":"V-205807","ruleId":"SV-205807r958808_rule","severity":"medium","ruleTitle":"Windows Server 2019 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.","description":"Using an allowlist 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.\n\nThe 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 allowlisting.","checkContent":"Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs.\n\nIf an application allowlisting program is not in use on the system, this is a finding.\n\nConfiguration of allowlisting applications will vary by the program.\n\nAppLocker is an allowlisting 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.\n\nIf AppLocker is used, perform the following to view the configuration of AppLocker:\n\nOpen \"PowerShell\".\n\nIf the AppLocker PowerShell module has not been imported previously, execute the following first:\n\nImport-Module AppLocker\n\nExecute the following command, substituting [c:\\temp\\file.xml] with a location and file name appropriate for the system:\n\nGet-AppLockerPolicy -Effective -XML > c:\\temp\\file.xml\n\nThis 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.\n\nImplementation guidance for AppLocker is available at the following link:\n\nhttps://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-policies-deployment-guide","fixText":"Configure an application allowlisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.\n\nConfiguration of allowlisting applications will vary by the program. AppLocker is an allowlisting application built into Windows Server.\n\nIf AppLocker is used, it is configured through group policy in Computer Configuration >> Windows Settings >> Security Settings >> Application Control Policies >> AppLocker.\n\nImplementation guidance for AppLocker is available at the following link:\n\nhttps://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-policies-deployment-guide","ccis":["CCI-001774"]},{"vulnId":"V-205808","ruleId":"SV-205808r1051080_rule","severity":"medium","ruleTitle":"Windows Server 2019 must not save passwords in the Remote Desktop Client.","description":"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.\n\nSatisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows NT\\Terminal Services\\\n\nValue Name: DisablePasswordSaving\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002038"]},{"vulnId":"V-205809","ruleId":"SV-205809r1051081_rule","severity":"medium","ruleTitle":"Windows Server 2019 Remote Desktop Services must always prompt a client for passwords upon connection.","description":"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.\n\nSatisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows NT\\Terminal Services\\\n\nValue Name: fPromptForPassword\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002038"]},{"vulnId":"V-205810","ruleId":"SV-205810r1051082_rule","severity":"medium","ruleTitle":"Windows Server 2019 Windows Remote Management (WinRM) service must not store RunAs credentials.","description":"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.\n\nSatisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\WinRM\\Service\\\n\nValue Name: DisableRunAs\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002038"]},{"vulnId":"V-205811","ruleId":"SV-205811r1051083_rule","severity":"medium","ruleTitle":"Windows Server 2019 User Account Control approval mode for the built-in Administrator must be enabled.","description":"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.\n\nSatisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156","checkContent":"UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience).\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: FilterAdministratorToken\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002038"]},{"vulnId":"V-205812","ruleId":"SV-205812r1051084_rule","severity":"medium","ruleTitle":"Windows Server 2019 User Account Control must automatically deny standard user requests for elevation.","description":"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.\n\nSatisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156","checkContent":"UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience).\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: ConsentPromptBehaviorUser\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0)","fixText":"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\".","ccis":["CCI-002038"]},{"vulnId":"V-205813","ruleId":"SV-205813r1051085_rule","severity":"medium","ruleTitle":"Windows Server 2019 User Account Control must run all administrators in Admin Approval Mode, enabling UAC.","description":"User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC.\n\nSatisfies: SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00156","checkContent":"UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2019 versus Server with Desktop Experience).\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: EnableLUA\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002038"]},{"vulnId":"V-205814","ruleId":"SV-205814r971545_rule","severity":"medium","ruleTitle":"Windows Server 2019 must restrict unauthenticated Remote Procedure Call (RPC) clients from connecting to the RPC server on domain-joined member servers and standalone or nondomain-joined systems.","description":"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.","checkContent":"This applies to member servers and standalone or nondomain-joined systems. It is NA for domain controllers.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive:  HKEY_LOCAL_MACHINE\nRegistry Path:  \\SOFTWARE\\Policies\\Microsoft\\Windows NT\\Rpc\\\n\nValue Name:  RestrictRemoteClients\n\nType:  REG_DWORD\nValue:  0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Remote Procedure Call >> \"Restrict Unauthenticated RPC clients\" to \"Enabled\" with \"Authenticated\" selected.","ccis":["CCI-001967"]},{"vulnId":"V-205815","ruleId":"SV-205815r971545_rule","severity":"medium","ruleTitle":"Windows Server 2019 computer account password must not be prevented from being reset.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\Parameters\\\n\nValue Name: DisablePasswordChange\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> \"Domain member: Disable machine account password changes\" to \"Disabled\".","ccis":["CCI-001967"]},{"vulnId":"V-205816","ruleId":"SV-205816r958848_rule","severity":"medium","ruleTitle":"Windows Server 2019 Windows Remote Management (WinRM) client must not allow unencrypted traffic.","description":"Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.\n\nSatisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\WinRM\\Client\\\n\nValue Name: AllowUnencryptedTraffic\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Client >> \"Allow unencrypted traffic\" to \"Disabled\".","ccis":["CCI-002890","CCI-003123"]},{"vulnId":"V-205817","ruleId":"SV-205817r958848_rule","severity":"medium","ruleTitle":"Windows Server 2019 Windows Remote Management (WinRM) service must not allow unencrypted traffic.","description":"Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.\n\nSatisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\WinRM\\Service\\\n\nValue Name: AllowUnencryptedTraffic\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows Remote Management (WinRM) >> WinRM Service >> \"Allow unencrypted traffic\" to \"Disabled\".","ccis":["CCI-002890","CCI-003123"]},{"vulnId":"V-205818","ruleId":"SV-205818r987791_rule","severity":"medium","ruleTitle":"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.","description":"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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nReview the organization network diagram(s) or documentation to determine the level of classification for the network(s) over which replication data is transmitted.\n\nDetermine the classification level of the Windows domain controller.\n\nIf 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.\n\nIf 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.","fixText":"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.","ccis":["CCI-002450"]},{"vulnId":"V-205819","ruleId":"SV-205819r958902_rule","severity":"low","ruleTitle":"Windows Server 2019 must be configured to ignore NetBIOS name release requests except from WINS servers.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive:  HKEY_LOCAL_MACHINE\nRegistry Path:  \\SYSTEM\\CurrentControlSet\\Services\\Netbt\\Parameters\\\n\nValue Name:  NoNameReleaseOnDemand\n\nValue Type:  REG_DWORD\nValue:  0x00000001 (1)","fixText":"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\".\n\nThis 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.","ccis":["CCI-002385"]},{"vulnId":"V-205820","ruleId":"SV-205820r958908_rule","severity":"medium","ruleTitle":"Windows Server 2019 domain controllers must require LDAP access signing.","description":"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.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\NTDS\\Parameters\\\n\nValue Name: LDAPServerIntegrity\n\nValue Type: REG_DWORD\nValue: 0x00000002 (2)","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> \"Domain controller: LDAP server signing requirements\" to \"Require signing\".","ccis":["CCI-002418","CCI-002421"]},{"vulnId":"V-205821","ruleId":"SV-205821r958908_rule","severity":"medium","ruleTitle":"Windows Server 2019 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled.","description":"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.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\Parameters\\\n\nValue Name: RequireSignOrSeal\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002418","CCI-002421"]},{"vulnId":"V-205822","ruleId":"SV-205822r958908_rule","severity":"medium","ruleTitle":"Windows Server 2019 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to enabled.","description":"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.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\Parameters\\\n\nValue Name: SealSecureChannel\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002418","CCI-002421"]},{"vulnId":"V-205823","ruleId":"SV-205823r958908_rule","severity":"medium","ruleTitle":"Windows Server 2019 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled.","description":"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.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\Parameters\\\n\nValue Name: SignSecureChannel\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002418","CCI-002421"]},{"vulnId":"V-205824","ruleId":"SV-205824r958908_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to require a strong session key.","description":"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.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\Parameters\\\n\nValue Name: RequireStrongKey\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)\n \nThis setting may prevent a system from being joined to a domain if not configured consistently between systems.","fixText":"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\".","ccis":["CCI-002418","CCI-002421"]},{"vulnId":"V-205825","ruleId":"SV-205825r958908_rule","severity":"medium","ruleTitle":"Windows Server 2019 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled.","description":"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.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters\\\n\nValue Name: RequireSecuritySignature\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> \"Microsoft network client: Digitally sign communications (always)\" to \"Enabled\".","ccis":["CCI-002418","CCI-002421"]},{"vulnId":"V-205826","ruleId":"SV-205826r958908_rule","severity":"medium","ruleTitle":"Windows Server 2019 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled.","description":"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.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\LanmanWorkstation\\Parameters\\\n\nValue Name: EnableSecuritySignature\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002418","CCI-002421"]},{"vulnId":"V-205827","ruleId":"SV-205827r958908_rule","severity":"medium","ruleTitle":"Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.","description":"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.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\LanManServer\\Parameters\\\n\nValue Name: RequireSecuritySignature\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> \"Microsoft network server: Digitally sign communications (always)\" to \"Enabled\".","ccis":["CCI-002418","CCI-002421"]},{"vulnId":"V-205828","ruleId":"SV-205828r958908_rule","severity":"medium","ruleTitle":"Windows Server 2019 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled.","description":"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.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\LanManServer\\Parameters\\\n\nValue Name: EnableSecuritySignature\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-002418","CCI-002421"]},{"vulnId":"V-205829","ruleId":"SV-205829r958912_rule","severity":"medium","ruleTitle":"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.","description":"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.\n\nEnsuring 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.\n\nUse 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.\n\nSatisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190","checkContent":"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.\n\nIf protection methods have not been implemented, this is a finding.","fixText":"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.","ccis":["CCI-002420","CCI-002422"]},{"vulnId":"V-205830","ruleId":"SV-205830r958928_rule","severity":"medium","ruleTitle":"Windows Server 2019 Explorer Data Execution Prevention must be enabled.","description":"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.","checkContent":"The default behavior is for Data Execution Prevention to be turned on for File Explorer.\n\nIf the registry value name below does not exist, this is not a finding.\n\nIf it exists and is configured with a value of \"0\", this is not a finding.\n\nIf it exists and is configured with a value of \"1\", this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\Explorer\\\n\nValue Name: NoDataExecutionPrevention\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0) (or if the Value Name does not exist)","fixText":"The default behavior is for data execution prevention to be turned on for File Explorer.\n\nIf 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\".","ccis":["CCI-002824"]},{"vulnId":"V-205832","ruleId":"SV-205832r991578_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Account Logon - Credential Validation successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nCredential Validation records events related to validation tests on credentials for a user account logon.","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nAccount Logon >> Credential Validation - Success","fixText":"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.","ccis":["CCI-000172"]},{"vulnId":"V-205833","ruleId":"SV-205833r991578_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Account Logon - Credential Validation failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nCredential Validation records events related to validation tests on credentials for a user account logon.","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nAccount Logon >> Credential Validation - Failure","fixText":"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.","ccis":["CCI-000172"]},{"vulnId":"V-205834","ruleId":"SV-205834r991578_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Logon/Logoff - Group Membership successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Group Membership records information related to the group membership of a user's logon token.","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nLogon/Logoff >> Group Membership - Success","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> \"Audit Group Membership\" with \"Success\" selected.","ccis":["CCI-000172"]},{"vulnId":"V-205835","ruleId":"SV-205835r991578_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Logon/Logoff - Special Logon successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSpecial Logon records special logons that have administrative privileges and can be used to elevate processes.\n\nSatisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nLogon/Logoff >> Special Logon - Success","fixText":"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.","ccis":["CCI-000172"]},{"vulnId":"V-205836","ruleId":"SV-205836r991578_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Object Access - Other Object Access Events successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAuditing for other object access records events related to the management of task scheduler jobs and COM+ objects.","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective.\n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nObject Access >> Other Object Access Events - Success","fixText":"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.","ccis":["CCI-000172"]},{"vulnId":"V-205837","ruleId":"SV-205837r991578_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Object Access - Other Object Access Events failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAuditing for other object access records events related to the management of task scheduler jobs and COM+ objects.","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective.\n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nObject Access >> Other Object Access Events - Failure","fixText":"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.","ccis":["CCI-000172"]},{"vulnId":"V-205838","ruleId":"SV-205838r991581_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit logoff successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nLogoff 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.\n\nSatisfies: SRG-OS-000472-GPOS-00217, SRG-OS-000480-GPOS-00227","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nLogon/Logoff >> Logoff - Success","fixText":"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.","ccis":["CCI-000172","CCI-000366"]},{"vulnId":"V-205839","ruleId":"SV-205839r991583_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Detailed Tracking - Plug and Play Events successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nPlug and Play activity records events related to the successful connection of external devices.","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nDetailed Tracking >> Plug and Play Events - Success","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Detailed Tracking >> \"Audit PNP Activity\" with \"Success\" selected.","ccis":["CCI-000172"]},{"vulnId":"V-205840","ruleId":"SV-205840r991583_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Object Access - Removable Storage successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nRemovable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nObject Access >> Removable Storage - Success\n\nVirtual 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.","fixText":"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.","ccis":["CCI-000172"]},{"vulnId":"V-205841","ruleId":"SV-205841r991583_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit Object Access - Removable Storage failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nRemovable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.","checkContent":"Security Option \"Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings\" must be set to \"Enabled\" (WN19-SO-000050) for the detailed auditing subcategories to be effective. \n\nUse the \"AuditPol\" tool to review the current Audit Policy configuration:\n\nOpen \"PowerShell\" or a \"Command Prompt\" with elevated privileges (\"Run as administrator\").\n\nEnter \"AuditPol /get /category:*\"\n\nCompare the \"AuditPol\" settings with the following:\n\nIf the system does not audit the following, this is a finding.\n\nObject Access >> Removable Storage - Failure\n\nVirtual 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.","fixText":"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.","ccis":["CCI-000172"]},{"vulnId":"V-205842","ruleId":"SV-205842r1137699_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.","description":"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.","checkContent":"This is NA if the host is running SharePoint.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\FIPSAlgorithmPolicy\\\n\nValue Name: Enabled\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)\n \nClients 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.\n\nIf the server is hosting SharePoint, this is not applicable.","fixText":"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\".","ccis":["CCI-002450"]},{"vulnId":"V-205843","ruleId":"SV-205843r959008_rule","severity":"medium","ruleTitle":"Windows Server 2019 must, at a minimum, offload audit records of interconnected systems in real time and offload standalone or nondomain-joined systems weekly.","description":"Protection of log data includes ensuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.","checkContent":"Verify the audit records, at a minimum, are offloaded for interconnected systems in real time and offloaded for standalone or nondomain-joined systems weekly. \n\nIf they are not, this is a finding.","fixText":"Configure the system to, at a minimum, offload audit records of interconnected systems in real time and offload standalone or nondomain-joined systems weekly.","ccis":["CCI-001851"]},{"vulnId":"V-205844","ruleId":"SV-205844r991589_rule","severity":"high","ruleTitle":"Windows Server 2019 users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks.","description":"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.","checkContent":"Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account. \n\nIf users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding.","fixText":"Ensure each user with administrative privileges has a separate account for user duties and one for privileged duties.","ccis":["CCI-000366"]},{"vulnId":"V-205845","ruleId":"SV-205845r991589_rule","severity":"high","ruleTitle":"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.","description":"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.\n\nSince 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.\n\nThe 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.\n\nWhitelisting can be used to enforce the policy to ensure compliance.","checkContent":"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.\n\nIf it does not, this is a finding.\n\nThe organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.","fixText":"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.\n\nThe organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.","ccis":["CCI-000366"]},{"vulnId":"V-205846","ruleId":"SV-205846r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 members of the Backup Operators group must have separate accounts for backup duties and normal operational tasks.","description":"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.","checkContent":"If no accounts are members of the Backup Operators group, this is NA.\n\nVerify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks.\n\nIf users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding.","fixText":"Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions.","ccis":["CCI-000366"]},{"vulnId":"V-205847","ruleId":"SV-205847r991589_rule","severity":"medium","ruleTitle":"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.","description":"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.","checkContent":"Determine if manually managed application/service accounts exist. If none exist, this is NA.\n\nIf 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.\n\nIdentify manually managed application/service accounts.\n\nTo determine the date a password was last changed:\n\nDomain controllers:\n\nOpen \"PowerShell\".\n\nEnter \"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.\n\nIf the \"PasswordLastSet\" date is more than one year old, this is a finding.\n\nMember servers and standalone or nondomain-joined systems:\n\nOpen \"Command Prompt\".\n\nEnter 'Net User [application account name] | Find /i \"Password Last Set\"', where [application account name] is the name of the manually managed application/service account.\n\nIf the \"Password Last Set\" date is more than one year old, this is a finding.","fixText":"Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization.\n\nIt is recommended that system-managed service accounts be used whenever possible.","ccis":["CCI-000366"]},{"vulnId":"V-205848","ruleId":"SV-205848r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use.","description":"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.","checkContent":"For standalone or nondomain-joined systems, this is NA.\n\nVerify the system has a TPM and it is ready for use.\n\nRun \"tpm.msc\".\n\nReview the sections in the center pane.\n\n\"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\".\n\nTPM Manufacturer Information - Specific Version = 2.0 or 1.2\n\nIf a TPM is not found or is not ready for use, this is a finding.","fixText":"Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.)\n\nThe TPM must be enabled in the firmware.\n\nRun \"tpm.msc\" for configuration options in Windows.","ccis":["CCI-000366"]},{"vulnId":"V-205849","ruleId":"SV-205849r991589_rule","severity":"high","ruleTitle":"Windows Server 2019 must be maintained at a supported servicing level.","description":"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.","checkContent":"Open \"Command Prompt\".\n\nEnter \"winver.exe\".\n\nIf the \"About Windows\" dialog box does not display \"Microsoft Windows Server Version 1809 (Build 17763.xxx)\" or greater, this is a finding.\n\nPreview versions must not be used in a production environment.","fixText":"Update the system to a Version 1809 (Build 17763.xxx) or greater.","ccis":["CCI-000366"]},{"vulnId":"V-205850","ruleId":"SV-205850r991589_rule","severity":"high","ruleTitle":"Windows Server 2019 must use an anti-virus program.","description":"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.","checkContent":"Verify an anti-virus solution is installed on the system. The anti-virus solution may be bundled with an approved host-based security solution.\n\nIf there is no anti-virus solution installed on the system, this is a finding.\n\nVerify if Windows Defender is in use or enabled:\n\nOpen \"PowerShell\".\n\nEnter “get-service | where {$_.DisplayName -Like \"*Defender*\"} | Select Status,DisplayName”\n\nVerify if third-party anti-virus is in use or enabled:\n\nOpen \"PowerShell\".\n\nEnter \"get-service | where {$_.DisplayName -Like \"*mcafee*\"} | Select Status,DisplayName”\n\nEnter \"get-service | where {$_.DisplayName -Like \"*symantec*\"} | Select Status,DisplayName”","fixText":"If no anti-virus software is in use, install Windows Defender or third-party anti-virus.\n\nOpen \"PowerShell\".\n\nEnter \"Install-WindowsFeature -Name Windows-Defender”.\n\nFor third-party anti-virus, install per anti-virus instructions and disable Windows Defender.\n\nOpen \"PowerShell\".\n\nEnter \"Uninstall-WindowsFeature -Name Windows-Defender”.","ccis":["CCI-000366"]},{"vulnId":"V-205851","ruleId":"SV-205851r1186378_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have a host-based intrusion detection and prevention service installed.","description":"A properly configured Host-based Intrusion Detection System (HIDS) and 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.","checkContent":"Determine if there is a HIDS and HIPS on each server. \n\nA 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 information system security officer (ISSO).\n\nIf a HIDS and HIPS are not installed on the system, this is a finding.","fixText":"Install a HIDS and HIPS on each server.","ccis":["CCI-000366"]},{"vulnId":"V-205852","ruleId":"SV-205852r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have software certificate installation files removed.","description":"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.","checkContent":"Search all drives for *.p12 and *.pfx files.\n\nIf any files with these extensions exist, this is a finding.\n\nThis 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.","fixText":"Remove any certificate installation files (*.p12 and *.pfx) found on a system.\n\nNote: This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files.","ccis":["CCI-000366"]},{"vulnId":"V-205853","ruleId":"SV-205853r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 FTP servers must be configured to prevent anonymous logons.","description":"The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult.\n\nUsing 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.","checkContent":"If FTP is not installed on the system, this is NA.\n\nOpen \"Internet Information Services (IIS) Manager\".\n\nSelect the server.\n\nDouble-click \"FTP Authentication\".\n\nIf the \"Anonymous Authentication\" status is \"Enabled\", this is a finding.","fixText":"Configure the FTP service to prevent anonymous logons.\n\nOpen \"Internet Information Services (IIS) Manager\".\n\nSelect the server.\n\nDouble-click \"FTP Authentication\".\n\nSelect \"Anonymous Authentication\".\n\nSelect \"Disabled\" under \"Actions\".","ccis":["CCI-000366"]},{"vulnId":"V-205854","ruleId":"SV-205854r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 FTP servers must be configured to prevent access to the system drive.","description":"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.","checkContent":"If FTP is not installed on the system, this is NA.\n\nOpen \"Internet Information Services (IIS) Manager\".\n\nSelect \"Sites\" under the server name.\n\nFor any sites with a Binding that lists FTP, right-click the site and select \"Explore\".\n\nIf the site is not defined to a specific folder for shared FTP resources, this is a finding.\n\nIf the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding.","fixText":"Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system.","ccis":["CCI-000366"]},{"vulnId":"V-205855","ruleId":"SV-205855r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have orphaned security identifiers (SIDs) removed from user rights.","description":"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.","checkContent":"Review the effective User Rights setting in Local Group Policy Editor.\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.\n\nReview 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-\".)\n\nIf any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /export /areas USER_RIGHTS /cfg c:\\path\\UserRights.txt\n\nThe 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. \n\nIf any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding.\n\nSID - Group\nS-1-5-11 - Authenticated Users\nS-1-5-113 - Local account\nS-1-5-114 - Local account and member of Administrators group\nS-1-5-19 - Local Service\nS-1-5-20 - Network Service\nS-1-5-32-544 - Administrators\nS-1-5-32-546 - Guests\nS-1-5-6 - Service\nS-1-5-9 - Enterprise Domain Controllers\nS-1-5-domain-512 - Domain Admins\nS-1-5-root domain-519 - Enterprise Admins\nS-1-5-80-3139157870-2983391045-3678747466-658725712-1809340420 - NT Service\\WdiServiceHost","fixText":"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.","ccis":["CCI-000366"]},{"vulnId":"V-205856","ruleId":"SV-205856r991589_rule","severity":"low","ruleTitle":"Windows Server 2019 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS.","description":"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.","checkContent":"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.\n\nVerify the system firmware is configured to run in \"UEFI\" mode, not \"Legacy BIOS\".\n\nRun \"System Information\".\n\nUnder \"System Summary\", if \"BIOS Mode\" does not display \"UEFI\", this is a finding.","fixText":"Configure UEFI firmware to run in \"UEFI\" mode, not \"Legacy BIOS\" mode.","ccis":["CCI-000366"]},{"vulnId":"V-205857","ruleId":"SV-205857r991589_rule","severity":"low","ruleTitle":"Windows Server 2019 must have Secure Boot enabled.","description":"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.","checkContent":"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.  \n\nRun \"System Information\".\n\nUnder \"System Summary\", if \"Secure Boot State\" does not display \"On\", this is a finding.\n\nOn server core installations, run the following PowerShell command:\n\nConfirm-SecureBootUEFI\n\nIf a value of \"True\" is not returned, this is a finding.","fixText":"Enable Secure Boot in the system firmware.","ccis":["CCI-000366"]},{"vulnId":"V-205858","ruleId":"SV-205858r991589_rule","severity":"low","ruleTitle":"Windows Server 2019 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing.","description":"Configuring the system to disable IPv6 source routing protects against spoofing.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Tcpip6\\Parameters\\\n\nValue Name: DisableIPSourceRouting\n\nType: REG_DWORD\nValue: 0x00000002 (2)","fixText":"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.\n\nThis 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.","ccis":["CCI-000366"]},{"vulnId":"V-205859","ruleId":"SV-205859r991589_rule","severity":"low","ruleTitle":"Windows Server 2019 source routing must be configured to the highest protection level to prevent Internet Protocol (IP) source routing.","description":"Configuring the system to disable IP source routing protects against spoofing.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters\\\n\nValue Name: DisableIPSourceRouting\n\nValue Type: REG_DWORD\nValue: 0x00000002 (2)","fixText":"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.\n\nThis 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.","ccis":["CCI-000366"]},{"vulnId":"V-205860","ruleId":"SV-205860r991589_rule","severity":"low","ruleTitle":"Windows Server 2019 must be configured to prevent Internet Control Message Protocol (ICMP) redirects from overriding Open Shortest Path First (OSPF)-generated routes.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters\\\n\nValue Name: EnableICMPRedirect\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> MSS (Legacy) >> \"MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes\" to \"Disabled\".\n\nThis 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.","ccis":["CCI-000366"]},{"vulnId":"V-205861","ruleId":"SV-205861r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 insecure logons to an SMB server must be disabled.","description":"Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper access.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\LanmanWorkstation\\\n\nValue Name: AllowInsecureGuestAuth\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Network >> Lanman Workstation >> \"Enable insecure guest logons\" to \"Disabled\".","ccis":["CCI-000366"]},{"vulnId":"V-205862","ruleId":"SV-205862r991589_rule","severity":"medium","ruleTitle":"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.","description":"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.","checkContent":"This requirement is applicable to domain-joined systems. For standalone or nondomain-joined systems, this is NA.\n\nIf the following registry values do not exist or are not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\NetworkProvider\\HardenedPaths\\\n\nValue Name: \\\\*\\NETLOGON\nValue Type: REG_SZ\nValue: RequireMutualAuthentication=1, RequireIntegrity=1\n\nValue Name: \\\\*\\SYSVOL\nValue Type: REG_SZ\nValue: RequireMutualAuthentication=1, RequireIntegrity=1\n\nAdditional entries would not be a finding.","fixText":"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):\n\nValue Name: \\\\*\\SYSVOL\nValue: RequireMutualAuthentication=1, RequireIntegrity=1\n\nValue Name: \\\\*\\NETLOGON\nValue: RequireMutualAuthentication=1, RequireIntegrity=1","ccis":["CCI-000366"]},{"vulnId":"V-205863","ruleId":"SV-205863r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to enable Remote host allows delegation of non-exportable credentials.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\CredentialsDelegation\\\n\nValue Name: AllowProtectedCreds\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> System >> Credentials Delegation >> \"Remote host allows delegation of non-exportable credentials\" to \"Enabled\".","ccis":["CCI-000366"]},{"vulnId":"V-205864","ruleId":"SV-205864r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection.","description":"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).","checkContent":"For standalone or nondomain-joined systems, this is NA.\n\nOpen \"PowerShell\" with elevated privileges (run as administrator).\n\nEnter the following:\n\n\"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\\Microsoft\\Windows\\DeviceGuard\"\n\nIf \"RequiredSecurityProperties\" does not include a value of \"2\" indicating \"Secure Boot\" (e.g., \"{1, 2}\"), this is a finding.\n\nIf \"Secure Boot and DMA Protection\" is configured, \"3\" will also be displayed in the results (e.g., \"{1, 2, 3}\").\n\nIf \"VirtualizationBasedSecurityStatus\" is not a value of \"2\" indicating \"Running\", this is a finding.\n\nAlternately:\n\nRun \"System Information\".\n\nUnder \"System Summary\", verify the following:\n\nIf \"Virtualization based security\" does not display \"Running\", this is a finding.\n\nIf \"Virtualization based Required security Properties\" does not display \"Base Virtualization Support, Secure Boot\", this is a finding.\n\nIf \"Secure Boot and DMA Protection\" is configured, \"DMA Protection\" will also be displayed (e.g., \"Base Virtualization Support, Secure Boot, DMA Protection\").\n\nThe 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.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\DeviceGuard\\\n\nValue Name: EnableVirtualizationBasedSecurity\nValue Type: REG_DWORD\nValue: 0x00000001 (1)\n\nValue Name: RequirePlatformSecurityFeatures\nValue Type: REG_DWORD\nValue: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection)\n\nA Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link:\n\nhttps://technet.microsoft.com/itpro/windows/keep-secure/credential-guard","fixText":"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.\n\nA Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link:\n\nhttps://technet.microsoft.com/itpro/windows/keep-secure/credential-guard","ccis":["CCI-000366"]},{"vulnId":"V-205865","ruleId":"SV-205865r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad.","description":"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.","checkContent":"The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce \"Good, unknown and bad but critical\" (preventing \"bad\").\n\nIf the registry value name below does not exist, this is not a finding.\n\nIf it exists and is configured with a value of \"0x00000007 (7)\", this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Policies\\EarlyLaunch\\\n\nValue Name: DriverLoadPolicy\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist)\n\nPossible values for this setting are:\n8 - Good only\n1 - Good and unknown\n3 - Good, unknown and bad but critical\n7 - All (which includes \"bad\" and would be a finding)","fixText":"The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce \"Good, unknown and bad but critical\" (preventing \"bad\").\n\nIf 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.","ccis":["CCI-000366"]},{"vulnId":"V-205866","ruleId":"SV-205866r1135352_rule","severity":"medium","ruleTitle":"Windows Server 2019 group policy objects must be reprocessed even if they have not changed.","description":"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.","checkContent":"This requirement is not applicable for Domain Controllers.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\Group Policy\\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\\\n\nValue Name: NoGPOListChanges\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"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.","ccis":["CCI-000366"]},{"vulnId":"V-205867","ruleId":"SV-205867r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (on battery).","description":"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).","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Power\\PowerSettings\\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\\\n\nValue Name: DCSettingIndex\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205868","ruleId":"SV-205868r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 users must be prompted to authenticate when the system wakes from sleep (plugged in).","description":"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).","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Power\\PowerSettings\\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\\\n\nValue Name: ACSettingIndex\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205869","ruleId":"SV-205869r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 Telemetry must be configured to Security or Basic.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\DataCollection\\\n\nValue Name: AllowTelemetry\n\nType: REG_DWORD\nValue: 0x00000000 (0) (Security), 0x00000001 (1) (Basic)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Data Collection >> \"Allow Telemetry\" to \"Enabled\" with \"0 - Security [Enterprise Only]\" or \"1 - Basic\" selected in \"Options\".","ccis":["CCI-000366"]},{"vulnId":"V-205870","ruleId":"SV-205870r991589_rule","severity":"low","ruleTitle":"Windows Server 2019 Windows Update must not obtain updates from other PCs on the Internet.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\DeliveryOptimization\\\n\nValue Name: DODownloadMode\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0) - No peering (HTTP Only)\n0x00000001 (1) - Peers on same NAT only (LAN)\n0x00000002 (2) - Local Network / Private group peering (Group)\n0x00000063 (99) - Simple download mode, no peering (Simple)\n0x00000064 (100) - Bypass mode, Delivery Optimization not used (Bypass)\n\nA value of 0x00000003 (3), Internet, is a finding.","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Delivery Optimization >> \"Download Mode\" to \"Enabled\" with any option except \"Internet\" selected.\n\nAcceptable selections include:\n\nBypass (100)\nGroup (2)\nHTTP only (0)\nLAN (1)\nSimple (99)","ccis":["CCI-000366"]},{"vulnId":"V-205871","ruleId":"SV-205871r991589_rule","severity":"low","ruleTitle":"Windows Server 2019 Turning off File Explorer heap termination on corruption must be disabled.","description":"Legacy plug-in applications may continue to function when a File Explorer session has become corrupt. Disabling this feature will prevent this.","checkContent":"The default behavior is for File Explorer heap termination on corruption to be enabled.\n\nIf the registry Value Name below does not exist, this is not a finding.\n\nIf it exists and is configured with a value of \"0\", this is not a finding.\n\nIf it exists and is configured with a value of \"1\", this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\Explorer\\\n\nValue Name: NoHeapTerminationOnCorruption\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0) (or if the Value Name does not exist)","fixText":"The default behavior is for File Explorer heap termination on corruption to be disabled.\n\nIf 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\".","ccis":["CCI-000366"]},{"vulnId":"V-205872","ruleId":"SV-205872r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 File Explorer shell protocol must run in protected mode.","description":"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.","checkContent":"The default behavior is for shell protected mode to be turned on for File Explorer.\n\nIf the registry value name below does not exist, this is not a finding.\n\nIf it exists and is configured with a value of \"0\", this is not a finding.\n\nIf it exists and is configured with a value of \"1\", this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\\n\nValue Name: PreXPSP2ShellProtocolBehavior\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0) (or if the Value Name does not exist)","fixText":"The default behavior is for shell protected mode to be turned on for File Explorer.\n\nIf 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\".","ccis":["CCI-000366"]},{"vulnId":"V-205873","ruleId":"SV-205873r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must prevent attachments from being downloaded from RSS feeds.","description":"Attachments from RSS feeds may not be secure. This setting will prevent attachments from being downloaded from RSS feeds.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Internet Explorer\\Feeds\\\n\nValue Name: DisableEnclosureDownload\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> RSS Feeds >> \"Prevent downloading of enclosures\" to \"Enabled\".","ccis":["CCI-000366"]},{"vulnId":"V-205874","ruleId":"SV-205874r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 users must be notified if a web-based program attempts to install software.","description":"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.","checkContent":"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.\n\nIf the registry value name below does not exist, this is not a finding.\n\nIf it exists and is configured with a value of \"0\", this is not a finding.\n\nIf it exists and is configured with a value of \"1\", this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\Installer\\\n\nValue Name: SafeForScripting\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0) (or if the Value Name does not exist)","fixText":"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.\n\nIf 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\".","ccis":["CCI-000366"]},{"vulnId":"V-205875","ruleId":"SV-205875r991589_rule","severity":"high","ruleTitle":"Windows Server 2019 directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access.","description":"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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nOpen \"Command Prompt\" (not elevated).\n\nRun \"ldp.exe\".\n\nFrom the \"Connection menu\", select \"Bind\".\n\nClear the User, Password, and Domain fields.\n\nSelect \"Simple bind\" for the Bind type and click \"OK\".\n\nConfirmation of anonymous access will be displayed at the end:\n\nres = ldap_simple_bind_s\nAuthenticated as: 'NT AUTHORITY\\ANONYMOUS LOGON'\n\nFrom the \"Browse\" menu, select \"Search\".\n\nIn the Search dialog, enter the DN of the domain naming context (generally something like \"dc=disaost,dc=mil\") in the Base DN field.\n\nClear the Attributes field and select \"Run\".\n\nError messages should display related to Bind and user not authenticated.\n\nIf attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding.\n\nThe following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access.\n\nNetwork hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. \n\nPremise 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.","fixText":"Configure directory data (outside the root DSE) of a non-public directory to prevent anonymous access.\n\nFor AD, there are multiple configuration items that could enable anonymous access.\n\nChanging 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).\n\nThe dsHeuristics option is used. This is addressed in check V-8555 in the AD Forest STIG.","ccis":["CCI-000366"]},{"vulnId":"V-205876","ruleId":"SV-205876r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 domain controllers must be configured to allow reset of machine account passwords.","description":"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.","checkContent":"This applies to domain controllers. It is NA for other systems.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\Parameters\\\n\nValue Name: RefusePasswordChange\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> \"Domain controller: Refuse machine account password changes\" to \"Disabled\".","ccis":["CCI-000366"]},{"vulnId":"V-205877","ruleId":"SV-205877r991589_rule","severity":"medium","ruleTitle":"The password for the krbtgt account on a domain must be reset at least every 180 days.","description":"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).\n\nThe 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.","checkContent":"This requirement is applicable to domain controllers; it is NA for other systems. \n\nOpen \"Windows PowerShell\".\n\nEnter \"Get-ADUser krbtgt -Property PasswordLastSet\".\n\nIf the \"PasswordLastSet\" date is more than 180 days old, this is a finding.","fixText":"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 reauthenticate (including application services) but is desired if a compromise is suspected.\n\nPowerShell scripts are available to accomplish this such as at the following link:\n\nhttps://docs.microsoft.com/en-us/answers/questions/97108/resetting-the-krbtgt-account-password-in-a-domain.html\n\nAll scripts should be tested.\n\nOpen \"Active Directory Users and Computers\" (available from various menus or run \"dsa.msc\").\n\nSelect \"Advanced Features\" in the \"View\" menu if not previously selected.\n\nSelect the \"Users\" node.\n\nRight-click on the krbtgt account and select \"Reset password\".\n\nEnter a password that meets password complexity requirements.\n\nClear the \"User must change password at next logon\" check box.\n\nThe system will automatically change this to a system-generated complex password.","ccis":["CCI-000366"]},{"vulnId":"V-205906","ruleId":"SV-205906r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must limit the caching of logon credentials to four or less on domain-joined member servers.","description":"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.","checkContent":"This applies to member servers. For domain controllers and standalone or nondomain-joined systems, this is NA.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive:  HKEY_LOCAL_MACHINE\nRegistry Path:  \\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\\n\nValue Name:  CachedLogonsCount\n\nValue Type:  REG_SZ\nValue:  4 (or less)","fixText":"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.","ccis":["CCI-000366"]},{"vulnId":"V-205907","ruleId":"SV-205907r991589_rule","severity":"high","ruleTitle":"Windows Server 2019 must be running Credential Guard on domain-joined member servers.","description":"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.","checkContent":"For domain controllers and standalone or nondomain-joined systems, this is NA.\n\nOpen \"PowerShell\" with elevated privileges (run as administrator).\n\nEnter the following:\n\n\"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\\Microsoft\\Windows\\DeviceGuard\"\n\nIf \"SecurityServicesRunning\" does not include a value of \"1\" (e.g., \"{1, 2}\"), this is a finding.\n\nAlternately:\n\nRun \"System Information\".\n\nUnder \"System Summary\", verify the following:\n\nIf \"Device Guard Security Services Running\" does not list \"Credential Guard\", this is a finding.\n\nThe 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.\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\DeviceGuard\\\n\nValue Name: LsaCfgFlags\nValue Type: REG_DWORD\nValue: 0x00000001 (1) (Enabled with UEFI lock)\n\nA Microsoft article on Credential Guard system requirement can be found at the following link:\n\nhttps://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements","fixText":"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\".\n\nA Microsoft article on Credential Guard system requirement can be found at the following link:\n\nhttps://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements\n\nSeverity 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:\n\nThe use of Microsoft Local Administrator Password Solution (LAPS) or similar products to control different local administrative passwords for all affected servers. This is to include a strict password change requirement (60 days or less).\n….\nStrict 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.\n….\nUse of a Privileged Access Workstation (PAW) and adherence to the Clean Source principle for administering affected servers. \n….\nBoundary Protection that is currently in place to protect from vulnerabilities in the network/servers.\n….\nWindows Defender rule block credential stealing from LSASS.exe is applied.  This rule can only be applied if Windows Defender is in use.\n….\nThe overall number of vulnerabilities that are unmitigated on the network/servers.","ccis":["CCI-000366"]},{"vulnId":"V-205908","ruleId":"SV-205908r991589_rule","severity":"high","ruleTitle":"Windows Server 2019 must prevent local accounts with blank passwords from being used from the network.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\\n\nValue Name: LimitBlankPasswordUse\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205909","ruleId":"SV-205909r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 built-in administrator account must be renamed.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options.\n\nIf the value for \"Accounts: Rename administrator account\" is not set to a value other than \"Administrator\", this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"NewAdministratorName\" is not something other than \"Administrator\" in the file, this is a finding.","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205910","ruleId":"SV-205910r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 built-in guest account must be renamed.","description":"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.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options.\n\nIf the value for \"Accounts: Rename guest account\" is not set to a value other than \"Guest\", this is a finding.\n\nFor server core installations, run the following command:\n\nSecedit /Export /Areas SecurityPolicy /CFG C:\\Path\\FileName.Txt\n\nIf \"NewGuestName\" is not something other than \"Guest\" in the file, this is a finding.","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205911","ruleId":"SV-205911r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 maximum age for machine account passwords must be configured to 30 days or less.","description":"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.","checkContent":"This is the default configuration for this setting (30 days).\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\Parameters\\\n\nValue Name: MaximumPasswordAge\n\nValue Type: REG_DWORD\nValue: 0x0000001e (30) (or less, but not 0)","fixText":"This is the default configuration for this setting (30 days).\n\nConfigure 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).","ccis":["CCI-000366"]},{"vulnId":"V-205912","ruleId":"SV-205912r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 Smart Card removal option must be configured to Force Logoff or Lock Workstation.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon\\\n \nValue Name: scremoveoption\n\nValue Type: REG_SZ\nValue: 1 (Lock Workstation) or 2 (Force Logoff)\n\nIf 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.","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205913","ruleId":"SV-205913r991589_rule","severity":"high","ruleTitle":"Windows Server 2019 must not allow anonymous SID/Name translation.","description":"Allowing anonymous SID/Name translation can provide sensitive information for accessing a system. Only authorized users must be able to perform such translations.","checkContent":"Verify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options.\n\nIf the value for \"Network access: Allow anonymous SID/Name translation\" is not set to \"Disabled\", this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> \"Network access: Allow anonymous SID/Name translation\" to \"Disabled\".","ccis":["CCI-000366"]},{"vulnId":"V-205914","ruleId":"SV-205914r991589_rule","severity":"high","ruleTitle":"Windows Server 2019 must not allow anonymous enumeration of Security Account Manager (SAM) accounts.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\\n\nValue Name: RestrictAnonymousSAM\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205915","ruleId":"SV-205915r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to prevent anonymous users from having the same permissions as the Everyone group.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\\n\nValue Name: EveryoneIncludesAnonymous\n\nValue Type: REG_DWORD\nValue: 0x00000000 (0)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205916","ruleId":"SV-205916r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\LSA\\\n\nValue Name: UseMachineId\n\nType: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205917","ruleId":"SV-205917r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must prevent NTLM from falling back to a Null session.","description":"NTLM sessions that are allowed to fall back to Null (unauthenticated) sessions may gain unauthorized access.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\LSA\\MSV1_0\\\n\nValue Name: allownullsessionfallback\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> Security Options >> \"Network security: Allow LocalSystem NULL session fallback\" to \"Disabled\".","ccis":["CCI-000366"]},{"vulnId":"V-205918","ruleId":"SV-205918r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must prevent PKU2U authentication using online identities.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\LSA\\pku2u\\\n\nValue Name: AllowOnlineID\n\nType: REG_DWORD\nValue: 0x00000000 (0)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205919","ruleId":"SV-205919r991589_rule","severity":"high","ruleTitle":"Windows Server 2019 LAN Manager authentication level must be configured to send NTLMv2 response only and to refuse LM and NTLM.","description":"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 or nondomain-joined computers that are running later versions.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\\n\nValue Name: LmCompatibilityLevel\n\nValue Type: REG_DWORD\nValue: 0x00000005 (5)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205920","ruleId":"SV-205920r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to at least negotiate signing for LDAP client signing.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Services\\LDAP\\\n\nValue Name: LDAPClientIntegrity\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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.","ccis":["CCI-000366"]},{"vulnId":"V-205921","ruleId":"SV-205921r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\MSV1_0\\\n\nValue Name: NTLMMinClientSec\n\nValue Type: REG_DWORD\nValue: 0x20080000 (537395200)","fixText":"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).","ccis":["CCI-000366"]},{"vulnId":"V-205922","ruleId":"SV-205922r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Lsa\\MSV1_0\\\n\nValue Name: NTLMMinServerSec\n\nValue Type: REG_DWORD\nValue: 0x20080000 (537395200)","fixText":"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).","ccis":["CCI-000366"]},{"vulnId":"V-205923","ruleId":"SV-205923r991589_rule","severity":"low","ruleTitle":"Windows Server 2019 default permissions of global system objects must be strengthened.","description":"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.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\\n\nValue Name: ProtectionMode\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-205924","ruleId":"SV-205924r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must preserve zone information when saving attachments.","description":"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.","checkContent":"The default behavior is for Windows to mark file attachments with their zone information.\n\nIf the registry Value Name below does not exist, this is not a finding.\n\nIf it exists and is configured with a value of \"2\", this is not a finding.\n\nIf it exists and is configured with a value of \"1\", this is a finding.\n\nRegistry Hive: HKEY_CURRENT_USER\nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\Attachments\\\n\nValue Name: SaveZoneInformation\n\nValue Type: REG_DWORD\nValue: 0x00000002 (2) (or if the Value Name does not exist)","fixText":"The default behavior is for Windows to mark file attachments with their zone information.\n\nIf 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\".","ccis":["CCI-000366"]},{"vulnId":"V-205925","ruleId":"SV-205925r991591_rule","severity":"medium","ruleTitle":"Windows Server 2019 must disable automatically signing in the last interactive user after a system-initiated restart.","description":"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.","checkContent":"Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.\n\nRegistry Hive: HKEY_LOCAL_MACHINE \nRegistry Path: \\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\\n\nValue Name: DisableAutomaticRestartSignOn\n\nValue Type: REG_DWORD\nValue: 0x00000001 (1)","fixText":"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\".","ccis":["CCI-000366"]},{"vulnId":"V-214936","ruleId":"SV-214936r991589_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have a host-based firewall installed and enabled.","description":"A firewall provides a line of defense against attack, allowing or blocking inbound and outbound connections based on a set of rules.","checkContent":"Determine if a host-based firewall is installed and enabled on the system.\n\nIf a host-based firewall is not installed and enabled on the system, this is a finding.\n\nThe configuration requirements will be determined by the applicable firewall STIG.","fixText":"Install and enable a host-based firewall on the system.","ccis":["CCI-000366","CCI-002080"]},{"vulnId":"V-257503","ruleId":"SV-257503r958420_rule","severity":"medium","ruleTitle":"Windows Server 2019 must have PowerShell Transcription enabled.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nEnabling PowerShell Transcription will record detailed information from the processing of PowerShell commands and scripts. This can provide additional detail when malware has run on a system.","checkContent":"If the following registry value does not exist or is not configured as specified, this is a finding:\n\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: \\SOFTWARE\\Policies\\Microsoft\\Windows\\PowerShell\\Transcription\\\n\nValue Name: EnableTranscripting\n\nValue Type: REG_DWORD\nValue: 1","fixText":"Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Windows PowerShell >> \"Turn on PowerShell Transcription\" to \"Enabled\".\n\nSpecify the Transcript output directory to point to a Central Log Server or another secure location to prevent user access.","ccis":["CCI-000134"]},{"vulnId":"V-271428","ruleId":"SV-271428r1137691_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured for certificate-based authentication for domain controllers.","description":"Active Directory domain services elevation of privilege vulnerability could allow a user rights to the system, such as administrative and other high-level capabilities.","checkContent":"This applies to domain controllers. This is not applicable for member servers.\n\nIf the following registry value does not exist or is not configured as specified, this is a finding:\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: SYSTEM\\CurrentControlSet\\Services\\Kdc\n \nValue Name: StrongCertificateBindingEnforcement\n \nValue Type: REG_DWORD\nValue: 0x00000001 (1) or 0x00000002 (2)","fixText":"Configure the registry value.\nRegistry Hive: HKEY_LOCAL_MACHINE\nRegistry Path: SYSTEM\\CurrentControlSet\\Services\\Kdc\n \nValue Name: StrongCertificateBindingEnforcement\n \nValue Type: REG_DWORD\nValue: 0x00000001 (1) or 0x00000002 (2)","ccis":["CCI-000213"]},{"vulnId":"V-271429","ruleId":"SV-271429r1137691_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured for named-based strong mappings for certificates.","description":"Weak mappings give rise to security vulnerabilities and demand hardening measures. Certificate names must be correctly mapped to the intended user account in Active Directory. A lack of strong name-based mappings allows certain weak certificate mappings, such as Issuer/Subject AltSecID and User Principal Names (UPN) mappings, to be treated as strong mappings.","checkContent":"This applies to domain controllers. This is not applicable for member servers.\n\nVerify the effective setting in Local Group Policy Editor.\n\nRun \"gpedit.msc\".\nOr\nUsing the registry, check HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\KDC\\Parameters, Key: UseStrongNameMatches.                      \nOr\nUsing GPRESULT, check the applicable GPO for \"Allow name-based strong mappings for certificates\".\n\nNavigate to Local Computer Policy >> Computer Configuration >> Administrative Template >> System >> KDC >> Allow name-based strong mappings for certificates.\n\nIf \"Allow name-based strong mappings for certificates\" is not \"Enabled\", this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Administrative Template >> System >> KDC >> Allow name-based strong mappings for certificates to \"Enabled\".","ccis":["CCI-000213"]},{"vulnId":"V-278934","ruleId":"SV-278934r1135330_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit file system failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system 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.","checkContent":"Verify that Audit File System auditing has been enabled: \n\nComputer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit File System.\n\nIf \"Audit File System\" is not set to \"Failure\", this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> \"Audit File System\" with \"Failure\" selected.","ccis":["CCI-000172"]},{"vulnId":"V-278935","ruleId":"SV-278935r1135333_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit file system successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system 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.","checkContent":"Verify that Audit File System auditing has been enabled: \n\nComputer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit File System. \n\nIf \"Audit File System\" is not set to \"Success\", this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> \"Audit File System\" with \"Success\" selected.","ccis":["CCI-000172"]},{"vulnId":"V-278936","ruleId":"SV-278936r1135336_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit handle manipulation failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system 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.","checkContent":"Verify that Audit Handle Manipulation auditing has been enabled: \n\nComputer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Handle Manipulation. \n\nIf \"Audit Handle Manipulation\" is not set to \"Failure\", this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> \"Audit Handle Manipulation\" with \"Failure\" selected.","ccis":["CCI-000172"]},{"vulnId":"V-278937","ruleId":"SV-278937r1135339_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit handle manipulation successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system 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.","checkContent":"Verify that Audit Handle Manipulation auditing has been enabled: \n\nComputer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Handle Manipulation. \n\nIf \"Audit Handle Manipulation\" is not set to \"Success\", this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> \"Audit Handle Manipulation\" with \"Success\" selected.","ccis":["CCI-000172"]},{"vulnId":"V-278938","ruleId":"SV-278938r1135342_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit registry failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system 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.","checkContent":"Verify that Audit Registry auditing has been enabled: \n\nComputer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Registry. \n\nIf \"Audit Registry\" is not set to \"Failure\", this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> \"Audit Registry\" with \"Failure\" selected.","ccis":["CCI-000172"]},{"vulnId":"V-278939","ruleId":"SV-278939r1135345_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit registry successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system 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.","checkContent":"Verify that Audit Registry auditing has been enabled: \n\nComputer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Registry. \n\nIf \"Audit Registry\" is not set to \"Success\", this is a finding.","fixText":"Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> \"Audit Registry\" with \"Success\" selected.","ccis":["CCI-000172"]},{"vulnId":"V-278940","ruleId":"SV-278940r1141922_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit sensitive privilege use successes.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system 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.","checkContent":"Verify that Audit Sensitive Privilege Use auditing has been enabled: \n\nComputer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Privilege Use >> Audit Sensitive Privilege Use. \n\nIf \"Audit Sensitive Privilege Use\" is not set to \"Success\", this is a finding.","fixText":"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.","ccis":["CCI-000172"]},{"vulnId":"V-278941","ruleId":"SV-278941r1141925_rule","severity":"medium","ruleTitle":"Windows Server 2019 must be configured to audit sensitive privilege use failures.","description":"Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system 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.","checkContent":"Verify that Audit Sensitive Privilege Use auditing has been enabled: \n\nComputer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Privilege Use >> Audit Sensitive Privilege Use. \n\nIf \"Audit Sensitive Privilege Use\" is not set to \"Failure\", this is a finding.","fixText":"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.","ccis":["CCI-000172"]}]}