Skip to main content
Skip table of contents

Events

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 Default

LogRhythm Default v2.0

Header: Severity

<severity>

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A 

N/A

N/A

N/A

<vmid>

N/A

active directory

<object>

N/A

N/A

<objectname>

N/A

N/A

<dname>

N/A

N/A

<sip>

N/A

N/A

<domain>
<login>

N/A

authentication

<tag1>

N/A

N/A

<smac>

N/A

N/A

<login>

N/A

dhcp

<object>

N/A

N/A

<dip>

N/A

N/A

<dmac>

N/A

N/A

<snatip>

N/A

content_filtering

<object>

N/A

url

<url>

N/A

category

<objectname>

N/A

server

<dip>
<dport>

N/A

client_ip

<sip>

N/A

client_mac

<smac>

N/A

cn

<login>

N/A

type

<vmid>

N/A

packet

<objectname>

N/A

bssid

<smac>

N/A

dst

<dmac>

N/A

state

<object>

N/A

reason

<reason>
<subject>

N/A

identity

<domain>
<login>

N/A

dhcp_ip

<dip>

N/A

dhcp_server_mac

<dmac>

N/A

original_server_ip

<sip>

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

1005924

Events

Base Rule

System Events

Network Traffic

Active Directory Messages

Sub Rule

General Active Directory Information

Information

Authentication Messages

Sub Rule

Authentication Activity

Authentication Success

Content Filtering Block Messages

Sub Rule

Dropped By Content Filtering

Failed Activity

DHCP Messages

Sub Rule

General DHCP

Information

LogRhythm Default v2.0

N/A

JavaScript errors detected

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

If this problem persists, please contact our support.