LSASS Memory Dumping and Protection Bypasses
What You'll Learn
You'll learn how attackers extract credentials from Windows memory by dumping the LSASS process and bypassing modern protections designed to stop this attack.
Understanding LSASS as a Credential Vault
The Local Security Authority Subsystem Service (LSASS) is a Windows process that handles authentication, storing credentials in memory—including plaintext passwords, NTLM hashes, and Kerberos tickets. Think of it as a vault that must stay unlocked while you're logged in, making it a prime target for post-exploitation credential theft.
Memory Dumping Techniques
Once you have administrative access to a Windows system, you can create a memory dump of the LSASS process. Tools like procdump, Task Manager, or Mimikatz can extract this memory snapshot. The dump file contains everything LSASS was processing, including credentials that can be parsed offline.
procdump.exe -ma lsass.exe lsass.dmp
This technique is fundamental to lateral movement after initial compromise, as dumped credentials often unlock access to other systems.
LSA Protection and Evasion
Microsoft introduced LSA Protection (RunAsPPL) to prevent untrusted processes from reading LSASS memory. Protected processes require kernel-level access to interact with them. Attackers bypass this by:
- Loading vulnerable signed drivers that can disable protections
- Exploiting kernel vulnerabilities to elevate privileges
- Using techniques like PPLdump to clone LSASS handles from protected contexts
- Leveraging debugging privileges through alternative interfaces
These bypasses highlight that protection mechanisms add friction but aren't absolute barriers against determined attackers with administrative access.
Key Takeaway: LSASS memory dumping remains a critical post-exploitation technique for credential harvesting, and while LSA Protection raises the bar, kernel-level access or driver exploitation can circumvent these defenses.