Related to the lsass.exe process on Windows

About windows lsass.exe process Author: eygle Source: http://blog.eygle.com date: December 26,200 4

«Install cronolog and format Apache Log Files | blog homepage | configure AWStats and Apache log analysis tools»

Today, we can see people asking about the lsass.exe process, turning over something and recording something here.

LSASS-lsass.exe-Process Information
Process file: LSASS or lsass.exe
Process name: local security permission Service
Description: The local security permission Service controls the Windows security mechanism.
Common Errors: N/
Whether the process is a system process: Yes

The process is a system process and cannot be terminated in the task manager. Remember to kill the process on the command line before, which may cause the system blue screen (unconfirmed ).

Microsoft's description is as follows:

Lsass.exe-you cannot end this process from task manager.
This is the local security authentication server, and it generates the process responsible for authenticating users for the Winlogon service. this process is already med by using authentication packages such as the default MSGINA. DLL. if authentication is successful, LSASS generates the user's access token, which is used to launch the initial shell. other processes that the user initiates inherit this token.

Link

It means:
This is a local security authorization service, and it will generate a process for authorized users using the Winlogon service. This process is executed by using an authorized package, such as the default MSGINA. dll. If the authorization succeeds, LSASS will generate the user's access token. Do not use the start initial shell as the token. Other user-initiated processes will inherit this token.

However, proper concerns are necessary. Some known viruses are related to LSASS.
First, the soft environment lsass.exe is located in C:/Windows/system32/lsass.exe

We should be clear about the dynamic link library required for running LSASS normally:

C:/>tlist 720 720 lsass.exe CWD: C:/WINDOWS/system32/ CmdLine: C:/WINDOWS/system32/lsass.exe VirtualSize: 43208 KB PeakVirtualSize: 49040 KB WorkingSetSize: 1360 KB PeakWorkingSetSize: 10640 KB NumberOfThreads: 19 732 Win32StartAddr:0x74497f07 LastErr:0x00000000 State:Waiting 736 Win32StartAddr:0x7c94798d LastErr:0x00000000 State:Waiting 740 Win32StartAddr:0x7c930760 LastErr:0x00000000 State:Waiting 744 Win32StartAddr:0x7c949fae LastErr:0x00000000 State:Waiting 748 Win32StartAddr:0x0000028e LastErr:0x00000000 State:Waiting 764 Win32StartAddr:0x7c930aca LastErr:0x00000000 State:Waiting 792 Win32StartAddr:0x00000000 LastErr:0x00000000 State:Waiting 800 Win32StartAddr:0x00040d64 LastErr:0x00000000 State:Waiting 812 Win32StartAddr:0x74488c23 LastErr:0x00000000 State:Waiting 1700 Win32StartAddr:0x74488c23 LastErr:0x00000000 State:Waiting 212 Win32StartAddr:0x77dbb479 LastErr:0x00000000 State:Waiting 364 Win32StartAddr:0x77c0a341 LastErr:0x000003e5 State:Waiting 376 Win32StartAddr:0x77c0a341 LastErr:0x00000000 State:Waiting 380 Win32StartAddr:0x77c0a341 LastErr:0x00000000 State:Waiting 3056 Win32StartAddr:0x759d8831 LastErr:0x00000000 State:Waiting 1048 Win32StartAddr:0x77e56bf0 LastErr:0x0000006d State:Waiting 2628 Win32StartAddr:0x00000000 LastErr:0x000003f0 State:Waiting 3204 Win32StartAddr:0x00000000 LastErr:0x00000000 State:Waiting 3032 Win32StartAddr:0x77e56bf0 LastErr:0x00000000 State:Waiting 5.1.2600.2180 shp 0x01000000 lsass.exe 5.1.2600.2180 shp 0x7c920000 ntdll.dll 5.1.2600.2180 shp 0x7c800000 kernel32.dll 5.1.2600.2180 shp 0x77da0000 ADVAPI32.dll 5.1.2600.2180 shp 0x77e50000 RPCRT4.dll 5.1.2600.2525 shp 0x74480000 LSASRV.dll 5.1.2600.2180 shp 0x71a90000 MPR.dll 5.1.2600.2180 shp 0x77d10000 USER32.dll 5.1.2600.2180 shp 0x77ef0000 GDI32.dll 5.1.2600.2180 shp 0x76db0000 MSASN1.dll 7.0.2600.2180 shp 0x77be0000 msvcrt.dll 5.1.2600.2180 shp 0x5fdd0000 NETAPI32.dll 5.1.2600.2180 shp 0x76770000 NTDSAPI.dll 5.1.2600.2180 shp 0x76ef0000 DNSAPI.dll 5.1.2600.2180 shp 0x71a20000 WS2_32.dll 5.1.2600.2180 shp 0x71a10000 WS2HELP.dll 5.1.2600.2180 shp 0x76f30000 WLDAP32.dll 5.1.2600.2180 shp 0x77fc0000 Secur32.dll 5.1.2600.2180 shp 0x71b70000 SAMLIB.dll 5.1.2600.2180 shp 0x743a0000 SAMSRV.dll 5.1.2600.2180 shp 0x76760000 cryptdll.dll 5.1.2600.2180 shp 0x5cc30000 ShimEng.dll 0x58fb0000 AcGenral.DLL 5.1.2600.2180 shp 0x76b10000 WINMM.dll 5.1.2600.2180 shp 0x76990000 ole32.dll 5.1.2600.2180 shp 0x770f0000 OLEAUT32.dll 5.1.2600.2180 shp 0x77bb0000 MSACM32.dll 5.1.2600.2180 shp 0x77bd0000 VERSION.dll 6.0.2900.2180 shp 0x773a0000 SHELL32.dll 6.0.2900.2180 shp 0x77f40000 SHLWAPI.dll 5.1.2600.2180 shp 0x759d0000 USERENV.dll 6.0.2900.2180 shp 0x5adc0000 UxTheme.dll 5.1.2600.2180 shp 0x76300000 IMM32.DLL 5.1.2600.2180 shp 0x62c20000 LPK.DLL 1.420.2600.2180 sh 0x73fa0000 USP10.dll 5.82.2900.2180 shp 0x77180000 comctl32.dll 5.82.2900.2180 shp 0x5d170000 comctl32.dll 5.1.2600.2180 shp 0x20000000 msprivs.dll 5.1.2600.2180 shp 0x71c70000 kerberos.dll 5.1.2600.2180 shp 0x77c40000 msv1_0.dll 5.1.2600.2180 shp 0x76d30000 iphlpapi.dll 5.1.2600.2180 shp 0x74410000 netlogon.dll 5.1.2600.2180 shp 0x76790000 w32time.dll 6.0.8168.0 shp 0x75ff0000 MSVCP60.dll 5.1.2600.2180 shp 0x767c0000 schannel.dll 5.131.2600.2180 sh 0x765e0000 CRYPT32.dll 5.1.2600.2180 shp 0x742e0000 wdigest.dll 5.1.2600.2161 shp 0x0ffd0000 rsaenh.dll 5.1.2600.2180 shp 0x74370000 scecli.dll 5.1.2600.2180 shp 0x76060000 SETUPAPI.dll 5.1.2600.2180 shp 0x74340000 ipsecsvc.dll 5.1.2600.2180 shp 0x77fe0000 AUTHZ.dll 5.1.2600.2180 shp 0x73ed0000 oakley.DLL 5.1.2600.2180 shp 0x742d0000 WINIPSEC.DLL 5.1.2600.2180 shp 0x74300000 pstorsvc.dll 0x43000000 GoogleDesktopNetwork1.dll 5.1.2600.2180 shp 0x719c0000 mswsock.dll 5.1.2600.2180 shp 0x60fd0000 hnetcfg.dll 5.1.2600.2180 shp 0x71a00000 wshtcpip.dll 5.1.2600.2180 shp 0x74320000 psbase.dll 5.1.2600.2133 shp 0x68100000 dssenh.dll

As you can see, Google's desktop search also needs to be registered here. This process is required for permission control.
Some software verification and updates or verification of registration information, will use port 500 communication (Internet Key Exchange (IKE)-Internet Key Exchange port), sometimes may be reported as a virus or Trojan.

I usually think that as long as we have a proper understanding of Windows processes and do not rely on anti-virus tools, we can still be sensitive to abnormal processes or abnormal DLL, so as to find suspicious processes and find out the problem.
Tlist, a simple tool, once helped me discover a few viruses that cannot be identified in time by anti-virus software.

Currently, LSASS-related viruses are known to be:
W32.hllw. lovgate. c @ MM-Symantec Corporation
W32.mydoom. l @ MM-Symantec Corporation
W32.nimos. worm-Symantec Corporation
W32.sasser. E. worm (lsasss.exe)-McAfee

Therefore, you should pay attention to this process.