4648 - Explicit Credentials Success
https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4648
Event ID 4648 in the Windows Security Event Log is a significant security event that indicates a logon attempt was made using explicit credentials. This event occurs when a user attempts to log on to a computer or access network resources by specifying credentials different from those associated with the current session. Such behavior is typical in scenarios where the "RunAs" command is used, or when scheduled tasks and services are configured to run under a specific account. Monitoring Event ID 4648 is crucial for identifying potential security risks, such as credential misuse or lateral movement attempts within a network.
Logged by the Security subsystem whenever a process or user initiates a logon attempt with explicit credentials.
Category: Audit Logon
Significance:
Security Implications: Event ID 4648 may indicate legitimate use cases, such as administrators managing multiple accounts or services configured with specific user credentials. However, it can also signal malicious activities, including pass-the-hash attacks, where attackers use stolen credentials to move laterally across a network.
Operational Context: In benign scenarios, this event helps track administrative activities and application behaviors requiring alternate credentials. In security contexts, it aids in detecting unauthorized access attempts and potential compromise.
Details Included in Event ID 4648
Subject: Information about the user or process that initiated the logon attempt. This includes:
Security ID: The SID of the initiating user.
Account Name: The name of the initiating account.
Account Domain: The domain of the initiating account.
Logon ID: A reference to the logon session of the initiating account.
Logon Type: Specifies the type of logon that was attempted. Common types include interactive (2), network (3), and batch (4).
Account Whose Credentials Were Used: Details about the account whose credentials were explicitly specified. This includes:
Account Name: The name of the account whose credentials were used.
Account Domain: The domain of the account whose credentials were used.
Process Information: Provides details about the process that requested the logon. This includes:
Process ID: The identifier of the process.
Process Name: The name of the process.
Network Information: Details about the network address and port number involved in the logon attempt.
How to Use Event ID 4648 for Security
Monitoring and Alerting: Setting up alerts for unexpected or unauthorized use of Event ID 4648 can help detect potential security threats early. Special attention should be given to patterns or anomalies, such as logon attempts at unusual hours or from unusual locations.
Forensic Analysis: In the aftermath of a security incident, analyzing occurrences of Event ID 4648 can help in understanding how an attacker might have used stolen credentials to access resources or move laterally within the environment.
Access Reviews and Audits: Regular reviews of logs containing Event ID 4648 are important for ensuring that the use of explicit credentials aligns with organizational policies and security best practices.
Best Practices for Monitoring Event ID 4648
Enable Detailed Auditing: Ensure that "Audit Logon" is enabled in Group Policy to capture detailed events related to logon activities, including the use of explicit credentials.
Implement Least Privilege Principle: Minimize the number of users and accounts with permissions to use alternate credentials to reduce the risk of misuse or attack.
Educate Users and Administrators: Provide training on the secure management of credentials and the potential risks associated with their misuse.
Use SIEM Solutions: Employ Security Information and Event Management (SIEM) systems to correlate Event ID 4648 with other indicators of compromise, enhancing the ability to detect malicious activities.
Limitations
While Event ID 4648 provides valuable information about the use of explicit credentials, it does not inherently distinguish between legitimate and malicious activities. Contextual analysis, correlation with additional indicators, and understanding normal usage patterns within the organization are necessary to accurately interpret these events.
Last updated
Was this helpful?