SV-205669r1137691: Windows Server 2019 Deny log on as a service user right must be configured to include no accounts or groups (blank) on domain controllers. | Microsoft Windows Server 2019 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

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

Discussion Text

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities. The "Deny log on as a service" user right defines accounts that are denied logon as a service. Incorrect configurations could prevent services from starting and result in a denial of service.

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

IA Controls

NIST SP 800-53

Not mappedCCI-000213V-93003SV-103091

References

DPMS Target Microsoft Windows Server 2019 DISA DPMS Target Microsoft Windows Server 2019 2907

Checks

DISA STIG (Manual Reference)

This applies to domain controllers. A separate version applies to other systems.

Verify the effective setting in Local Group Policy Editor.

Run "gpedit.msc".

Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment.

If any accounts or groups are defined for the "Deny log on as a service" user right, this is a finding.

For server core installations, run the following command:

Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt

Review the text file.

If any SIDs are granted the "SeDenyServiceLogonRight" user right, this is a finding.

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.windows2019:def:205669
# Windows Server 2019 Deny log on as a service user right must be configured to include no accounts or groups (blank) on domain controllers.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Deny log on as a service - None
# userright_object (userright_test)
function test_1 {
  return (($__tmp = "$env:TEMP\scc_userrights_$([guid]::NewGuid().Guid).cfg"; secedit /export /cfg $__tmp /areas USER_RIGHTS /quiet | Out-Null; $__m = Select-String -Path $__tmp -Pattern '^SeDenyServiceLogonRight\s*=\s*(.*)$'; Remove-Item $__tmp -ErrorAction SilentlyContinue; if ($__m -and $__m.Matches[0].Groups[1].Value.Trim().Length -gt 0) { (($__m.Matches[0].Groups[1].Value -split ',') | ForEach-Object { $__sid = $_.Trim().TrimStart('*'); try { (New-Object System.Security.Principal.SecurityIdentifier($__sid)).Translate([System.Security.Principal.NTAccount]).Value -replace '^[^\\]*\\', '' } catch { $__sid } }) -join ',' } else { '' }) -eq '')
}

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_2019 target this check assesses.

# OVAL Definition: oval:mil.disa.stig.windows2019:def:205669
$userRight = Get-CimInstance -ClassName Win32_UserRight -Filter "UserRight = 'SE_DENY_SERVICE_LOGON_NAME'"
if ($userRight -eq $null -or $userRight.Members -eq $null -or $userRight.Members -contains "") { Write-Output "PASS"; exit 0 }
Write-Output "FAIL"; exit 1

Remediation

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