LSA Protection
Verified with Microsoft Security Baseline (MSS / SecGuide) 25H2 — updated on July 10, 2026
Supported on: At least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
Path in the GPO console
Computer Configuration\Administrative Templates\MS Security Guide Description
For Windows 11, version 22H2 and beyond a new setting is used to configure this. IT can be located at 'System\Local Security Authority\Configures LSASS to run as a protected process' which provides additional configuration options. Enable LSA protection. For more information, see http://technet.microsoft.com/en-us/library/dn408187.aspx
Registry
HKLM
SYSTEM\CurrentControlSet\Control\Lsa Value name: RunAsPPL
Enabled: RunAsPPL = 1
Disabled: RunAsPPL = 0
Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: LSA Protection
; State: Enabled
; Supported on: At least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"RunAsPPL"=dword:00000001More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: LSA Protection
# State: Enabled
# Supported on: At least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
$path = 'HKLM:\SYSTEM\CurrentControlSet\Control\Lsa'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'RunAsPPL' -Value 1 -Type DWordIntune XML
No direct Policy CSP / OMA-URI mapping for this policy. Use the Intune Remediation tab, or ingest the ADMX in Intune.Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: LSA Protection
# State: Enabled
# Supported on: At least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Lsa' -Name 'RunAsPPL' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: LSA Protection
# State: Enabled
# Supported on: At least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
$path = 'HKLM:\SYSTEM\CurrentControlSet\Control\Lsa'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'RunAsPPL' -Value 1 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: LSA Protection
# State: Enabled
# Supported on: At least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: LSA Protection
# State: Enabled
# Supported on: At least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Lsa' -Name 'RunAsPPL' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: LSA Protection
# State: Enabled
# Supported on: At least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
$path = 'HKLM:\SYSTEM\CurrentControlSet\Control\Lsa'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'RunAsPPL' -Value 1 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.