Event ID 4624
An account was successfully logged on
An account was successfully logged on.
Subject:
Security ID: %1
Account Name: %2
Account Domain: %3
Logon ID: %4
Logon Information:
Logon Type: %9
Restricted Admin Mode: %22 [Windows 10+]
Virtual Account: %25 [Windows 10+]
Elevated Token: %27 [Windows 10+]
Impersonation Level: %21 [Windows 8/2012+]
New Logon:
Security ID: %5
Account Name: %6
Account Domain: %7
Logon ID: %8
Linked Logon ID: %26 [Windows 10+]
Network Account Name: %23 [Windows 10+]
Network Account Domain: %24 [Windows 10+]
Logon GUID: %13
Process Information:
Process ID: %17
Process Name: %18
Network Information:
Workstation Name: %12
Source Network Address: %19
Source Port: %20
Detailed Authentication Information:
Logon Process: %10
Authentication Package: %11
Transited Services: %14
Package Name (NTLM only): %15
Key Length: %16
This event is generated when a logon session is created. It is generated on the computer that was accessed.
The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The impersonation level field indicates the extent to which a process in the logon session can impersonate.
The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
This event generates when a logon session is created (on destination machine). It generates on the computer that was accessed, where the session was created.
Auditing:
Conditional
Audit on servers and workstations, on domain controllers if possible.
Volume:
Low
Medium
High
Very High
Volume may be high on busy domain controllers.
Security recommendations
CJIS 5.4.1.1.1
ISO 27001:2013 A.12.4.3
HIPAA: 164.308 (a)(5)(ii)(C)
NIST SP 800-53: AC-2
NIST 800-171: 3.1.1
CMMC v2 L1: AC.L2-3.1.16
Name |
Field |
Insertion String |
OS |
Example |
|
|
Security ID |
SubjectUserSid |
%1 |
Any |
S-1-5-18
|
|
Account Name |
SubjectUserName |
%2 |
Any |
ComputerName
|
|
Account Domain |
SubjectDomainName |
%3 |
Any |
WORKGROUP
|
|
Logon ID |
SubjectLogonId |
%4 |
Any |
0x3e7
|
|
Security ID |
TargetUserSid |
%5 |
Any |
THEDOMAIN\JohnDoe
|
|
Account Name |
TargetUserName |
%6 |
Any |
JohnDoe
|
|
Account Domain |
TargetDomainName |
%7 |
Any |
THEDOMAIN
|
|
Logon ID |
TargetLogonId |
%8 |
Any |
0x3e7
|
|
Logon Type |
LogonType |
%9 |
Any |
View Codes
|
|
Logon Process |
LogonProcessName |
%10 |
Any |
ProcessName
|
|
Authentication Package |
AuthenticationPackageName |
%11 |
Any |
View Codes
|
|
Workstation Name |
WorkstationName |
%12 |
Any |
ComputerName
|
|
Logon GUID |
LogonGuid |
%13 |
Any |
{00000000-0000-0000-0000-000000000000}
|
|
Transited Services |
TransmittedServices |
%14 |
Any |
-
|
|
Package Name (NTLM only) |
LmPackageName |
%15 |
Any |
NTLMv2
|
|
Key Length |
KeyLength |
%16 |
Any |
0
|
|
Process ID |
ProcessId |
%17 |
Any |
0x1f8
|
|
Process Name |
ProcessName |
%18 |
Any |
C:\Windows\System32\services.exe
|
|
Source Network Address |
IpAddress |
%19 |
Any |
192.168.0.2
|
|
Source Port |
IpPort |
%20 |
Any |
44555
|
|
Impersonation Level |
ImpersonationLevel |
%21 |
8/2012+ |
View Codes
|
|
Restricted Admin Mode |
RestrictedAdminMode |
%22 |
10+ |
Yes
|
|
Network Account Name |
TargetOutboundUserName |
%23 |
10+ |
-
|
|
Network Account Domain |
TargetOutboundDomainName |
%24 |
10+ |
-
|
|
Virtual Account |
VirtualAccount |
%25 |
10+ |
No
|
|
Linked Logon ID |
TargetLinkedLogonId |
%26 |
10+ |
0x0
|
|
Elevated Token |
ElevatedToken |
%27 |
10+ |
%%1842
|
SID of account that reported information about successful logon or invokes it. Event Viewer automatically tries to resolve SIDs and show the account name. If the SID cannot be resolved, you will see the source data in the event.
The name of the account that reported information about successful logon.
Subject’s domain or computer name. Formats vary, and include the following:
Domain NETBIOS name example: DOMAIN
Lowercase full domain name: domain.local
Uppercase full domain name: DOMAIN.LOCAL
For some well-known security principals, such as LOCAL SERVICE or ANONYMOUS LOGON, the value of this field is “NT AUTHORITY”.
For local user accounts, this field will contain the name of the computer or device that this account belongs to, for example: “ComputerName”.
Hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID, for example, “4672(S): Special privileges assigned to new logon.”
SID of account for which logon was performed. Event Viewer automatically tries to resolve SIDs and show the account name. If the SID cannot be resolved, you will see the source data in the event.
The name of the account for which logon was performed.
Subject’s domain or computer name. Formats vary, and include the following:
Domain NETBIOS name example: DOMAIN
Lowercase full domain name: domain.local
Uppercase full domain name: DOMAIN.LOCAL
For some well-known security principals, such as LOCAL SERVICE or ANONYMOUS LOGON, the value of this field is “NT AUTHORITY”.
For local user accounts, this field will contain the name of the computer or device that this account belongs to, for example: “ComputerName”.
Hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID, for example, “4672(S): Special privileges assigned to new logon.”
The type of logon which was performed. The table on the description contains the list of possible values for this field.
The name of the trusted logon process that was used for the logon. See event “4611: A trusted logon process has been registered with the Local Security Authority” description for more information.
The name of the authentication package which was used for the logon authentication process. Default packages loaded on LSA startup are located in “HKLM\SYSTEM\CurrentControlSet\Control\Lsa\OSConfig” registry key. Other packages can be loaded at runtime. When a new package is loaded a “4610: An authentication package has been loaded by the Local Security Authority” (typically for NTLM) or “4622: A security package has been loaded by the Local Security Authority” (typically for Kerberos) event is logged to indicate that a new package has been loaded along with the package name.
The most common authentication packages are:
NTLM – NTLM-family Authentication
Kerberos – Kerberos authentication.
Negotiate – the Negotiate security package selects between Kerberos and NTLM protocols. Negotiate selects Kerberos unless it cannot be used by one of the systems involved in the authentication or the calling application did not provide sufficient information to use Kerberos.
Machine name from which logon attempt was performed.
A GUID that can help you correlate this event with another event that can contain the same Logon GUID, “4769(S, F): A Kerberos service ticket was requested event on a domain controller.
Transmitted services are populated if the logon was a result of a Service For User logon process.
[Type = UInt32]: the length of NTLM Session Security key. Typically it has 128 bit or 56 bit length. This parameter is always 0 if “Authentication Package” = “Kerberos”, because it is not applicable for Kerberos protocol. This field will also have “0” value if Kerberos was negotiated using Negotiate authentication package.
Hexadecimal Process ID of the process that attempted the logon. Process ID (PID) is a number used by the operating system to uniquely identify an active process.
Full path and the name of the executable for the process.
IP address of machine from which logon attempt was performed.
Source port which was used for logon attempt from remote machine.
0 for interactive logons.
User name that will be used for outbound (network) connections. Valid only for NewCredentials logon type.
Domain for the user that will be used for outbound (network) connections. Valid only for NewCredentials logon type.
a “Yes” or “No” flag, which indicates if the account is a virtual account (e.g., "Managed Service Account"), which was introduced in Windows 7 and Windows Server 2008 R2 to provide the ability to identify the account that a given Service uses, instead of just using "NetworkService".
A hexadecimal value of the paired logon session. If there is no other logon session associated with this logon session, then the value is “0x0”.
a “Yes” or “No” flag. If “Yes” then the session this event represents is elevated and has administrator privileges.
Lookup Audit Policy Configuration Settings
C:\> AuditPol.exe /get /subcategory:Logon
LEFT/RIGHT arrow keys for navigation
Back to List