Active Directory auditing is a vitally important part of Active Directory security and operations. A common problem that Active Directory administrators face is how to identify the source of frequent account lockouts. If user accounts are getting locked out frequently for any reason, it may result in downtime, and it can often be a time-consuming and frustrating process to get the AD account re-enabled.
In this article, we will look at two ways to find the source of account lockout in AD. The first is, finding the Event ID 4740 in Event Log Viewer and the second way is to use Lepide Auditor for Active Directory.
Why AD Account Gets Locked Out Frequently – Common Causes
Below are some of the common causes of frequent AD account lockouts:
- Mapped drives using old credentials
- Systems using old cached credentials
- Applications using old credentials
- Windows Services using expired credentials
- Scheduled Tasks
Read more about common account lockout causes in detail.
Steps to Find Out the AD Account Lockout Source
Follow the steps below to track locked out accounts and find the source of Active Directory account lockouts. If you already know the lockout account in question, you can start directly from step 5 (to track the source).
Step 1 – Search for the DC having the PDC Emulator Role
The DC (Domain Controller) with the PDC (Primary Domain Controller) emulator role will capture event ID 4740. If you have only one DC then you can skip this step.
Get-AdDomain – Running this cmdlet will search for the domain controller having the role of a PDC emulator.
Step 2 – Look for the Account Lockout Event ID 4740
Open the event log viewer of the domain controller. Go to the security logs, and search for Event ID 4740.
Step 3 – Put Appropriate Filters
There are suitable filters to generate a more customized report. For example, you can search for a lockout that occurred in the last hour and find the recent lockout source of a particular user.
Step 4 – Find Out the Locked Account Whose Information is Require
Click on the Find button in the Actions pane to look for the User whose account has been locked out.
Step 5 – Open the Event Report, to Find the Account Lockout Source
Here you can find the name of the user account in the Account Name, and the source of the lockout location as well in the Caller Computer Name field.
Steps to Find Out the Cause of Account Lockout
To perform a more detailed analysis of the cause of this lockout, carry out the following actions on the DC:
- In the Event Viewer, filter the current view to look for the Event ID 4625, which is logged when there is a failed logon.
- On the right pane of the Event Viewer window, click Find, enter the user’s name that was locked out, and click Find Next.
- Look for an event logged after the account lockout time and view its properties.
- Scroll down to Caller Process Name. This will show you the location of the process that possibly caused the lockout.
How Lepide Auditor Troubleshoots Account Lockouts
Lepide Active Directory Auditor generates Account Lockout Reports where complete information about the event is displayed in a single row. When you right-click on any event, the context menu will give you the following options; “Unlock”, “Reset Password” and “Investigate”.
To run the Account Lockout Report:
- From the States & Behavior screen, expand the Active Directory component and click on Account Lockout Report
- Select a date range and click Generate Report
- The report is generated and can be grouped, filtered, saved and exported
Unlock Account
Click on this option to unlock the chosen user account. Once done, it shows the following message.
Reset Password
If you want to reset the users’ password, click on the “Reset Password” option. Enter the new password and then confirm it. Select the “User must change password at the next logon” option to force the user to change the password on the next logon.
Investigate
In order to investigate how the user account was locked out click on the “Investigate” option in the context menu. After clicking on the “Investigate” button, “Lockout Investigator” window opens up. In this window, you can click on the “Generate Report” button to generate the report to view the reason behind the account lockout.
The Security Implications of Account Lockouts
Account lockouts are generally a harmless and completely common occurrence. Users forget their passwords frequently. A lot is often made of the operational effects of account lockouts, including downtime, disruption, and consumption of IT resources. However, account lockouts can be a symptom of something more sinister.
Often, if there are a large number of account lockouts over a very small period of time it can be an indication of a brute force attack, where attackers might be using password-spreading techniques to gain access to resources.
So, account lockouts are not to be brushed off completely. And it’s worth making sure that you have a way of knowing whether the account lockouts you’re seeing are normal everyday behavior for your employees or the symptom of something darker at work.
With Lepide, you can learn what the normal behavior for your employees looks like, and receive real-time alerts whenever behavior deviates from this norm. You can also deploy any number of pre-defined threat models to automatically detect and react to threats such as brute force attacks, or password spraying.
To learn more about the Lepide Active Directory Auditor and how it can help you get control of your account lockouts, start your free trial below:
