<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Filtering windows security event logs with Regex in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169988#M48625</link>
    <description>&lt;P&gt;Sorry for the delay.  I updated the answer.  Be careful that you are not dropping 100% of the 4624 events.&lt;/P&gt;</description>
    <pubDate>Tue, 04 Mar 2014 15:51:01 GMT</pubDate>
    <dc:creator>lukejadamec</dc:creator>
    <dc:date>2014-03-04T15:51:01Z</dc:date>
    <item>
      <title>Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169975#M48612</link>
      <description>&lt;P&gt;Hi there.&lt;/P&gt;

&lt;P&gt;We've been having issues with our DC's sending to much information across to Splunk and require assistance on creating some regex filtering strings, as we are not familiar with regex.&lt;/P&gt;

&lt;P&gt;We are currently pulling windows security events from 2 Windows domain controllers and received issues with the amount events indexed which constantly violates or license.  &lt;/P&gt;

&lt;P&gt;We have windows logon events (event code: 4624)  that capture both user information logons as well as machine logons. There are so many of these logon events that we dont need and would like to remove it in order to stay within the license limit.&lt;/P&gt;

&lt;P&gt;The security events also have a large description included in the event under the event type "Message" that would like to be removed.&lt;/P&gt;

&lt;P&gt;Here is an example of what we have:&lt;BR /&gt;
Log Name:      Security&lt;BR /&gt;
Source:        Microsoft-Windows-Security-Auditing&lt;BR /&gt;
Date:          2/28/2014 10:25:51 AM&lt;BR /&gt;
Event ID:      4624&lt;BR /&gt;
Task Category: Logon&lt;BR /&gt;
Level:         Information&lt;BR /&gt;
Keywords:      Audit Success&lt;BR /&gt;
User:          N/A&lt;BR /&gt;
Computer:      &lt;EM&gt;Computer&lt;/EM&gt;&lt;BR /&gt;
Description:&lt;BR /&gt;
An account was successfully logged on.&lt;/P&gt;

&lt;P&gt;Subject:&lt;BR /&gt;
            Security ID:                   NULL SID&lt;BR /&gt;
            Account Name:              -&lt;BR /&gt;
            Account Domain:                        -&lt;BR /&gt;
            Logon ID:                      0x0&lt;/P&gt;

&lt;P&gt;Logon Type:                              3&lt;/P&gt;

&lt;P&gt;New Logon:&lt;BR /&gt;
            Security ID:                   &lt;EM&gt;DOMAIN&lt;/EM&gt;*USERNAME*&lt;BR /&gt;
            Account Name:             &lt;EM&gt;username&lt;/EM&gt;&lt;BR /&gt;
            Account Domain:                        &lt;EM&gt;DOMAIN&lt;/EM&gt;&lt;BR /&gt;
            Logon ID:                      0xb008f014&lt;BR /&gt;
            Logon GUID:                  {877a24e2-7fff-857b-30a6-e4f061536b11}&lt;/P&gt;

&lt;P&gt;Process Information:&lt;BR /&gt;
            Process ID:                   0x0&lt;BR /&gt;
            Process Name:               -&lt;/P&gt;

&lt;P&gt;Network Information:&lt;BR /&gt;
            Workstation Name:&lt;BR /&gt;&lt;BR /&gt;
            Source Network Address:            &lt;EM&gt;IP address&lt;/EM&gt;&lt;BR /&gt;
            Source Port:                  49914&lt;/P&gt;

&lt;P&gt;Detailed Authentication Information:&lt;BR /&gt;
            Logon Process:              Kerberos&lt;BR /&gt;
            Authentication Package:  Kerberos&lt;BR /&gt;
            Transited Services:        -&lt;BR /&gt;
            Package Name (NTLM only):        -&lt;BR /&gt;
            Key Length:                   0&lt;/P&gt;

&lt;P&gt;This event is generated when a logon session is created. It is generated on the computer that was accessed.&lt;/P&gt;

&lt;P&gt;The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.&lt;/P&gt;

&lt;P&gt;The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).&lt;/P&gt;

&lt;P&gt;The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.&lt;/P&gt;

&lt;P&gt;The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.&lt;/P&gt;

&lt;P&gt;The authentication information fields provide detailed information about this specific logon request.&lt;BR /&gt;
            - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.&lt;BR /&gt;
            - Transited services indicate which intermediate services have participated in this logon request.&lt;BR /&gt;
            - Package name indicates which sub-protocol was used among the NTLM protocols.&lt;BR /&gt;
            - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;We recieve the same event for machine logons however it has the machine name with a $ in the name:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;        Security ID:                   *DOMAIN*\*MACHINE*$
        Account Name:              *MACHINE*$
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The request is pretty much this:&lt;/P&gt;

&lt;P&gt;Create a regex for the props and transforms that will filter out ALL events that contain the "machine"$  and KEEP the events that contain a proper username. REMOVE the "Message" field from the events to reduce indexing size.&lt;/P&gt;

&lt;P&gt;Any help will be greatly appreciated. Please let me know if it needs more clarification.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Andrew&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 02:17:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169975#M48612</guid>
      <dc:creator>andrewdidone</dc:creator>
      <dc:date>2014-02-28T02:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169976#M48613</link>
      <description>&lt;P&gt;What version of Splunk?&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 02:24:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169976#M48613</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-02-28T02:24:04Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169977#M48614</link>
      <description>&lt;P&gt;This should work for you:&lt;/P&gt;

&lt;P&gt;props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; [source::wineventlog:security]
 TRANSFORMS-drop = delFilter
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;transforms.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[delFilter]
REGEX = (?msi)^EventCode=4624\D.*Account\s+Name:\s+[a-z0-9-]+[\$]
DEST_KEY = queue
FORMAT = nullQueue
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will grab any account name made up of the characters &lt;CODE&gt;a-z 0-9&lt;/CODE&gt; and &lt;CODE&gt;-&lt;/CODE&gt; that ends in a &lt;CODE&gt;$&lt;/CODE&gt;.  You should test this in a search regex first though because it is very possible that the machine name is as one of the account names in 100% of the 4624 events, which means you would be dropping all of them.&lt;/P&gt;

&lt;P&gt;See this post:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/answers/102989/windows-event-filtering"&gt;http://answers.splunk.com/answers/102989/windows-event-filtering&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 02:37:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169977#M48614</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-02-28T02:37:50Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169978#M48615</link>
      <description>&lt;P&gt;Hi lukejadamec&lt;/P&gt;

&lt;P&gt;Thanks for the quick reply. I tried this and sadly it didn't seem to work.&lt;/P&gt;

&lt;P&gt;Breakdown of what I did:&lt;BR /&gt;
-Created and placed props.conf and transforms.conf with config supplied above into the system/local folder of the Indexer.&lt;BR /&gt;
-Restarted splunk via command line: "splunk restart".&lt;/P&gt;

&lt;P&gt;I changed the time picker to 1 minute ago. Unfortunately I am still seeing the "Message" field as well as the events from the "machine"$ hots. &lt;BR /&gt;
Would you have any further ideas on this. Anything will greatly appreciated.&lt;/P&gt;

&lt;P&gt;Cheers,&lt;BR /&gt;
Andrew&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 03:07:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169978#M48615</guid>
      <dc:creator>andrewdidone</dc:creator>
      <dc:date>2014-02-28T03:07:01Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169979#M48616</link>
      <description>&lt;P&gt;I can test it in the morning.&lt;BR /&gt;
Otherwise, the way you set it up looks good except - this does not target the Message field.  You should be able to test the regex in a search string to fix it:&lt;BR /&gt;
&lt;CODE&gt;index=main EventCode=4624 | regex "(?msi)^EventCode=4624\D.*^Security\sID:\s+[^ ]\$.*^Account\s+Name:\s+[^ ]\$" |table EventCode&lt;/CODE&gt;&lt;BR /&gt;
That should pull only 4624 events as specified, if you get nothing, then the regex needs fixing.&lt;BR /&gt;
You can start small:&lt;BR /&gt;
 &lt;CODE&gt;index=main EventCode=4624 | regex "(?msi)^EventCode=4624\D&lt;/CODE&gt;"&lt;BR /&gt;
And grow:&lt;BR /&gt;
&lt;CODE&gt;index=main EventCode=4624 | regex "(?msi)^EventCode=4624\D.*^Security\sID:\s+[^ ]\$"&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 03:22:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169979#M48616</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-02-28T03:22:38Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169980#M48617</link>
      <description>&lt;P&gt;6.0 on the Indexer and SearchHead, 5.0.5 on Heavy Forwarder.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 03:33:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169980#M48617</guid>
      <dc:creator>andrewdidone</dc:creator>
      <dc:date>2014-02-28T03:33:08Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169981#M48618</link>
      <description>&lt;P&gt;Place the props and transforms on the heavy forwarder.&lt;BR /&gt;
You can only cook data once.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 03:36:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169981#M48618</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-02-28T03:36:27Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169982#M48619</link>
      <description>&lt;P&gt;Thanks for that.&lt;BR /&gt;
The small string returns events, but the "grow" string and initial search string does not. &lt;BR /&gt;
Also, I should mention that the "Account Name" and "Seurity ID" are labeled as "Account_Name" and "Security_ID" in the Splunk fields. Perhaps that causes issues int the regex?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:00:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169982#M48619</guid>
      <dc:creator>andrewdidone</dc:creator>
      <dc:date>2020-09-28T16:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169983#M48620</link>
      <description>&lt;P&gt;The Heavy forwarder is just passing other information and is not indexing. It exists for other types of data sets. Apologies, I should have mentioned that.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 03:52:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169983#M48620</guid>
      <dc:creator>andrewdidone</dc:creator>
      <dc:date>2014-02-28T03:52:20Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169984#M48621</link>
      <description>&lt;P&gt;When using regex, base your regex on the return from -&lt;BR /&gt;
&lt;CODE&gt;EventCode=4624 |table _raw&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 03:53:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169984#M48621</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-02-28T03:53:12Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169985#M48622</link>
      <description>&lt;P&gt;Ah ok. Yep they return as Security ID: and Account Name. I'll keep that in mind for the future.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 04:04:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169985#M48622</guid>
      <dc:creator>andrewdidone</dc:creator>
      <dc:date>2014-02-28T04:04:27Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169986#M48623</link>
      <description>&lt;P&gt;I see the problem.  These are multi value fields, and the machine name with a $ can occur in 100% of them.  Are you looking to drop the events where the $ is in the first or second Account_Name field?&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2014 15:21:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169986#M48623</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-02-28T15:21:01Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169987#M48624</link>
      <description>&lt;P&gt;Both, really. We don't want to see the events from the $ machines at all. Is that possible? I realize it's difficult with the Windows event logs format being the way they are.&lt;/P&gt;</description>
      <pubDate>Sun, 02 Mar 2014 22:37:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169987#M48624</guid>
      <dc:creator>andrewdidone</dc:creator>
      <dc:date>2014-03-02T22:37:27Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169988#M48625</link>
      <description>&lt;P&gt;Sorry for the delay.  I updated the answer.  Be careful that you are not dropping 100% of the 4624 events.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Mar 2014 15:51:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169988#M48625</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-03-04T15:51:01Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169989#M48626</link>
      <description>&lt;P&gt;Hey, thanks for taking the time on this. Unfortunately i am still seeing the undesired events. Please see raw data below I believe whats causing an issue is the fact there are 2 Account Name fields in the event. Is there a way to do "Account Name: = "-"  AND "&lt;EM&gt;machine&lt;/EM&gt;$" &lt;/P&gt;

&lt;P&gt;Subject:&lt;BR /&gt;
    Security ID:        NULL SID&lt;BR /&gt;
    Account Name:       -&lt;BR /&gt;
    Account Domain:     -&lt;BR /&gt;
    Logon ID:       0x0&lt;/P&gt;

&lt;P&gt;Logon Type:         3&lt;/P&gt;

&lt;P&gt;New Logon:&lt;BR /&gt;
    Security ID:        AUSODOM\0613-09015$&lt;BR /&gt;
    Account Name:       0613-09015$&lt;BR /&gt;
    Account Domain:     AUSODOM&lt;BR /&gt;
    Logon ID:       0x157ad97b2&lt;BR /&gt;
    Logon GUID:     {98EF322F-&lt;BR /&gt;
    Key Length:     0&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Andrew&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2014 23:59:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169989#M48626</guid>
      <dc:creator>andrewdidone</dc:creator>
      <dc:date>2014-03-06T23:59:13Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169990#M48627</link>
      <description>&lt;P&gt;Yes....  But it will take a few minutes.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2014 00:57:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169990#M48627</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-03-07T00:57:12Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169991#M48628</link>
      <description>&lt;P&gt;Try this in a search first:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;EventCode=4624 | regex "(?msi)^EventCode=4624\D.*Account\s+Name:\s+-.*Account\s+Name:\s+[a-z0-9-]+[\$]"&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;It should find all of the events you want to drop.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2014 01:01:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169991#M48628</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2014-03-07T01:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169992#M48629</link>
      <description>&lt;P&gt;Can you share the transforms.conf on removing the "Message" and "Body" in order to reduce indexing size? Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Mar 2015 09:21:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169992#M48629</guid>
      <dc:creator>hkust</dc:creator>
      <dc:date>2015-03-13T09:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169993#M48630</link>
      <description>&lt;P&gt;Can you explain how can I just filter out Security_ID="NULL SID". Need help to find exact regex&lt;/P&gt;</description>
      <pubDate>Thu, 07 May 2015 15:37:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169993#M48630</guid>
      <dc:creator>sys1pmp</dc:creator>
      <dc:date>2015-05-07T15:37:42Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering windows security event logs with Regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169994#M48631</link>
      <description>&lt;P&gt;this works great in the search, but I tried this in my transforms and I still get the events...   &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2015 23:28:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Filtering-windows-security-event-logs-with-Regex/m-p/169994#M48631</guid>
      <dc:creator>leonsanm</dc:creator>
      <dc:date>2015-09-02T23:28:59Z</dc:date>
    </item>
  </channel>
</rss>

