AnsweredAssumed Answered

winevent_nic parser with Windows Server 2016

Question asked by Marco Demonte on Apr 6, 2017
Latest reply on May 10, 2017 by Marco Demonte

Hello,

I have noticed a parsing error in Windows Server 2016 login events with the "winevent_nic" parser, latest version (Parser Version: 181, Event Source Update: 105)

The LogonType MetaKey is valorized in a wrong way. 

 

Logon Type: 3 Restricted Admin Mode: - Virtual Account: No Elevated Token: No

 

 

For your information, I attach here below an example of the RAW and parsed event.

 

%NICWIN-4-Security_4624_Microsoft-Windows-Security-Auditing: Security,rn=116551 cid=2028 eid=592,Thu Apr 06 02:01:59 2017,4624,Microsoft-Windows-Security-Auditing,,Audit Success,servername.domain.com,Logon,,An account was successfully logged on. Subject: Security ID: S-1-0-0 Account Name: - Account Domain: - Logon ID: 0x0 Logon Information: Logon Type: 3 Restricted Admin Mode: - Virtual Account: No Elevated Token: No Impersonation Level: Impersonation New Logon: Security ID: S-1-5-21-000000000000000000 Account Name: MyAccountName Account Domain: DOMAIN Logon ID: 0x125AC36C Linked Logon ID: 0x0 Network Account Name: - Network Account Domain: - Logon GUID: {00000000-0000-0000-0000-000000000000} Process Information: Process ID: 0x0 Process Name: - Network Information: Workstation Name: SERVERNAME Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): NTLM V2 Key Length: 128 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.

 

 

sessionid    =    151688165432
time    =    2017-04-06T04:03:30.0
size    =    2476
lc.cid    =    
device.host    =    
medium    =    32
device.type    =    
device.class    =    
event.desc    =    "An account was successfully logged on."
event.user    =    "-"
logon.type    =    
obj.name    =    
user.dst    =    
alias.host    =    
process    =    
ec.theme    =    
ec.subject    =    
ec.activity    =    
ec.outcome    =    
msg    =    "An account was successfully logged on. Subject: Security ID: S-1-0-0 Account Name: - Account Domain: - Logon ID: 0x0 Logon Information: Logon Type: 3 Restricted Admin Mode: - Virtual Account: No Elevated Token: No Impersonation Level: Im"
event.time    =    2017-04-06 02:01:59.000
reference.id    =    
alert    =    
event.source    =    
event.type    =    
event.computer    =    
category    =    
obj.type    =    
msg.id    =    
event.cat.name    =    
device.group    =    
alert.id    =    
alert.id    =    
did    =    
rid    =    96306626132

 

 

Do you already have a solution or, are you going to release a new version for the parser?

Have you experienced the same issue?

 

Thank you for your help

Regards

 

 

Marco

Outcomes