Event Details
Operating System->Microsoft Windows->Built-in logs->Windows 2008 or higher->Security Log->Account Logon->Kerberos Authentication Service->EventID 4824 - Kerberos preauthentication by using DES or RC4 failed because the account was a member of the Protected User group.
EventID 4824 - Kerberos preauthentication by using DES or RC4 failed because the account was a member of the Protected User group.

Find more information about this event on 
ultimatewindowssecurity.com.
 Sample:
Kerberos preauthentication by using DES or RC4 failed because the account was a member of the Protected User group.

Account Information:
	Security ID:		%2
	Account Name:		%1

Service Information:
	Service Name:		%3

Network Information:
	Client Address:		%7
	Client Port:		%8

Additional Information:
	Ticket Options:		%4
	Failure Code:		%5
	Pre-Authentication Type:	%6

Certificate Information:
	Certificate Issuer Name:		%9
	Certificate Serial Number: 	%10
	Certificate Thumbprint:		%11

Certificate information is only provided if a certificate was used for pre-authentication.
Pre-authentication types, ticket options and failure codes are defined in RFC 4120.
If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.
Log Type: Windows Event Log
 Uniquely Identified By:
Log Name: Security
Filtering Field Equals to Value
OSVersion Windows Vista (2008)
Windows 7 (2008 R2)
Windows 8 (2012)
Windows 8.1 (2012 R2)
Windows 10 (2016)
Category Account Logon
Source Microsoft-Windows-Security-Auditing
TaskCategory Kerberos Authentication Service
EventId 4824
Field Matching
FieldDescriptionStored inSample Value
DateTime Date/Time of event origination in GMT format. DateTime 10.10.2000 19:00:00
Source Name of an Application or System Service originating the event. Source Security
Type Warning, Information, Error, Success, Failure, etc. Type Success
User Domain\Account name of user/service/computer initiating event. User RESEARCH\Alebovsky
Computer Name of server workstation where event was logged. Computer DC1
EventID Numerical ID of event. Unique within one Event Source. EventId 576
Description The entire unparsed event message. Description Special privileges assigned to new logon.
Log Name The name of the event log (e.g. Application, Security, System, etc.) LogName Security
Task Category A name for a subclass of events within the same Event Source. TaskCategory
Level Warning, Information, Error, etc. Level
Keywords Audit Success, Audit Failure, Classic, Connection etc. Keywords
Category A name for an aggergative event class, corresponding to the similar ones present in Windows 2003 version. Category Account Logon
Object Name -
Whom -
Object Type -
Class Name -
Security ID InsertionString2
Account Name InsertionString1
Account Domain -
Account Information: Account Name The name of the account that Kerberos request was processed for InsertionString1 DCC1$
Service Information: Service Name The account name of the service distributing tickets, e.g. krbtgt InsertionString4 krbtgt
Network Information: Client Address The IP address of the computer that sent the ticket request. If the request was made locally, then the address will be listed as 127.0.0.1 InsertionString10 ::1
Network Information: Client Port The network port on the client machine that request was sent from InsertionString11 0
Additional Information: Ticket Options A hexadecimal number representing the Key Distribution Center (KDC) Option flags that were used or requested when the ticket was issued. KDC Option flags include information such as whether a ticket can be forwarded or renewed. The number in the Ticket Options field is a bit mask InsertionString6 0x40810010
Security ID -
Account Name -
Service Name InsertionString3
Client Address InsertionString7
Client Port InsertionString8
Ticket Options InsertionString4
Failure Code InsertionString5
Pre-Authentication Type InsertionString6
Certificate Issuer Name InsertionString9
Certificate Serial Number InsertionString10
Certificate Thumbprint InsertionString11
Comments
You must be logged in to comment