Windows 10: Excessive number of security credential reads when computer goes to idle lsass.exe, event...

PaulMertens · Oct 19, 2021

Hi, Whenever my home server is not in use, security processes continuously consume disproportionate CPU resources. Using Event Viewer, I notice excessive logging of several events. Any information on how to solve either of the following problems would be greatly appreciated!Problem 1 Event 5379, logged by lsass.exeThis event is logged only for the current user, many hundreds of times per second. Description: "This event occurs when a user performs a read operation on stored credentials in Credential Manager."Problem 2 Events 4624 and 4672, logged by services.exeThese events are logged

:)

IgnatiusBenny · Oct 19, 2021

Excessive Security Log Events - Event ID 5379 - Windows 10

I have been experiencing Windows Application crashes on my 3 month old Windows 10 install. While troubleshooting, I noticed that there 50+ security events each minute in the Event Viewer under Windows Logs > Security.

Is this normal?

The majority are Audit Success Messages with the Event ID 5379. There are approximately 50 of these identical messages every minute. Thanks for any insight on this.

See below for typical Message:

Credential Manager credentials were read.

Subject:

Security ID: DESKTOP\*****

Account Name: *****

Account Domain: DESKTOP

Logon ID: 0x354889

Read Operation: Enumerate Credentials

This event occurs when a user performs a read operation on stored credentials in Credential Manager.
Click to expand...

i had ex[eriences like that last night - my laptop so slowly

Brink · Oct 19, 2021

Credential Guard lab companion

If you have heard about Credential Guard in Windows Server 2016 (and in Windows 10), but do not have an environment to try it out, here is a lab environment we built for you to play.

Lab access

The link will lead you to a sign up page, after that, you will see the following labs listed for Windows Server 2016:

Windows Server 2016 labs

There are 3 exercises in the “Implementing Breach Resistance Security in Windows Server 2016”:

Credential Guard

Remote Credential Guard

Device Guard

This blogpost will walk you through the Credential Guard lab details.

After click on the link of Breach Resistance lab, you be required to sign in and then you can launch the lab:

Sign-in

Launch page

It takes a few minutes to create the VMs, and once it has done, you will see the following machines prepared:

Initialize

DC: domain controller, which is not used for this exercise.

SRV01 and SRV02: both are Windows Server 2016, and used for the lab exercise.

Lab exercise – Explained

The steps are listed in the Content section:

Content

This lab is structured to cover the following in sequence:

Understand how attackers can use the hash in memory to gain access to domain controllers

Configure Credential Guard

Verify the hash in memory is protected using Credential Guard

You can follow the steps listed under the content section to complete the lab, the intent of the blog, is to break the procedures into groups, to help you understand the exercise better.

Prep the hash

Lsass.exe is the process which handles user logon, it stores the user credential information in its memory. The memory is cleared when the machine starts up. In this lab environment, all the virtual machines start at the time lab launches, when you logon to the machine, you will only have the logon user credential information in memory. In order to demonstrate an attacker gaining user access using other account’s hash, the first part of the lab is to simulate a server which has been running for a while, different users had remotely or locally connected to it, therefore, lsass memory stored many different user credential information.
This is accomplished by step 1-8.

Retrieving credential hash

Mimikatz is a popular tool for retrieving lsass memory information. The tool has been copied to the lab machines, step 9-13 walk you through the process of dumping lsass memory using Mimikatz.

Pass the Hash

Pass the hash is a hacking technique that allows an attacker to authenticate by using the underlying NTLM, instead of specifying the user password. In step 14 to 24, you will extract LabAdmin hash from lsass using Mimikatz, and use the hash to open a PowerShell console, and perform a couple of operations using the LabAdmin privilege:

Add a user to the domain admin group

Open remote PowerShell connection to a domain controller

Both operations could not be performed by the logon user. But using the hash of the LabAdmin, an attacker will be able to do it using the information retrieve from Lsass memory.

Configure and verify Credential Guard

Step 25 to 36 illustrate the steps to configure credential guard, then verify its status using msinfo32.exe and PowerShell.

Step 37 to 43 goes further to use Mimikatz to show the hash in Lsass is now encrypted using Credential Guard.

More info

The exercise illustrated the benefit of Credential Guard in Windows Server 2016 as well as Windows 10. For more information, you can find here.
Click to expand...

Source: Credential Guard lab companion Datacenter and Private Cloud Security Blog

See also:

Enable or Disable Credential Guard in Windows 10 Windows 10 Security System Tutorials

Verify if Credential Guard is Enabled or Disabled in Windows 10 Windows 10 Security System Tutorials

TD47 · Oct 19, 2021

Excessive Security Log Events - Event ID 5379 - Windows 10

@David Salmon - even fresh installs will have 5379 events. It is a NORMAL "info" event, just a standard audit event, for user activity that uses credentials. It is NOT signifying any problem - it is just annoying and a bit excessive for normal home systems.

Windows 10: Excessive number of security credential reads when computer goes to idle lsass.exe, event...

Excessive number of security credential reads when computer goes to idle lsass.exe, event...

Excessive number of security credential reads when computer goes to idle lsass.exe, event...

Excessive number of security credential reads when computer goes to idle lsass.exe, event...

Excessive number of security credential reads when computer goes to idle lsass.exe, event... - Similar Threads - Excessive number security

Excessive Events in Event Viewer on computer

Excessive Events in Event Viewer on computer

Excessive Events in Event Viewer on computer

Blocking credential stealing from lsass VS letting lsass free to operate?

Blocking credential stealing from lsass VS letting lsass free to operate?

Lsass using excess Memory

Lsass using excess Memory

Excessive Number of Processes

Excessive Security Log Events - Event ID 5379 - Windows 10