Support
 
Phone Get Quote
 
Support
 
US: +1 888 720 9500
US: +1 888 791 1189
Intl: +1 925 924 9500
Aus: +1 800 631 268
UK: 0800 028 6590
CN: +86 400 660 8680

Direct Inward Dialing: +1 408 916 9892

Get Quote

 

Windows logon auditing: Everything you need to know
in only 10 minutes

Written by Mahidhar Adarsh,

IT security team, ManageEngine

Updated on Sep 2025

  

Summary: Key takeaways on Windows logon auditing

  • A logon happens on the computer a user accesses, while authentication is handled by the computer hosting the user’s account.
  • To record all logon activity, enable security auditing through audit policy or advanced audit policy settings.
  • Among the 69 Event IDs related to logon, the 12 most important are: 4768, 4769, 4771, 4624, 4625, 4647, 4778, 4779, 4800, 4801, 4802, and 4803.
  • Pay close attention to key event fields such as: Logon Type, Failure Code, Client Address, SID, and Account Name.
  • Auditing using native tools like Event Viewer and PowerShell has three main limitations: log aggregation, critical activity detection, and event correlation.

Windows logon auditing

Logon activity needs to be audited to meet various security, operational, and compliance requirements of an IT environment, such as:

  • Detecting unusual and potentially malicious activities like a high volume of logon failures.
  • Tracking the active and idle time spent by users at their workstations.
  • Maintaining a comprehensive audit trail of logons occurring across the domain.

So, it is imperative for administrators to audit logons. However, the process has a steep learning curve. This guide provides concise information to help you configure auditing settings, track key Event IDs, and understand important event fields.

1. Difference between authentication and logon

A logon occurs on the computer to which a user gains access, so it gets recorded in the local computer's security log. Authentication is performed by the system hosting the account. Kerberos and NTLM are the primary authentication protocols used in Windows.

When a local account is used, both logon and authentication happen on the same computer. When a domain account is used, the accessed computer performs the logon while the domain controller handles authentication.

Logon and authentication can be better understood through real-world scenarios.

Scenario 1: Local account logon

Assume a user logs into a standalone computer using a local account. Since the machine is not part of a domain, both authentication and logon occur locally, and events are recorded on that same system.

Local account logon illustration

Scenario 2: Domain account logon

Next, let's assume Bob logs into the computer allotted to him at his workplace, which is a member of a domain. He can log on with either a local user account or a domain user account. In order to access resources on the domain, like a shared folder for example, let's assume he logs on with a domain user account. In this case, the computer can’t perform the authentication, because the domain user account and its password hash aren’t stored locally.

So the computer requests a DC to authenticate and an authentication event is logged in whichever DC handles the request. Once the user is authenticated, the computer proceeds with creating the logon session for the user and a logon event is recorded in its local security log.

Domain account logon illustration

2. Enabling logging via auditing policies

Security auditing must be configured to ensure that events are recorded whenever any logon activity occurs. Security auditing can be configured via audit policy settings or advanced audit policy settings.

Note: It is recommended that advanced audit policy settings are configured on systems running Windows Server 2008 R2 and above.

Audit policy settings can be found under: Computer Configuration → Windows Settings → Security Settings → Local Policies → Audit Policy.

The 2 categories of audit policy settings related to logon are:

Serial number Category Helps track
1 Audit account logon events Authentication of account data
2 Audit logon events Accesses to a computer

Advanced audit policies generate granular control over logged events. Below are the most important subcategories.

S.No Category Subcategory Helps track Event volume Event IDs logged
1 Account Logon Audit Credential Validation NTLM authentication High on DCs, low on member servers and workstations 4774, 4775, 4776, and 4777
2 Audit Kerberos Authentication Service Kerberos authentication ticket granting tickets (TGT) High on DCs, does not get logged on member servers and workstations 4768, 4771, and 4772
3 Audit Kerberos Service Ticket Operations Kerberos service tickets (TGS) High on DCs, does not get logged on member servers and workstations 4769, 4770, and 4773
4 Audit Other Account Logon Events Information not available (might help track events in the Account Logon category that don't fall under any of the other subcategories) Information not available Information not available
5 Logon/Logoff Audit Account Lockout Failed attempt to log on to an account that's locked out Low on DCs, member servers, and workstations 4625
6 Audit Logoff Logon sessions that are terminated High on DCs, member servers and workstations 4634 and 4647
7 Audit Logon User attempts to log on to a computer Medium on DCs and member servers, low on workstations 4624, 4625, 4648, and 4675
8 Audit Other Logon/Logoff Events Remote Desktop session connects and disconnects, workstation lock and unlock events, and other logon-related activity Low on DCs, member servers and workstations 4649, 4778, 4779, 4800, 4801, 4802, 4803, 5378, 5632, and 5633
9 Audit Special Logon Logon by admins or members of special groups Medium on DCs and member servers, low on workstations 4964 and 4672
Note: Event volume is not defined in exact numbers as it varies based on the environment.

3. 10 key points to keep in mind while enabling logging

1. We recommend that you apply audit policies on a per-computer basis rather than per-user.

2. To enable logging on all computers in a domain, link the Group Policy Object (GPO) that contains the auditing settings to the domain. To enable logging on specific computers in a domain, link the GPO that contains the auditing settings to an organizational unit (OU) that contains the specific computers.

3. To configure auditing settings for a domain or an OU, ensure that you are logged in as a member of the Domain Admins group.

4. Choose what category or subcategory of auditing settings to configure. Keep in mind what activities, resources, and users you want to track and the event volume generated by a particular category or subcategory of settings. If you do not plan well, you might miss out on logging critical activity or end up logging too many activities, which will hinder auditors from spotting the suspicious ones.

5. Depending on the event volume generated, ensure that suitable event log size and retention settings are configured to prevent logs from getting overwritten. Event log settings can be found under Computer Configuration > Policies > Windows Settings > Security Settings > Event Log.

6. If you are configuring advanced audit policy settings (recommended), ensure force audit policy subcategory settings is enabled in order to override audit policy settings. To do so, navigate to Local Polices > Security Options, and enable Audit: Force audit policy subcategory settings to override audit policy category settings.

7. For each auditing setting, you can specify whether to log success, log failure, log both, or not log at all.

8. Microsoft's audit policy recommendations for client computers running on Windows 7 and above and servers running on Windows Server 2008 and needing high security requirements are listed in the below table.

Subcategory Recommendations
Audit Credential Validation Log both success and failure
Audit Kerberos Authentication Service Log both success and failure
Audit Kerberos Service Ticket Operations Log both success and failure
Audit Other Account Logon Events Log both success and failure
Audit Account Lockout Log success
Audit Logoff Log success
Audit Logon Log both success and failure
Audit Special Logon Log both success and failure

Note: In addition to the recommendations in the table above, you should:

  • Log both success and failure for the Audit Other Logon/Logoff Events subcategory for only servers.
  • Log both success and failure for the Audit IPsec Main Mode under specific scenarios for both servers and client computers.

9. To view a consolidated list of all auditing settings that will be applied, run the Group Policy Results Wizard found under the Group Policy Management Console.

10. To ensure that auditing settings are applied instantly instead of waiting for the next scheduled refresh, right-click on the domain or OU to which you linked the GPO and click on Group Policy Update.

4. 12 critical Event IDs to keep track of

There are 69 Event IDs related to logon activity, but the 12 most important ones that you should keep track of are:

Serial number Category Event ID Description
1. Account Logon 4768 A Kerberos authentication ticket (TGT) was requested
2. 4769 A Kerberos service ticket was requested
3. 4771 Kerberos pre-authentication failed
4. Logon/Logoff 4624 Successful logon
5. 4625 Failed logon attempt
6. 4647 User-initiated logoff
7. 4778 Remote desktop session reconnected
8. 4779 Remote desktop session disconnected
9. 4800 Workstation locked
10. 4801 Workstation unlocked
11. 4802 Screen saver invoked
12. 4803 Screen saver dismissed

5. Logon types and failure codes

Logon types [7]:

Logon types describe how a logon occurs on a computer. The logon type is one of the event fields of logon Event ID 4624. The logon type helps with detecting potentially malicious activities such as a batch logon (type 4) being used by a member of a domain administrator group.

Of the 12 different logon types, the 6 most common ones are:

Serial number Logon type Title Logon occurs
1 2 Interactive Via a computer's console
2 3 Network When a resource (a shared folder for example) is accessed from a computer on the network
3 4 Batch Job When a scheduled task runs as a specified account
4 5 Service When a service runs as a specified account
5 10 RemoteInteractive Via a remote session
6 11 CachedInteractive Via cached domain credentials, such as when a user logs on to their computer when away from the network
Note: Cached credentials are typically stored for the last 10 users logged on to a computer. When the eleventh user logs on to the computer, the cached credentials of the first user gets overwritten (the default value of 10 can be reset)

(Logon failure) Status codes [8]:

These codes pinpoint the reason for logon failures, they are one of the event fields listed in the logon failure event ID, 4625.

Of the many different codes, the 10 most common ones are:

Serial number Code Logon failed because of
1 0xC0000064 Wrong user name
2 0xC000006A Wrong user password
3 0xC0000234 Locked out user account being used
4 0xC0000072 Disabled user account being used
5 0xC000006F Logon occurring outside authorized hours
6 0xC0000070 Logon occurring from an unauthorized workstation
7 0xC00000193 An expired user account being used
8 0xC0000071 An expired password being used
9 0xC0000133 Time sync missing between clocks on DC and other computer
10 0xC000015b User not being granted the requested logon type at the computer

(Kerberos) Failure Codes [9]:

These codes pinpoint the reason a Kerberos service ticket was denied, they are one of the event fields listed in Kerberos authentication Event ID 4769.

Of the many different codes, the 8 most common are:

Serial number Code A Kerberos service ticket was denied because of
1 0x6 Wrong user name
2 0x7 A DC not being able to find the server’s name
3 0x9 The master key is missing for the client or server
4 0xC A logon restriction in place on a user’s account, like a workstation restriction for example
5 0x12 A disabled, expired, or locked out user account being used
6 0x17 An expired password being used
7 0x18 A wrong user password
8 0x25 A missing time sync between clocks on the DC and the computer

Note: A sudden spike in failed authentication or logon activity due to wrong user name or password can be signs of a possible brute-force attack.

6. A few other important event fields to pay attention to

Only event fields specific to the important Account Logon via Kerberos and Logon/Logoff Event IDs, namely 4768, 4769, 4771, 4624, 4625, and 4647, are covered here.

Event ID Event field Description Helps track
4768, 4769, and 4771 Client Address IP address of computer Logon attempts from outside your internal IP range
4624, and 4625 Source Network Address A DC not being able to find the server’s name
4768 User ID Security identifier (SID) of account Logon from an account that should never be used, such as an expired or disabled one
4771, 4624, 4625, and 4647 Security ID
4768, 4769, 4771, 4624, 4625, and 4647 Account Name Logon name of account (computer account names end with $ character) Logon from accounts that don’t comply with your company's naming conventions (applicable only if you have a specific naming convention in place)
4624 and 4647 Logon ID Hexadecimal value that helps correlate logon Event ID 4624 with logoff initiated Event ID 4647 Duration of a logon session
4624 and 4625 Process Name Full path and the name of the executable Potentially malicious software or software that is not authorized to request logon

7. How to overcome the limitations of native auditing

Event Viewer simply provides a view of event data. It is not designed to help administrators with auditing, as it has a few limitations. This section will shed light on three major limitations of auditing using Event Viewer and how ADAudit Plus helps overcome them.

Limitation 1: DCs, member servers, and workstations log only the logons occurring on them, and security logs do not get replicated between computers. So, an organization's logon audit trail is fragmented across multiple computers. You can leverage Windows Event Forwarding (WEF) to read logs on any computer and forward the events you choose to one or more Windows Event Collector (WEC) servers. However, successful WEF deployment requires expertise.

How ADAudit Plus helps overcome the limitation: ADAudit Plus compiles data from all configured computers across the domain and provides a central repository of logon information.

Limitation 2: Each logon activity creates multiple events. Considering the huge volume of events that get logged, using native tools to spot a critical event is a labor-intensive process that's like looking for a needle in a haystack. You can attach a task to the security log and ask Windows to send you an email notification whenever a particular Event ID is generated.

However, Windows can't raise red flags. For example, Windows can send you an email every time Event ID 4776 is generated, but it will not be able to notify you about logon attempts from unauthorized computers, attempts occurring outside business hours, or attempts from expired accounts.

How ADAudit Plus helps overcome the limitation: ADAudit Plus sorts through large reservoirs of event data and instantly pulls the information you are looking for. The solution lets you define thresholds based on volume, time, and other criteria to detect critical activities such as the ones discussed above (logon attempts from an unauthorized computer, attempts occurring outside business hours, or attempts from an expired account). You can also choose to get instantly notified via email and SMS of critical activities.

Limitation 3: In some cases, Windows provides severely limited information, which impedes the correlation necessary to get the full picture. For example, to calculate the duration of a logon session, logon Event ID 4624 needs to be correlated with the logoff-initiated Event ID 4647 using the Logon ID event field.

How ADAudit Plus helps overcome the limitation: ADAudit Plus processes logs and establishes a connection between them to provide you with the full picture. For example, its User Work Hours report correlates multiple events related to user logon and log off times, workstation lock and unlock times, and screen saver start and stop times to provide you with information on the active and idle time spent by users at their workstations.

Other highlights of ADAudit Plus: ADAudit Plus provides several other critical functions to help you easily meet your security, operational, and compliance requirements.

With ADAudit Plus, you can:

  • Track suspicious activities such as a spike in logon failures, users logged on to multiple computers, authentication occurring via NTLM protocol, and more.
  • Detect attacks like kerberoasting, Golden Ticket, pass-the-ticket, brute-force password, and more.
  • Leverage user behavior analytics (UBA) to establish activity patterns and spot subtle anomalies such as an unusual time of logon for a particular user.
  • Execute scripts to automate response actions, like shutting down a device or disabling an account.
  • Monitor employee attendance and actual work hours.
  • Automate the generation of logon audit trails to pass compliance audits such as SOX, HIPAA, PCI DSS, GLBA, FISMA, the GDPR, and ISO 27001.

What's more, you can go from downloading ADAudit Plus to receiving logon notifications and reports in an hour.

Learn more about how ADAudit Plus can help you audit:

8. FAQ

What's the difference between logon and authentication?

Where do I enable auditing for logon activity?

Using Group Policy, advanced audit policy settings can be found under: Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Audit Policy.

For more information, see Section 2.

Should I use basic or advanced audit policies?

Use advanced audit policy settings for Windows Server 2008 R2/Windows 7 and above. Advanced policies reduce noise and let you target specific events.

For more information, see Section 2.

Which advanced audit subcategories matter most for logons?

Of the 15 subcategories of advanced audit policy settings, the nine most important for logon are: Credential Validation, Kerberos Authentication Service, Kerberos Service Ticket Operations, Other Account Logon Events, Account Lockout, Logoff, Logon, Other Logon/Logoff Events, and Special Logon.

For more information, see Section 2.

How do I roll auditing out to the right scope?

Link the GPO to the domain to cover all computers or to specific OUs to target subsets. Ensure you have the required privileges to configure it.

For more information, see Section 3.

Which logon and authentication Event IDs are most important?

Of the 69 events related to account logon and logon/logoff, the 12 most important ones are: 4768, 4769, 4771, 4624, 4625, 4647, 4778, 4779, 4800, 4801, 4802, and 4803.

For more information, see Section 4.

What do Logon Types tell me?

They describe how the logon occurred, for example: 2 (Interactive), 3 (Network), 4 (Batch), 5 (Service), 10 (RemoteInteractive), and 11 (CachedInteractive).

For more information, see Section 5.

How can I triage failed logons quickly?

Use status codes on Event ID 4625. Common codes include 0xC000006A (wrong password), 0xC0000234 (account locked), 0xC0000071 (expired password), and 0xC0000133 (time sync issue).

For more information, see Section 5.

Pay extra attention to these event fields:

  • Client Address/Source Network Address for outside IP range activity
  • Security ID (SID)/User ID for forbidden or expired accounts
  • Account Name for naming-policy violations
  • Logon ID to correlate 4624 with 4647 for session duration
  • Process Name to spot unapproved software requesting logons

For more information, see Section 6.

Why can't I use Event Viewer for auditing?

Event Viewer can't be used for auditing because of limitations related to log aggregation, critical activity detection, and event correlation.

For more information, see Section 7.

What helps overcome native auditing limits?

For comprehensive auditing, you can use Windows Event Forwarding plus centralized analysis, or a solution like ADAudit Plus that aggregates, thresholds, alerts, and correlates events such as mapping 4624 to 4647 to compute session duration.

For more information, see Section 7.

Where can I learn more or try the tool used in this guide?

Here are some links to get you started with ADAudit Plus:

About ManageEngine ADAudit Plus

Named a Gartner® Peer Insights™ Customers' Choice for SIEM for four years in a row, ADAudit Plus is a unified tool for auditing, security, and compliance across Active Directory, Microsoft Entra ID, file servers, Windows Servers, and workstations.

Here are the top-five things you can do with ADAudit Plus:

  1. Get instant notifications of changes in your Active Directory and Microsoft Entra ID.
  2. Monitor user logons and troubleshoot account lockouts.
  3. Audit file activities across Windows, NetApp, EMC, and other NAS file systems.
  4. Mitigate attacks using Attack Surface Analyzer, UBA, and response automation.
  5. Generate audit-ready compliance reports for SOX, the GDPR, and other IT mandates.

ADAudit Plus is licensed on a per-server basis, and pricing starts at $595 annually.

Thank you for your interest.

We have mailed you the e-book. If you do not see it shortly, please check your spam folder.

Fill your details and Get a you e-book copy

  •  
  •  
  •  
  • By clicking 'Download now' you agree to processing of personal data according to the Privacy Policy.
 

ADAudit Plus Trusted By