{"id":68,"date":"2016-02-20T15:26:09","date_gmt":"2016-02-20T15:26:09","guid":{"rendered":"http:\/\/eventlogxp.com\/blog\/?p=68"},"modified":"2016-03-10T06:23:12","modified_gmt":"2016-03-10T06:23:12","slug":"advanced-filtering-how-to-filter-events-by-event-descriptions","status":"publish","type":"post","link":"https:\/\/eventlogxp.com\/blog\/advanced-filtering-how-to-filter-events-by-event-descriptions\/","title":{"rendered":"Advanced filtering. How to filter events by event description"},"content":{"rendered":"

A key instrument for event logs analysis is the function of event filtering. All known event log analysis tools have filtering feature, and I suppose, it is the most demanded feature of these applications. Setting filter for the most of event fields is easy. As a rule, all the event log applications let you filter by timeframe, event level, source, event IDs, users or computers with a more or less friendly user interface.<\/p>\n

However, sometimes you may need to filter events by extra details, which you can see in the event description. Let’s take the task of\u00a0 displaying logon events from RDP users. Previously <\/a>I described how to display all the logon events, but now we need to make a more complex filter.<\/p>\n

We know that logon events are 4624 and 4625 (successful logon and unsuccessful logon attempt). In this post<\/a>, I showed how to interpret logon types and you can see that Logon type for RDP access is 10. So we need to filter by event ID= 4624 or 4625 and Logon type = 10. And this filter should be applied to Security log.<\/p>\n

Although Windows Event Viewer does not provide user interface to filter events by extra event details, you can query event log by using structured XML queries. This feature is available since Windows 2008\/Vista. Structured XML query is a special language based on XPath 1.0 syntax intended to retrieve events from event logs. \u00a0You can find information about the structured XML queries and XPath expressions at https:\/\/msdn.microsoft.com\/en-us\/library\/windows\/desktop\/dd996910(v=vs.85).aspx<\/a><\/p>\n

Here is a XML filter query for our task:<\/p>\n

<QueryList>
\n<Query Id=”0″ Path=”Security”>
\n<Select Path=”Security”>
\n*[System[(EventID=4624 or EventID=4625)]]
\nand
\n*[EventData[Data[@Name=’LogonType’] and Data=10]]
\n<\/Select>
\n<\/Query>
\n<\/QueryList><\/p><\/blockquote>\n

Using the power of XML query, you may filter events by virtually any criteria. Our Event Log Explorer “understands” the structured XML queries as well as built-in Event Viewer. But unlike Event Viewer, you don’t need to use full XML queries. Event Log Explorer accepts short XPath expressions like:<\/p>\n

*[System[(EventID=4624 or EventID=4625)]] \u00a0and
\n*[EventData[Data[@Name=’LogonType’] and Data=10]]<\/p><\/blockquote>\n

However, despite the advantages of XML filtering, it is not easy to use it, especially if you don\u2019t used to write XML queries on a regular basis.<\/p>\n

So now, I will show how we simplified this process with our software.<\/p>\n

Select View->Filter from the Event Log Explorer main menu to display Filter dialog.<\/p>\n

First of all, you should type 4624,4625<\/em><\/strong> into Event ID(s) filed because we need only logon events.<\/p>\n

Event Log Explorer provides two basic ways of filtering events by description.<\/p>\n

Filtering events by description text<\/h4>\n

You can just type any text in “Text in description” field and Event Log Explorer will display all events that contain this text in the description. You may just try to type<\/p>\n

Logon Type: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a010<\/em><\/strong><\/p><\/blockquote>\n

And this MAY really work. However, it is not reliable at all. You should not rely on the number of tabs inside description, moreover you cannot just type the tabulation symbols in the input line (I pasted it from the event description, and you should not copy it from this article – it won’t work – there\u00a0are three tabulation symbols between “:” and “10”). Thereby, I suggest using this simple way, only for simple filters, e.g. when you need to display events containing a specific file name in the description.<\/p>\n

The same “Text in description” filed has an extra feature when you enable RegExp checkbox near it. In this case, you can filter events with the power of regular expressions. When RegExp checkbox enabled, Event Log Explorer will search all event descriptions for occurrence of the regular expressions you typed in “Text in description” filed. Our expression should look like<\/p>\n

Logon Type:\\s*10<\/em><\/strong><\/p><\/blockquote>\n

or<\/p>\n

Logon Type:[ \\t]*10<\/em><\/strong><\/p><\/blockquote>\n

You probably think that this way is not much better than using structured XML queries. Instead of learning XPath syntax, I recommend you to learn regular expressions?<\/p>\n

Although I don\u2019t see alternatives to regular expression filters for some specific log analysis tasks, Event Log Explorer lets you fulfill this very task (displaying RDP logon events) much easier.<\/p>\n

Filtering events by description parameters<\/h4>\n

Event Log Explorer gives you a user friendly ability to filter Security log by description parameters. In fact, you just tell the program the following:<\/p>\n

Logon type\u00a0\u00a0 equals\u00a0\u00a0 10<\/em><\/p>\n

To make entering the filter condition easy, I recommend select an even in the event list that contains Logon type in the description (you should do this before opening Filter dialog).<\/p>\n

Use Filter by description params<\/em> group to create your filter conditions:<\/p>\n

\"event<\/a><\/p>\n

I believe that this way significantly saves your time for security log analysis.<\/p>\n

Note that this approach works only when you analyze Security event logs because the security log descriptions are well-structured. When you analyze other logs, you may need to use regular expressions or XPath filter queries.<\/p>\n\"Facebook\"<\/a>\"twitter\"<\/a>\"reddit\"<\/a>\"pinterest\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>","protected":false},"excerpt":{"rendered":"

A key instrument for event logs analysis is the function of event filtering. All known event log analysis tools have filtering feature, and I suppose, it is the most demanded feature of these applications. Setting filter for the most of event fields is easy. As a rule, all the event log applications let you filter by timeframe, event level, source, event IDs, users or computers\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":74,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[10,40,42,2],"tags":[19,34,21,33,49,4,18,35],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts\/68"}],"collection":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/comments?post=68"}],"version-history":[{"count":11,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts\/68\/revisions"}],"predecessor-version":[{"id":99,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts\/68\/revisions\/99"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/media\/74"}],"wp:attachment":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/media?parent=68"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/categories?post=68"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/tags?post=68"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}