What changed in Microsoft Windows Server 2016 STIG V2R10V2R10 changes

Microsoft Windows Server 2016 STIG V2R10 (2025-01-15) replaced V2R9 (2024-11-15): 1 check added, 1 updated. It has 273 checks, against 272 in V2R9.

V2R10 checklistV2R9 checklist Compare V2R9 and V2R10 in STIG Compare

  • 1 added
  • 0 removed
  • 1 updated

Updated fields: Check text 1Fix text 1Discussion 1

Added in V2R10 (1)

  • V-271430CAT IWindows Server 2016 must be configured for name-based strong mappings for certificates.

Updated in V2R10 (1)

V-224828CAT ISystems must be maintained at a supported servicing level.Check text, Fix text, Discussion

Check text

This STIG is sunset and no longer maintained. Open "Command Prompt". Enter "winver.exe". If the "About Windows" dialog box doesdisplays not display "Microsoft Windows Server Version 1607 (Build 14393.xxx)" orand greater,there this is anot finding. Previewdocumented versionsextended mustsupport notfor beMicrosoft usedWindows inServer a2016, productionthis environmentis a finding.

Fix text

Update the system to a Version 1607 (Build 14393.xxx) or greater.Upgrade the operating system to a supported version.

Discussion

Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leaveleaves them subject to exploitation. Systems must be maintained at a servicing level supported by the vendor with new security updates.

V-224828 in V2R10

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 V2R10 no longer has.

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