What changed in Windows 10 STIG V2R3V2R3 changes

Windows 10 STIG V2R3 (2021-11-01) replaced V2R2 (2021-05-04): 2 checks added, 30 removed, 8 updated. It has 257 checks, against 285 in V2R2.

  • 2 added
  • 30 removed
  • 8 updated

Updated fields: Check text 6Fix text 3Discussion 2Title 1

Added in V2R3 (2)

  • V-250318CAT IIPowerShell Transcription must be enabled on Windows 10.
  • V-250319CAT IIHardened UNC Paths must be defined to require mutual authentication and integrity for at least the 11*1SYSVOL and 11*1NETLOGON shares.

Removed since V2R2 (30)

  • V-220804CAT IIHardened UNC Paths must be defined to require mutual authentication and integrity for at least the 11*1SYSVOL and 11*1NETLOGON shares.
  • V-220873CAT IIWindows 10 Exploit Protection system-level mitigation, Data Execution Prevention (DEP), must be on.
  • V-220874CAT IIWindows 10 Exploit Protection system-level mitigation, Randomize memory allocations (Bottom-Up ASLR), must be on.
  • V-220875CAT IIWindows 10 Exploit Protection system-level mitigation, Control flow guard (CFG), must be on.
  • V-220876CAT IIWindows 10 Exploit Protection system-level mitigation, Validate exception chains (SEHOP), must be on.
  • V-220877CAT IIWindows 10 Exploit Protection system-level mitigation, Validate heap integrity, must be on.
  • V-220878CAT IIExploit Protection mitigations in Windows 10 must be configured for Acrobat.exe.
  • V-220879CAT IIExploit Protection mitigations in Windows 10 must be configured for AcroRd32.exe.
  • V-220880CAT IIExploit Protection mitigations in Windows 10 must be configured for chrome.exe.
  • V-220881CAT IIExploit Protection mitigations in Windows 10 must be configured for EXCEL.EXE.
  • V-220882CAT IIExploit Protection mitigations in Windows 10 must be configured for firefox.exe.
  • V-220883CAT IIExploit Protection mitigations in Windows 10 must be configured for FLTLDR.EXE.
  • V-220884CAT IIExploit Protection mitigations in Windows 10 must be configured for GROOVE.EXE.
  • V-220885CAT IIExploit Protection mitigations in Windows 10 must be configured for iexplore.exe.
  • V-220886CAT IIExploit Protection mitigations in Windows 10 must be configured for INFOPATH.EXE.
  • V-220887CAT IIExploit Protection mitigations in Windows 10 must be configured for java.exe, javaw.exe, and javaws.exe.
  • V-220888CAT IIExploit Protection mitigations in Windows 10 must be configured for lync.exe.
  • V-220889CAT IIExploit Protection mitigations in Windows 10 must be configured for MSACCESS.EXE.
  • V-220890CAT IIExploit Protection mitigations in Windows 10 must be configured for MSPUB.EXE.
  • V-220891CAT IIExploit Protection mitigations in Windows 10 must be configured for OIS.EXE.
  • V-220893CAT IIExploit Protection mitigations in Windows 10 must be configured for OUTLOOK.EXE.
  • V-220894CAT IIExploit Protection mitigations in Windows 10 must be configured for plugin-container.exe.
  • V-220895CAT IIExploit Protection mitigations in Windows 10 must be configured for POWERPNT.EXE.
  • V-220896CAT IIExploit Protection mitigations in Windows 10 must be configured for PPTVIEW.EXE.
  • V-220897CAT IIExploit Protection mitigations in Windows 10 must be configured for VISIO.EXE.
  • V-220898CAT IIExploit Protection mitigations in Windows 10 must be configured for VPREVIEW.EXE.
  • V-220899CAT IIExploit Protection mitigations in Windows 10 must be configured for WINWORD.EXE.
  • V-220900CAT IIExploit Protection mitigations in Windows 10 must be configured for wmplayer.exe.
  • V-220901CAT IIExploit Protection mitigations in Windows 10 must be configured for wordpad.exe.
  • V-230220CAT IIPowerShell Transcription must be enabled on Windows 10.

Updated in V2R3 (8)

V-220701CAT IIWindows 10 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where ESS is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).Title, Discussion

Title

Windows 10 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where HBSSESS is used; 30 days, for any additional internal network scans not covered by HBSSESS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).

Discussion

An approved tool for continuous network scanning must be installed and configured to run. Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. To support this requirement, the operating system may have an integrated solution incorporating continuous scanning using HBSSESS and periodic scanning using other tools, as specified in the requirement.

V-220707CAT IThe Windows 10 system must use an anti-virus program.Check text, Fix text

Check text

Verify an anti-virus solution is installed on the system and in use. The anti-virus solution may be bundled with an approved host-basedEndpoint securitySecurity solutionSolution. Verify if Windows Defender is in use or enabled: Open "PowerShell". Enter "get-service | where {$_.DisplayName -Like "*Defender*"} | Select Status,DisplayName" Verify third-party antivirus is in use or enabled: Open "PowerShell". Enter "get-service | where {$_.DisplayName -Like "*mcafee*"} | Select Status,DisplayName" Enter "get-service | where {$_.DisplayName -Like "*symantec*"} | Select Status,DisplayName" If there is no anti-virus solution installed on the system, this is a finding.

Fix text

If no anti-virus software is on the system and in use, install Windows Defender or a third-party anti-virus solution.

V-220729CAT IIThe Server Message Block (SMB) v1 protocol must be disabled on the system.Check text

Check text

Different methods are available to disable SMBv1 on Windows 10. This is the preferred method, however if V-74723220730 and V-74725220731 are configured, this is NA. Run "Windows PowerShell" with elevated privileges (run as administrator). Enter the following: Get-WindowsOptionalFeature -Online | Where FeatureName -eq SMB1Protocol If "State : Enabled" is returned, this is a finding. Alternately: Search for "Features". Select "Turn Windows features on or off". If "SMB 1.0/CIFS File Sharing Support" is selected, this is a finding.

V-220730CAT IIThe Server Message Block (SMB) v1 protocol must be disabled on the SMB server.Check text

Check text

Different methods are available to disable SMBv1 on Windows 10, if V-70639220729 is configured, this is NA. If the following registry value does not exist or is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: 1SYSTEM1CurrentControlSet1Services1LanmanServer1Parameters1 Value Name: SMB1 Type: REG_DWORD Value: 0x00000000 (0)

V-220731CAT IIThe Server Message Block (SMB) v1 protocol must be disabled on the SMB client.Check text

Check text

Different methods are available to disable SMBv1 on Windows 10, if V-70639220729 is configured, this is NA. If the following registry value is not configured as specified, this is a finding: Registry Hive: HKEY_LOCAL_MACHINE Registry Path: 1SYSTEM1CurrentControlSet1Services1mrxsmb101 Value Name: Start Type: REG_DWORD Value: 0x00000004 (4)

V-220833CAT IIIf Enhanced diagnostic data is enabled it must be limited to the minimum required to support Windows Analytics.Check text

Check text

This setting requires v1709 or later of Windows 10; it is NA for prior versions. If "Enhanced" level is enabled for telemetry, this must be configured. If "Security" or "Basic" are configured, this is NA. (See V-220922220834). If the following registry value does not exist or is not configured as specified, this is a finding. Registry Hive: HKEY_LOCAL_MACHINE Registry Path: 1SOFTWARE1Policies1Microsoft1Windows1DataCollection1 Value Name: LimitEnhancedDiagnosticDataWindowsAnalytics Type: REG_DWORD Value: 0x00000001 (1)

V-220946CAT IIWindows 10 must use multifactor authentication for local and network access to privileged and non-privileged accounts.Fix text

Fix text

For non-domain joined systems, configuring Windows Hello for sign on options would be suggested based on the organizations needs and capabilities. Note: Before applying, the supplemental guidance provided with the STIG should be consulted to ensure continued access to the operating system.

V-220952CAT IIPasswords for enabled local Administrator accounts must be changed at least every 60 days.Check text, Fix text, Discussion

Check text

Review the password last set date for the enabled local Administrator account. On the local domain joined workstation: Open "PowerShell". Enter "Get-LocalUser –Name * | Select-Object *" If the "PasswordLastSet" date is greater than "60" days old for the local Administrator account for administering the computer/domain, this is a finding.

Fix text

Change the enabled local Administrator account password at least every "60" days. AutomatedIt tools,is suchhighly asrecommended to use Microsoft's LAPS, which may be used on domain-joined member servers to meet this requirement. The AO still has the overall authority to use another equivalent capability to accomplish the check.

Discussion

The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. A local Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for enabled Administrator accounts on a regular basis will limit its exposure. OrganizationsIt thatis usehighly anrecommended automatedto tool,use such Microsoft's Local Administrator Password Solution (LAPS),. on domainDomain-joined systems can configure this to occur more frequently. LAPS will change the password every "30" days by default. The AO still has the overall authority to use another equivalent capability to accomplish the check.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V2R3 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.