SV-225059r958408: Windows Server 2016 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing. | Microsoft Windows Server 2016 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

Windows Server 2016 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.

Description

Discussion Text

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. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000478-GPOS-00223

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-000068Not mappedCCI-002450V-73701SV-88365

References

DPMS Target Microsoft Windows Server 2016 DISA DPMS Target Microsoft Windows Server 2016 4205

Checks

DISA STIG (Manual Reference)

If the following registry value does not exist or is not configured as specified, this is a finding.

Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\

Value Name: Enabled

Value Type: REG_DWORD
Value: 0x00000001 (1)
 
Clients with this setting enabled will not be able to communicate via digitally encrypted or signed protocols with servers that do not support these algorithms. Both the browser and web server must be configured to use TLS; otherwise. the browser will not be able to connect to a secure site.

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

# Windows PowerShell
# Reconstructed from oval:mil.disa.stig.windows:def:1222
# Windows Server 2016 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Verifies 'System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing' is set to 'Enabled'
# registry_object (registry_test)
function test_1 {
  return (((@{String='reg_sz';ExpandString='reg_expand_sz';Binary='reg_binary';DWord='reg_dword';MultiString='reg_multi_sz';QWord='reg_qword';None='reg_none'}[(Get-Item -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy').GetValueKind('Enabled').ToString()]) -eq 'reg_dword') -and (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy' -Name 'Enabled' -ErrorAction SilentlyContinue) | Select-Object -ExpandProperty 'Enabled') -eq 1))
}

if (test_1) {
  Write-Output "PASS"
} else {
  Write-Output "FAIL"
}

Assessment Script Powered by AISyntax-verified

A standalone PowerShell script to assess this control automatically. Review before running it in your environment.

Syntax-checked as valid PowerShell. Not executed here — running it for real needs the actual ms_windows_server_2016 target this check assesses.

# OVAL Definition: oval:mil.disa.stig.windows:def:1222
$compliant = (Get-ItemProperty -Path "HKLM:\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy" -Name "Enabled" -ErrorAction SilentlyContinue).Enabled -eq 1
if ($compliant) { Write-Output "PASS"; Exit 0 } else { Write-Output "FAIL"; Exit 1 }

Remediation

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".