Local Security Authority is the Windows system that manages who can log in and what they're allowed to do
Local Security Authority, or LSA, is a Windows background process that runs constantly on your computer. It handles login verification — checking your password when you start up — and enforces permission rules that decide which user accounts can access which files and programs. You don't interact with it directly. It works silently, and when it works well, you never notice it exists.
The process runs under the name lsass.exe in your Task Manager. If you see it using a lot of CPU or memory, or if it keeps crashing, your computer will slow down noticeably because Windows can't verify permissions or manage user sessions properly. Understanding what LSA does helps you recognize when something is wrong with it — and when something else is pretending to be it.
Key Takeaways
- Local Security Authority (lsass.exe) verifies your password at login and enforces file and folder permissions throughout your session.
- If lsass.exe uses excessive CPU or memory, or crashes repeatedly, your computer will slow down because Windows can't manage user access properly.
- Malware sometimes disguises itself as lsass.exe to hide in your system, so checking the file location and publisher in Task Manager can reveal fakes.
- You cannot disable Local Security Authority without breaking Windows, but you can restart it through Services if it becomes unresponsive.
How Local Security Authority handles login and permissions
When you type your password at the Windows login screen, LSA receives it and checks it against the stored credentials on your computer. If the password matches, LSA creates a security token — a digital record that says "this person is who they claim to be." That token stays active for your entire session and travels with every action you take.
After login, LSA enforces the permission rules you set on files and folders. When you try to open a document, LSA checks whether your user account has read permission. When a program tries to write to a system folder, LSA blocks it if your account doesn't have write permission. This happens thousands of times per session, usually in milliseconds, so you don't see it happening.
LSA also manages what happens when you lock your computer or switch user accounts. It suspends your session's permissions and creates a new security context for the next user. If LSA fails during this handoff, you may find yourself unable to log in or stuck in a frozen session.
Why Local Security Authority problems slow your computer down
When lsass.exe uses 20%, 30%, or more of your CPU, Windows is spending most of its processing power on security checks instead of running your programs. This happens most often when LSA is stuck in a loop trying to verify permissions on a corrupted file, or when it's processing an unusually large number of login attempts in a short time.
High memory usage by lsass.exe is less common but more serious. It usually means LSA is caching security information that it can't clear — often because a network connection is broken or a domain server is unreachable. Your computer keeps trying to reach that server, and LSA keeps holding the failed attempt in memory.
A crashing lsass.exe is the worst scenario. Each time it crashes, Windows restarts it automatically, but during the restart, no user can log in and no permissions are enforced. If it crashes repeatedly, you may see a blue screen or find yourself locked out of your own computer.
How to check if lsass.exe is legitimate or malware
Open Task Manager by pressing Ctrl+Shift+Esc. Find "Local Security Authority Process" in the list. Right-click it and select "Open file location." A legitimate lsass.exe file is located at C:\Windows\System32\lsass.exe. If the file opens from any other folder — especially Desktop, Downloads, or AppData — it is malware pretending to be the real process.
Check the publisher as well. Right-click lsass.exe in Task Manager and select "Properties." On the Details tab, look for "File description" — it should say "Local Security Authority Process" and the publisher should be blank or say "Microsoft Corporation." If it says anything else, the file is fake.
You can also check the file's digital signature. In the Properties window, go to the Digital Signatures tab. A real lsass.exe has a valid signature from Microsoft. If there is no signature, or the signature is invalid, the file is not the genuine Windows process.
What to do if Local Security Authority is using too much CPU or memory
First, restart your computer. Many LSA problems are temporary and clear themselves on reboot. If the problem returns, check whether you recently installed new software or connected to a new network. Both can cause LSA to work harder than usual while it processes new permissions or domain information.
If restarting doesn't help, try restarting just the LSA service. Press Windows+R, type services.msc, and press Enter. Find "Local Security Authority" in the list, right-click it, and select "Restart." This stops and restarts the process without rebooting your whole computer. If LSA crashes again within minutes, you likely have a deeper problem that requires professional help.
Check your antivirus or security software. Sometimes security tools scan system processes aggressively and cause LSA to spike in CPU usage. Temporarily disable real-time scanning to see if the problem stops. If it does, add lsass.exe to your antivirus exclusion list so the security tool stops monitoring it.
When Local Security Authority problems mean you need help
If lsass.exe keeps crashing and you see blue screens or repeated login failures, your Windows installation may be corrupted. This is beyond what restarting or checking settings can fix. You will need to either repair Windows using installation media or restore your computer from a backup.
If you see a fake lsass.exe file on your computer, you have malware. Delete the fake file and run a full system scan with your antivirus software. If your antivirus doesn't find anything after a full scan, consider running a second opinion scanner like Malwarebytes to catch what the first tool missed.
If LSA problems started after you connected to a corporate network or domain, the issue may be on the network side. Contact your IT department or network administrator — they can check whether the domain server is reachable and whether your account permissions are set correctly.
Frequently Asked Questions
Can I disable Local Security Authority to speed up my computer?
No. LSA is required for Windows to function. If you disable it, you won't be able to log in, and your computer will become unusable. Disabling it is not a solution to performance problems — it's a way to break your system.
Why does lsass.exe spike in CPU usage when I first log in?
LSA is processing your login credentials, loading your user profile, and explore all the permission rules that explore to your account. This is normal and usually lasts only a few seconds. If it lasts longer than a minute, something is wrong with your profile or permissions.
Is it safe to end the lsass.exe process in Task Manager?
Technically yes, but you shouldn't. Ending it will log you out when ready and may corrupt your session. Windows will restart it automatically, but you'll lose any unsaved work. Use the Services tool to restart LSA properly instead.
What does "Local Security Authority Subsystem" mean?
That's the full name for the same process. You may see it called LSA, lsass.exe, Local Security Authority Process, or Local Security Authority Subsystem in different places. They all refer to the same Windows component.
Can a virus hide inside lsass.exe?
Malware can inject code into the real lsass.exe process, but it cannot hide inside the file itself — the file is protected by Windows. What malware does instead is create a fake lsass.exe in a different folder and run that. This is why checking the file location is your best defense.