Skip to main content
Skip table of contents

EVID 5449 : Windows Filtering Platform Provider Context Changed

Event Details

Event TypeWindows Filtering Platform Provider Context Changed
Event DescriptionN/A
Event ID5449

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

Provider N/A N/A
EventID<vmid><vmid>
VersionN/A N/A
Level<severity><severity>
TaskN/A<vendorinfo>
OpcodeN/A N/A
Keywords<command> <vendorinfo><result>
TimeCreatedN/A N/A
EventRecordIDN/A N/A
CorrelationN/A N/A
ExecutionN/A N/A
ChannelN/A N/A
Computer<dname><dname>
ProcessId<processid><processid>
UserSidN/A N/A
UserName<domainorigin>, <login><domainimpacted>, <account>
ProviderKeyN/A N/A
ProviderNameN/A N/A
ChangeType<tag3> <action>
CalloutKeyN/A N/A
CalloutNameN/A N/A
CalloutTypeN/A N/A
CalloutIdN/A N/A
LayerKeyN/A N/A
LayerName<object>NA
LayerIdN/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 IDRule NameRule TypeCommon EventClassification
1007861EVID 5446 - 5450 : Windows Filter Platform ChangeBase RuleConfiguration Modified : SecurityConfiguration
EVID 5446 : Filtering Platform Callout Chng : DelSub RuleConfiguration Deleted : SecurityConfiguration
EVID 5446 : Filtering Platform Callout Chng : AddSub RuleConfiguration Loaded : SecurityConfiguration

LogRhythm Default v2.0

Regex ID

Rule Name

Rule Type

Common Event

Classification

1012329

V 2.0 : EVID 5449 : Windows Filtering Platform Provider Context ChangedBase RuleConfiguration Modified : SecurityConfiguration
JavaScript errors detected

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

If this problem persists, please contact our support.