Skip to main content
Skip table of contents

Forensics 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 FieldLogRhythm DefaultLogRhythm Default v2.0
Product<version><vmid>
Action<action><action>
ActionN/A<tag1>
SIP<sip><sip>
SPort<sport><sport>
DIP<dip><dip>
dport<dport><dport>
protocol<protname><protnum>
ifname<sinterface><sinterface>
ifdirection<tag1>N/A
Reason<reason><reason>
Info<vendorinfo>N/A
XlateSIP<snatip><snatip>
XlateSport<snatport><snatport>
XlateDIP<dnatip><dnatip>
XlateDPort<dnatport><dnatport>
CN<login>N/A
matched_category<subject>N/A
Url<url><url>
src_machine_name<sname><sname>
src_user_name<login><login>
Confidence_Level<amount>N/A
Severity<severity><severity>
malware_action<vendorinfo><vendorinfo>
Protection_name<threatname><threatname>
Protection_name<object>N/A
description<subject><subject>
PolicyName<policy>N/A
file_md5<hash><hash>
file_name<objectname><object>
file_type<objecttype><objecttype>
file_size<bytes><size>
generalinformation<vendorinfo>N/A
N/AN/A<status>
N/AN/A<hash>
N/AN/A<hash>

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

Rule ID

Rule Name

Rule Type

Common Event

Classification

1011410Forensics EventsBase RuleVuln Low Severity : ForensicsVulnerability

LogRhythm Default v2.0

Rule IDRule NameRule TypeCommon EventClassification
1012019V 2.0 : Forensics EventsBase RuleGeneral Threat MessageActivity
V 2.0 : Forensics : Detect ActionSub RuleGeneral Threat MessageActivity
V 2.0 : Forensics : Prevent ActionSub RuleThreat BlockedFailed Activity
JavaScript errors detected

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

If this problem persists, please contact our support.