Skip to main content
Skip table of contents

Mirror State Change

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 Field

LogRhythm DefaultLogRhythm Default v2.0
ProviderN/A<tag2>
EventID Qualifiers<vmid><vmid>
VersionN/AN/A
Level<severity><severity>
Task<vendorinfo><vendorinfo>
OpcodeN/AN/A
Keywords<command><result>
TimeCreatedN/AN/A
EventRecordIDN/AN/A
CorrelationN/AN/A
ExecutionN/AN/A
ChannelN/AN/A
Computer<dname><dname>
SecurityN/AN/A
HiveNameLengthN/A<size>
HiveNameN/A<object>
KeysUpdatedN/AN/A
DirtyPagesN/A<quantity>
Target

N/A

<dname>,
<domainimpacted>
AccountN/AN/A
IDN/AN/A
RequestedEtypesN/AN/A
AvailableEtypesN/AN/A
AccountToResetN/A<account>
DataN/A<object>
Data<object>N/A
DataN/AN/A
DataN/AN/A
DataN/AN/A
DataN/AN/A
DataN/A<dip>
BinaryN/AN/A

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

1008166Mirror State ChangeBase RuleObject ModifiedAccess Success

LogRhythm Default v2.0

Regex ID

Rule Name

Rule Type

Common Event

Classification

1012650




V 2.0 : EVID 16: General Log MessageBase RuleGeneral Information Log MessageInformation
V 2.0 : EVID 16: ExtMirr: Mirrored State ChangedSub RuleMirror State ChangedInformation
V 2.0 : EVID 16: Kerberos Ticket Not GeneratedSub RuleGeneral Kerberos ErrorError
V 2.0 : EVID 16: Access History ClearedSub RuleLog ClearedAccess Success
V 2.0 : EVID 16: WindowsUpdateClientSub RuleConnection InformationInformation
V 2.0 : EVID 16: Mpio: MPIO ErrorSub RuleGeneral Error Log MessageError
JavaScript errors detected

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

If this problem persists, please contact our support.