LSA Protection Not Enabled
LSASS does not run as a protected process, so any process with administrative rights can read its memory or load code into it to steal credentials.
| Severity | Low |
| CVSS 3.1 | 1.9 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 1.8 CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-522: Insufficiently Protected Credentials |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1003.001 LSASS Memory, T1547.005 Security Support Provider |
| Category | Security Misconfiguration |
Description
The Local Security Authority Subsystem Service (LSASS) holds credential material for signed-in users, such as NT hashes and Kerberos tickets, and loads authentication packages, security support providers and password filters. Without LSA protection it runs as an ordinary process, so any process running with administrative rights and the debug privilege can open it, read its memory or load code into it. This does not give an attacker access on its own, but once they have administrative rights on a host they can dump LSASS with common tools, such as Mimikatz, ProcDump or the MiniDump function of comsvcs.dll, and recover the hashes and Kerberos tickets of users signed in there for pass-the-hash and pass-the-ticket, or install a malicious security support provider to capture passwords at later sign-ins. The value of what can be stolen depends on which accounts sign in to the host.
LSA protection, often called RunAsPPL after its registry value, runs LSASS as a protected process light. Processes that are not protected, including those running as administrator or SYSTEM, can then no longer read its memory or inject code into it, and LSASS only loads plug-ins and drivers that carry a Microsoft signature; an attacker has to load a kernel driver to remove the protection, which is more likely to be blocked or detected but remains possible. The protection is configured with the RunAsPPL value under HKLM\SYSTEM\CurrentControlSet\Control\Lsa, or through Group Policy on versions that include the setting.
The finding is identified from the registry or policy, from the System event log, where WinInit event 12 is recorded at start-up when LSASS runs as a protected process, or on a test when a tool such as Mimikatz can read LSASS memory without first loading a driver.
Remediation
- Enable LSA protection on all supported Windows systems, starting with servers and workstations where privileged accounts sign in, with the Group Policy setting Computer Configuration\Administrative Templates\System\Local Security Authority\Configure LSASS to run as a protected process where it is available, or by setting
RunAsPPLto 1 (REG_DWORD), and restart. - On devices with UEFI and Secure Boot, the value 1 also stores the setting in a UEFI variable, so it cannot be turned off from the registry alone. This resists tampering, but should be planned for before deployment.
- Before enforcing it on systems that run third-party authentication, smart card or security software, use audit mode (
AuditLevelset to 8 underHKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\LSASS.exe) and review Code Integrity events 3065 and 3066 for plug-ins that would fail to load. - Combine it with Credential Guard where supported, which protects hashes and tickets even from code running in the kernel, and with monitoring of access to LSASS.
Confirm the fix after a restart by finding WinInit event 12 in the System log, which records that LSASS started as a protected process, and, where permitted, by checking that an attempt to read its memory from an administrative session is refused.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.