Open in the explorer

Configures LSASS to run as a protected process

Configure LSASS pour qu’il s’exécute en tant que processus protégé

Type
Computer
GPO path
Computer Configuration › Policies › Administrative Templates › System › Local Security Authority FR: Configuration ordinateur › Stratégies › Modèles d'administration › Système › Autorité de sécurité locale
Supported on
At least Windows 10 Version 1903 FR: Au moins Windows 10 version 1903
ADMX file
LocalSecurityAuthority.admx
Internal name
LocalSecurityAuthority/ConfigureLsaProtectedProcess

Explanation

This policy controls the configuration under which LSASS is run.

If you do not configure this policy and there is no current setting in the registry, LSA will run as protected process for all clean installed, HVCI capable, client SKUs. This configuration is not UEFI locked. This can be overridden if the policy is configured.

If you configure and set this policy setting to "Disabled", LSA will not run as a protected process.

If you configure and set this policy setting to "EnabledWithUEFILock," LSA will run as a protected process and this configuration is UEFI locked.

If you configure and set this policy setting to "EnabledWithoutUEFILock", LSA will run as a protected process and this configuration is not UEFI locked.

French text from Windows 11 26H2

Cette stratégie contrôle la configuration sous laquelle LSASS est exécuté.

Si vous ne configurez pas cette stratégie et qu’il n’existe aucun paramètre actuel dans le Registre, LSA s’exécute en tant que processus protégé pour toutes les références SKU clientes, compatibles HVCI et installées en mode propre. Cette configuration n’est pas verrouillée par UEFI. Cela peut être substitué si la stratégie est configurée.

Si vous configurez et définissez ce paramètre de stratégie sur « Désactivé », LSA ne s’exécutera pas en tant que processus protégé.

Si vous configurez et définissez ce paramètre de stratégie sur « EnabledWithUEFILock », LSA s’exécute en tant que processus protégé et cette configuration est verrouillée par UEFI.

Si vous configurez et définissez ce paramètre de stratégie sur « EnabledWithoutUEFILock », LSA s’exécute en tant que processus protégé et cette configuration n’est pas verrouillée par UEFI.

Use cases

Runs LSASS as a protected process: non-protected processes can no longer read its memory or inject code into it, which makes in-memory credential theft harder. The list offers “Enabled with UEFI lock” (1), “Enabled without UEFI lock” (2) or Disabled (0); when not configured, LSA is protected by default on clean installs of HVCI-capable client devices, without a UEFI lock.

Main trap: with the UEFI lock on a Secure Boot machine, the state is stored in a UEFI variable, so deleting the registry value no longer rolls it back; Microsoft provides an opt-out tool for that. LSA plug-ins (smart cards, password filters, third-party crypto modules) must carry a Microsoft signature or they will not load: audit mode (CodeIntegrity events 3065 and 3066) helps you find them before you enforce.

Microsoft source: Configuring Additional LSA Protection

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System
Value name
not defined in the ADMX

Enable / disable values: not defined in the ADMX (see the options below).

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Enable

# Enable: LocalSecurityAuthority/ConfigureLsaProtectedProcess
$k = 'HKLM:\Software\Policies\Microsoft\Windows\System'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Configure LSA to run as a protected process
# Possible options:
#   Disabled = 0
#   Enabled with UEFI Lock = 1
#   Enabled without UEFI Lock = 2
Set-ItemProperty -Path $k -Name 'RunAsPPL' -Value 0 -Type DWord

Disable

# Disable: LocalSecurityAuthority/ConfigureLsaProtectedProcess
# No value is written in the "Disabled" state (nothing defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": LocalSecurityAuthority/ConfigureLsaProtectedProcess
$k = 'HKLM:\Software\Policies\Microsoft\Windows\System'
Remove-ItemProperty -Path $k -Name 'RunAsPPL' -ErrorAction SilentlyContinue

Options (1)

LabelControlRegistry valueREG typeConstraints / details
Configure LSA to run as a protected processConfigurer LSA pour qu’il s’exécute en tant que processus protégéConfigureLsaProtectedProcessDrop-down listenumRunAsPPLREG_DWORD
LabelValue
DisabledREG_DWORD = 0
Enabled with UEFI LockREG_DWORD = 1
Enabled without UEFI LockREG_DWORD = 2

Availability

Windows 10

— 22H2— 21H2— 21H1— 20H2— 2004— 1909— 1903— 1809— 1803— 1709— 1703— 1607— 1511— 1507

Windows Server

✓ 2025— 2022— 2016