[REQ-END-116] Configure User Rights: Modify firmware environment values
Target Scope
- Applicable Systems: Tier 2 client workstations and member servers. (For Tier 0 Privileged Access Workstations, refer to tightened baseline REQ-PAW-108). (For Domain Controllers, refer to REQ-DC-130).
- Operating Systems: Windows 10 Enterprise/Professional (1809 and above), Windows 11 Enterprise/Pro, Windows Server 2016, 2019, 2022, and 2025.
Implementation Details
- Priority: Medium
- GPO Path / Registry Location:
- Policy Display Name:
Modify firmware environment values - Privilege Constant:
SeSystemEnvironmentPrivilege - GPO Path:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Modify firmware environment values - Registry Location: Stored inside local security database under privilege
SeSystemEnvironmentPrivilegeset to*S-1-5-32-544 (Administrators).
- Policy Display Name:
Rationale
The SeSystemEnvironmentPrivilege allows a process to query and modify Non-Volatile RAM (NVRAM) firmware environment variables via Win32 APIs GetFirmwareEnvironmentVariable and SetFirmwareEnvironmentVariable. NVRAM variables govern UEFI boot sequences, Secure Boot policies, boot configuration data (BCD) handoffs, and hardware configuration flags.
1. Technical Threat Vector & Abuse Mechanics
Adversaries exploit SeSystemEnvironmentPrivilege to install firmware bootkits and undermine OS integrity: (1) Secure Boot Bypasses: Attackers alter UEFI NVRAM variables to invalidate Secure Boot validation, allowing unsigned bootloaders or malicious early-launch payloads (e.g., BlackLotus UEFI bootkit) to execute before the Windows kernel loads; (2) Hypervisor Tampering: Modifying virtualization parameters in NVRAM can weaken Virtualization-Based Security (VBS) and Credential Guard; (3) Persistence: Firmware modifications persist across complete OS re-installations and drive replacements.
2. Architectural Defense & Least Privilege Enforcement
On general workstations and member servers, enforcing least privilege for this user right is critical for host isolation. Preventing unprivileged users or rogue applications from exercising this right stops local privilege escalation (LPE) and blocks adversaries from leveraging co-located user sessions to harvest credentials or pivot across the corporate subnet.
This privilege must be restricted strictly to Administrators (S-1-5-32-544). Standard users, interactive accounts, and standard applications must never be permitted to modify firmware environment variables.
3. MITRE ATT&CK Mapping
- T1542.001 - Pre-OS Boot: System Firmware
- T1562.001 - Impair Defenses: Disable or Modify Tools
- T1068 - Exploitation for Privilege Escalation
Legacy Impact & Compatibility
- Operational Impact: Restricting
SeSystemEnvironmentPrivilegetoAdministratorsprotects UEFI firmware integrity. Firmware update tools (e.g., OEM BIOS flashers) running under administrative credentials operate normally. Auditing is captured under Security Event ID 4672.
Implementation Steps
Option A: Group Policy Object (GPO) Configuration (Preferred)
- Open the Group Policy Management Console (
gpmc.msc). - Navigate to the targeted GPO linked to Tier 2 systems (e.g.,
GPO_Hardening_Endpoints). - In the console tree, browse to:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment - Open the policy
Modify firmware environment values. - Select the Define these policy settings check box.
- Configure the security principal allocation to:
*S-1-5-32-544 (Administrators). - Click Apply and OK.
- Apply and verify policy enforcement across target hosts using
gpupdate /forceand inspect withsecedit /export /cfg C:\Windows\Temp\sec_audit.cfg.
Option B: PowerShell & Registry Configuration (Remediation / Non-GPO)
Download Script: Configure-UraSeSystemEnvironmentPrivilege.ps1
# Configure-UraSeSystemEnvironmentPrivilege.ps1
$SecTempDir = Join-Path $env:TEMP "SecurityTemplates"
if (-not (Test-Path $SecTempDir)) { New-Item -Path $SecTempDir -ItemType Directory -Force | Out-Null }
$CfgFile = Join-Path $SecTempDir "ura_sesystemenvironmentprivilege.cfg"
$DbFile = Join-Path $SecTempDir "secedit_sesystemenvironmentprivilege.sdb"
$LogFile = Join-Path $SecTempDir "secedit.log"
$Process = Start-Process secedit -ArgumentList "/export /cfg `"$CfgFile`"" -Wait -NoNewWindow -PassThru
if ($Process.ExitCode -ne 0) { Throw "Failed to export security template" }
$ConfigText = Get-Content -Path $CfgFile -Raw
if ($ConfigText -notmatch "\[Privilege Rights\]") {
$ConfigText += "`r`n[Privilege Rights]`r`n"
}
$Lines = $ConfigText -split "`r?`n"
$NewLines = @()
$InPriv = $false
$KeyAdded = $false
foreach ($Line in $Lines) {
if ($Line -match "^\[(.*)\]$") {
if ($Matches[1] -eq "Privilege Rights") {
$InPriv = $true
} else {
$InPriv = $false
}
}
if ($InPriv -and $Line -match "^\s*SeSystemEnvironmentPrivilege\s*=") {
$NewLines += "SeSystemEnvironmentPrivilege = *S-1-5-32-544"
$KeyAdded = $true
} else {
$NewLines += $Line
}
}
if (-not $KeyAdded) {
# Find Privilege Rights section index and insert it right after
$Idx = $NewLines.IndexOf("[Privilege Rights]")
if ($Idx -ge 0) {
$NewLines.Insert($Idx + 1, "SeSystemEnvironmentPrivilege = *S-1-5-32-544")
} else {
$NewLines += "SeSystemEnvironmentPrivilege = *S-1-5-32-544"
}
}
$NewLines | Set-Content -Path $CfgFile -Force
$Proc = Start-Process secedit -ArgumentList "/configure /db `"$DbFile`" /cfg `"$CfgFile`" /areas USER_RIGHTS /log `"$LogFile`"" -Wait -NoNewWindow -PassThru
if ($Proc.ExitCode -ne 0) { Throw "Failed to configure secedit user rights" }
Remove-Item -Path $CfgFile, $DbFile -ErrorAction SilentlyContinue
To audit the hardening status: Download Script: Get-UraSeSystemEnvironmentPrivilegeStatus.ps1
# Get-UraSeSystemEnvironmentPrivilegeStatus.ps1
$SecTempDir = Join-Path $env:TEMP "SecurityTemplates"
if (-not (Test-Path $SecTempDir)) { New-Item -Path $SecTempDir -ItemType Directory -Force | Out-Null }
$CfgFile = Join-Path $SecTempDir "ura_audit_sesystemenvironmentprivilege.cfg"
$Process = Start-Process secedit -ArgumentList "/export /cfg `"$CfgFile`"" -Wait -NoNewWindow -PassThru
if ($Process.ExitCode -ne 0) {
Write-Output "Non-Compliant"
exit 1
}
$ConfigText = Get-Content -Path $CfgFile -Raw
Remove-Item -Path $CfgFile -ErrorAction SilentlyContinue
$Match = $ConfigText -match "(?mi)^\s*SeSystemEnvironmentPrivilege\s*=\s*(.*)$"
$CurrentValue = ""
if ($Match) {
$CurrentValue = $Matches[1].Trim()
}
$Expected = "*S-1-5-32-544"
if ($CurrentValue -eq $Expected) {
Write-Output "Compliant"
exit 0
} else {
Write-Output "Non-Compliant"
exit 1
}
Sources & Compliance References
- ANSSI Active Directory Hardening Guide: ANSSI Active Directory Hardening Guide: R28 (User Rights Assignment)
- CIS Benchmark: 2.2.39 (L1) Ensure 'Modify firmware environment values' is set to 'Administrators'
- Microsoft Security Baseline: User Rights Configuration specifications
- Microsoft Learn: User Rights Assignment Reference