Skip to main content
Skip table of contents

EVID 11: KDC Duplicate Name

Vendor Documentation

Log Fields and Parsing

This section details the log fields available in this log message type, along with values parsed for both LogRhythm Default and LogRhythm Default v2.0 policies. A value of "N/A" (not applicable) means that there is no value parsed for a specified log field.

Log FieldLogRhythm DefaultLogRhythm Default v2.0
ProviderN/A<tag2>
EventID Qualifiers<vmid><vmid>
VersionN/AN/A
Level<severity><severity>
TaskN/A<vendorinfo>
OpcodeN/AN/A
KeywordsN/A<result>
TimeCreatedN/AN/A
EventRecordIDN/AN/A
CorrelationN/AN/A
Execution ProcessId<processid>N/A
ThreadID<session>N/A
ChannelN/AN/A
Computer<dname><dname>
SecurityN/AN/A
DataN/A<object>
DataN/AN/A
BinaryN/AN/A
MiniportNameLenN/A<size>
MiniportNameN/A<object>
Name<object><object>
Type<objectname><objecttype>
DataN/A<domainimpacted>
N/A<account>
DataN/AN/A
RenderingInfoN/AN/A
MessageN/A<subject>

Log Processing Settings

This section details log processing changes made from the LogRhythm Default policy to LogRhythm Default v2.0. In some cases, base rules are broken down into sub-rules to appropriately parse log message types by their event types.

LogRhythm Default

Regex ID

Rule Name

Rule Type

Common Event

Classification

1008261EVID 11: KDC Duplicate NameBase RuleGeneral Kerberos ErrorError

LogRhythm Default v2.0

Regex ID

Rule Name

Rule Type

Common Event

Classification

1012632V 2.0 : EVID 11: KDC Encountered Duplicate NamesBase RuleGeneral KDC ErrorError
V 2.0 : EVID 11: Network Controller ConfiguredSub RuleConfiguration SuccessfulInformation
V 2.0 : EVID 11: Disk : Controller Error DetectedSub RuleGeneral Error Log MessageError
V 2.0 : EVID 11: Miniport RestartedSub RuleGeneral Information Log MessageInformation
V 2.0 : EVID 11: KDC Encountered Duplicate NamesSub RuleGeneral KDC ErrorError
V 2.0 : EVID 11: Rpm : Connection ResumedSub RuleSession ResumedOther Audit Success
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.