2018-08-03 11:41 AM
Hello,
Recently out pentest team used Pykek in one of our clients, monitored by NW, and we could not detect anything.
I was trying to create a rule but it can manifest by these premisses:
MS14-068 events may have one (or more) of these issues:
The Account Domain field is blank when it should be DOMAIN
The Account Domain field is DOMAIN FQDN when it should be DOMAIN.
PyKEK: Account Name is a different account from the Security ID.
PyKEK MS14-068 Exploit (author Sylvain Monné)
Event ID: 4624 (Account Logon)The Account Domain field is DOMAIN FQDN when it should be DOMAIN.
Account Name is a different account from the Security
IDEvent ID: 4768 (Kerberos TGS Request)
The Account Domain field is DOMAIN FQDN when it should be DOMAIN.
Event ID: 4672 (Admin Logon)The Account Domain field is DOMAIN FQDN when it should be DOMAIN.
Account Name is a different account from the Security ID
How can i create a rule with the premisse: Domain Name= FQDN ou Domain Name= blank ou even account name diferent from security ID?
Thanks
2018-08-03 01:18 PM
do you have sample log messages of these events to share that illustrate these events?
%NICWIN-4-Security_4672_Microsoft-Windows-Security-Auditing: Security,rn=13653003 cid=1876 eid=532,Thu Aug 02 19:48:45 2018,4672,Microsoft-Windows-Security-Auditing,,Audit Success,dc.domain.ca,Special Logon,,Special privileges assigned to new logon. Subject: Security ID: S-1-5-18 Account Name: DC$ Account Domain: DOMAIN Logon ID: 0x32CC325A Privileges: SeSecurityPrivilege SeBackupPrivilege SeRestorePrivilege SeTakeOwnershipPrivilege SeDebugPrivilege SeSystemEnvironmentPrivilege SeLoadDriverPrivilege SeImpersonatePrivilege SeEnableDelegationPrivilege
in this case the DC.DOMAIN.ca would be blank or DC per your details in the exploit (event.computer?)
same thing below?
%NICWIN-4-Security_4624_Microsoft-Windows-Security-Auditing: Security,rn=13623471 cid=4928 eid=532,Sun Jul 29 16:15:47 2018,4624,Microsoft-Windows-Security-Auditing,,Audit Success,dc.domain.ca,Logon,,An account was successfully logged on. Subject: Security ID: S-1-0-0 Account Name: - Account Domain: - Logon ID: 0x0 Logon Type: 3 Impersonation Level: Impersonation New Logon: Security ID: S-1-5-21-485293327-653150177-1594093571-1161 Account Name: nw-domain-logcollect Account Domain: DOMAIN Logon ID: 0x1E919301 Logon GUID: {6FC4F651-A09E-135A-6A43-40B2CF3E3F59} Process Information: Process ID: 0x0 Process Name: - Network Information: Workstation Name: - Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Kerberos Authentication Package: Kerberos 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 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.
2018-08-03 05:15 PM
2018-08-07 10:55 AM
Hello Eric,
Thanks for the reply.
Unfortunely i don't have logs. The tests we made while i was on vacation and it seems i can't find it.
We are waiting for the client order to do another Pykek test and then, maybe then.