Skip to main content
Skip table of contents

EVID 4778, 4779 : Windows Session Events (XML - Security)

Event Details

Event TypeAudit Other Logon/Logoff Events
Event Description
  • 4778(S) : A session was reconnected to a Windows Station.
  • 4779(S) : A session was disconnected from a Windows Station.
Event IDs4778, 4779

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/AN/A
EventID<vmid><vmid>
VersionN/AN/A
Level<severity><severity>
TaskN/A<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>
AccountName<login><login>
AccountDomain<domain><domainorigin>
LogonID<session><session>
SessionName<object><sessiontype>
ClientName<sname><sname>
ClientAddress<sip><sip>

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 EventClassification
1007872EVID 4778 & 4779 : Windows Session EventsBase RuleAuthentication ActivityAuthentication Success
EVID 4779 : Win Session DisconnectSub RuleSession DisconnectedOther Audit Success
EVID 4778 : Win Session ReconnectSub RuleUser LogonAuthentication Success

LogRhythm Default v2.0

Regex IDRule NameRule TypeCommon EventClassification
1011080V 2.0 : EVID 4778 & 4779 : Windows Station SessionBase RuleSession InformationInformation
V 2.0 : EVID 4778 : A Session Was ReconnectedSub RuleSession ReconnectedOther Audit Success
V 2.0 : EVID 4779 : A Session Was DisconnectedSub RuleSession DisconnectedOther Audit Success
JavaScript errors detected

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

If this problem persists, please contact our support.