Hi All,
Would be great to get some help with this guys.
I get the following event IDs, using my admin account (which gets locked out). I can't see where these credentials are used for the life of me. I've looked at server tasks and nothing there.
---------------------------------------------------------------------------------------------
---Event ID 4648
A logon was attempted using explicit credentials.
Subject:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x7fbbb18
Logon GUID: {00000000-0000-0000-0000-000000000000}
Account Whose Credentials Were Used:
Account Name: ************Admin account
Account Domain:
Logon GUID: {00000000-0000-0000-0000-000000000000}
Target Server:
Target Server Name: ePO FQDN
Additional Information: ePO FQDN
Process Information:
Process ID: 0x4
Process Name:
Network Information:
Network Address: -
Port: -
This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
---------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------
---Event ID 4624
An account was successfully logged on.
Subject:
Security ID: SYSTEM
Account Name: My PC
Account Domain: Domain
Logon ID: 0x3e7
Logon Type: 9
New Logon:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x7fbbb18
Logon GUID: {00000000-0000-0000-0000-000000000000}
Process Information:
Process ID: 0xc9c
Process Name: C:\Program Files\McAfee\DLP\Agent\fcags.exe
Network Information:
Workstation Name:
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
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 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.
I also have an event 4634 and 4672 - not sure they'll be of any value.
I remove DLP and don't get the logs generated.
Thanks in advance.
Solved! Go to Solution.
Don't you used this accont credantials as DLP Evidence share user?
Don't you used this accont credantials as DLP Evidence share user?
Hi. Thanks for this. Yes. I just realised this about 10 minutes after posting. I've set it back to the system account. Now waiting for it all to calm down, but it is now generating less logs and without the username in question.
Well, the other practice could be to create designated service account, assign it appropriate privileges to DLP evidence share and configure it in DLP Client settings policy.