Open in the explorer

Allow Custom SSPs and APs to be loaded into LSASS

Autoriser le chargement des SSP et des adresses IP personnalisées dans LSASS

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/AllowCustomSSPsAPs

Explanation

This policy controls the configuration under which LSASS loads custom SSPs and APs.

If you enable this setting or do not configure it, LSA allows custom SSPs and APs to be loaded.

If you disable this setting, LSA does not load custom SSPs and APs.

French text from Windows 11 26H2

Cette stratégie contrôle la configuration sous laquelle LSASS charge des SPS et des adresses IP personnalisées.

Si vous activez ce paramètre ou si vous ne le configurez pas, LSA autorise le chargement des fournisseurs de service personnalisés et des adresses IP personnalisées.

Si vous désactivez ce paramètre, LSA ne charge pas les SPS et les adresses IP personnalisées.

Use cases

Controls loading of custom security (SSP) and authentication (AP) providers into LSASS. Disabling it reduces attack surface, since modules injected into LSASS are a classic credential-theft technique.

Pair it with LSA protection, which only accepts Microsoft-signed plug-ins anyway; first check that your third-party authentication products (smart card, SSO) do not rely on it.

Microsoft source: Configure added LSA protection

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System
Value name
AllowCustomSSPsAPs
StateValue written
EnabledREG_DWORD = 1
DisabledREG_DWORD = 0

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/AllowCustomSSPsAPs
$k = 'HKLM:\Software\Policies\Microsoft\Windows\System'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'AllowCustomSSPsAPs' -Value 1 -Type DWord

Disable

# Disable: LocalSecurityAuthority/AllowCustomSSPsAPs
$k = 'HKLM:\Software\Policies\Microsoft\Windows\System'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'AllowCustomSSPsAPs' -Value 0 -Type DWord

Revert to "Not configured"

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

Availability

Windows 10

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

Windows Server

✓ 2025— 2022— 2016