Skip to main content
Skip table of contents

EVID 18 : Named Pipe Connected (Sysmon)

Event Details

Event TypePipeEvent (Pipe Connected)
Event Description18 : Logs when a named pipe connection is made between a client and a server.
Event ID18

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 N/A
EventID<vmid><vmid>
Version<version>N/A 
Level<severity><severity>
Task<command><vendorinfo>
OpcodeN/A N/A 
KeywordsN/A <result>
TimeCreated N/A N/A 
EventRecordIDN/A N/A 
Correlation N/A N/A 
Execution <processid>N/A 
ChannelN/A N/A 
Computer<dname><dname>
Security N/A N/A 
UserID<domain>, <login>N/A 
ProcessGuid<serialnumber>N/A 
ProcessId<session><processid>
PipeName<objectname>N/A 
Image<object><process>
Pipe Connected<subject>, <vendorinfo>N/A
RuleNameN/A<policy>

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 IDRule NameRule TypeCommon EventsClassifications
1009502

EVID 17/18 : Named Pipe Created/Connected

Base Rule

Creating Named Pipe

Information

[1489790]

EVID 18 : Named Pipe ConnectedSub RuleCreating Named PipeInformation
EVID 17 : Named Pipe CreatedSub RuleCreating Named PipeInformation

LogRhythm Default v2.0 

Regex IDRule NameRule TypeCommon EventsClassifications
1011217


V 2.0 : Pipe Creation/Connection Events

Base Rule

Object Modified

Access Success

V 2.0 : EVID 17 : Pipe CreatedSub RuleObject CreatedAccess Success
V 2.0 : EVID 18 : Pipe ConnectedSub RuleConnection EnabledInformation
JavaScript errors detected

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

If this problem persists, please contact our support.