SV-254368r958408: Windows Server 2022 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications. | Microsoft Windows Server 2022 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

Windows Server 2022 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.

Description

Discussion Text

Allowing unsecure RPC communication exposes the system to man-in-the-middle attacks and data disclosure attacks. A man-in-the-middle attack occurs when an intruder captures packets between a client and server and modifies them before allowing the packets to be exchanged. Usually the attacker will modify the information in the packets in an attempt to cause either the client or server to reveal sensitive information. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093

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

IA Controls

NIST SP 800-53

Not mappedCCI-000068Not mappedCCI-001453

References

DPMS Target Microsoft Windows Server 2022 DISA DPMS Target Microsoft Windows Server 2022 5485

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.windows2022:def:254368
# Windows Server 2022 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Verifies 'Require secure RPC communication' 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\Software\Policies\Microsoft\Windows NT\Terminal Services').GetValueKind('fEncryptRPCTraffic').ToString()]) -eq 'reg_dword') -and (((Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Terminal Services' -Name 'fEncryptRPCTraffic' -ErrorAction SilentlyContinue) | Select-Object -ExpandProperty 'fEncryptRPCTraffic') -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_2022 target this check assesses.

# OVAL Definition: oval:mil.disa.stig.windows2022:def:254368
if (!(Test-Path -Path "HKLM:\Software\Policies\Microsoft\Windows NT\Terminal Services\fEncryptRPCTraffic" -ErrorAction SilentlyContinue) -or ((Get-ItemProperty -Path "HKLM:\Software\Policies\Microsoft\Windows NT\Terminal Services" -Name fEncryptRPCTraffic -ErrorAction SilentlyContinue).fEncryptRPCTraffic -ne 1)) { Write-Output "FAIL"; Exit 1 } else { Write-Output "PASS"; Exit 0 }

Remediation

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