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 Default
LogRhythm Default v2.0
Provider
N/A
N/A
EventID
<vmid>
<vmid>
Version
N/A
N/A
Level
N/A
<severity>
Task
N/A
<vendorinfo>
Opcode
N/A
N/A
Keywords
<tag1>
<result>
TimeCreated
N/A
N/A
EventRecordID
N/A
N/A
Correlation
N/A
N/A
Execution
N/A
N/A
Channel
N/A
N/A
Computer
<dname>
<dname>
SubjectUserSid
N/A
N/A
SubjectUserName
<login>, <tag2>
<login>
SubjectDomainName
<domain>
<domainorigin>
SubjectLogonId
<session>
<session>
DomainName
<tag3>
N/A
DomainSid
N/A
N/A
TdoType
<tag4>
N/A
TdoDirection
<tag5>
N/A
TdoAttributes
N/A
N/A
SidFilteringEnabled
N/A
N/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
1000630
EVID 4706, 4707, 4716 : Domain Trust Events
Base Rule
Domain Trust Information
Information
EVID 4706 : Domain Trust Created
Sub Rule
Trust Relationship Established
Access Granted
EVID 4707 : Domain Trust Removed
Sub Rule
Trust Relationship Revoked
Access Revoked
EVID 4716 : Domain Trust Info Modified
Sub Rule
Configuration Modified : Security
Configuration
LogRhythm Default v2.0
Regex ID
Rule Name
Rule Type
Common Event
Classification
1011104
V 2.0 : General Policy Change Events
Base Rule
Policy Modified : System
Policy
V 2.0 : EVID 4713 : Kerberos Policy Modified
Sub Rule
Policy Modified : System
Policy
V 2.0 : EVID 4715 : SACL On Object Modified
Sub Rule
Policy Modified : Object
Policy
V 2.0 : EVID 4716 : Domain Trust Modified
Sub Rule
Policy Modified : Domain
Policy
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.