<?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 How to filter users ending with $ using inputs.conf on a UF v6.6. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-users-ending-with-using-inputs-conf-on-a-UF-v6-6/m-p/335364#M62027</link>
    <description>&lt;P&gt;Hi and thankyou in advance,&lt;/P&gt;

&lt;P&gt;I need to be able to filter EventCode 4624 to NOT includes events with "Account Name" ending in $ (the machine name).&lt;BR /&gt;
OR&lt;BR /&gt;
Possibly with the Security ID: NULL SID&lt;BR /&gt;
However i would prefer with "Account Name" ending in $&lt;/P&gt;

&lt;P&gt;In our environment we use WEF for all workstations which forward to a WEF server which then has a splunk UF to forward to the indexer peers.&lt;/P&gt;

&lt;P&gt;I was under the impression this could be done on the UF if version was 6 or newer (i have v6.6.1)&lt;BR /&gt;
using the inputs.conf?&lt;/P&gt;

&lt;P&gt;I have tried things along the lines of &lt;BR /&gt;
whitelist = EventCode=%^(4624)$% Message="(?:Account Name:).+[?!\$]"&lt;/P&gt;

&lt;P&gt;but this ends up dropping all events.&lt;/P&gt;

&lt;P&gt;I have tried with just the following to check whitelisting does get logs in&lt;BR /&gt;
whitelist = EventCode=%^(4624)$%&lt;BR /&gt;
and this works so i know there is nothing wrong with that part.&lt;/P&gt;

&lt;H1&gt;Sample Event with EventCode 4624 so you can see what im trying to get&lt;/H1&gt;

&lt;P&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:        SYSTEM&lt;BR /&gt;
    Account Name:       P62134$&lt;BR /&gt;
    Account Domain:     MYDOMAINNET&lt;BR /&gt;
    Logon ID:       0x8f36f8ce&lt;BR /&gt;
    Logon GUID:     {c0780e74-3280-88b1-93aa-e67047cc3842}&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: 127.0.0.1&lt;BR /&gt;
    Source Port:        0&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;/P&gt;

&lt;H1&gt;    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.&lt;/H1&gt;

&lt;P&gt;Thanks im at a loss.&lt;/P&gt;</description>
    <pubDate>Thu, 08 Mar 2018 06:02:21 GMT</pubDate>
    <dc:creator>gerald_contrera</dc:creator>
    <dc:date>2018-03-08T06:02:21Z</dc:date>
    <item>
      <title>How to filter users ending with $ using inputs.conf on a UF v6.6.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-users-ending-with-using-inputs-conf-on-a-UF-v6-6/m-p/335364#M62027</link>
      <description>&lt;P&gt;Hi and thankyou in advance,&lt;/P&gt;

&lt;P&gt;I need to be able to filter EventCode 4624 to NOT includes events with "Account Name" ending in $ (the machine name).&lt;BR /&gt;
OR&lt;BR /&gt;
Possibly with the Security ID: NULL SID&lt;BR /&gt;
However i would prefer with "Account Name" ending in $&lt;/P&gt;

&lt;P&gt;In our environment we use WEF for all workstations which forward to a WEF server which then has a splunk UF to forward to the indexer peers.&lt;/P&gt;

&lt;P&gt;I was under the impression this could be done on the UF if version was 6 or newer (i have v6.6.1)&lt;BR /&gt;
using the inputs.conf?&lt;/P&gt;

&lt;P&gt;I have tried things along the lines of &lt;BR /&gt;
whitelist = EventCode=%^(4624)$% Message="(?:Account Name:).+[?!\$]"&lt;/P&gt;

&lt;P&gt;but this ends up dropping all events.&lt;/P&gt;

&lt;P&gt;I have tried with just the following to check whitelisting does get logs in&lt;BR /&gt;
whitelist = EventCode=%^(4624)$%&lt;BR /&gt;
and this works so i know there is nothing wrong with that part.&lt;/P&gt;

&lt;H1&gt;Sample Event with EventCode 4624 so you can see what im trying to get&lt;/H1&gt;

&lt;P&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:        SYSTEM&lt;BR /&gt;
    Account Name:       P62134$&lt;BR /&gt;
    Account Domain:     MYDOMAINNET&lt;BR /&gt;
    Logon ID:       0x8f36f8ce&lt;BR /&gt;
    Logon GUID:     {c0780e74-3280-88b1-93aa-e67047cc3842}&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: 127.0.0.1&lt;BR /&gt;
    Source Port:        0&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;/P&gt;

&lt;H1&gt;    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.&lt;/H1&gt;

&lt;P&gt;Thanks im at a loss.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Mar 2018 06:02:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-users-ending-with-using-inputs-conf-on-a-UF-v6-6/m-p/335364#M62027</guid>
      <dc:creator>gerald_contrera</dc:creator>
      <dc:date>2018-03-08T06:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to filter users ending with $ using inputs.conf on a UF v6.6.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-users-ending-with-using-inputs-conf-on-a-UF-v6-6/m-p/335365#M62028</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;
at first, equal (=) is a special char for regexes so you have to escape them&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;whitelist = EventCode\=%^(4624)$% Message\="(?:Account Name:).+[?!\$]"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;to avoid that your whitelist is empty&lt;/P&gt;

&lt;P&gt;In addition I'm not sure about your regex but maybe I'm wrongly reading it: please use Code Sample (the button with numbers) to corretly display regexes.&lt;/P&gt;

&lt;P&gt;Anyway, you could tale all events with whitelist&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;whitelist = EventCode\=4624
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;then extract Account_Name using the following regex&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| rex "(?ms)New Logon:.*Account Name:\s+(?&amp;lt;Account_Name&amp;gt;[^ ]*)"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;(test it at &lt;A href="https://regex101.com/r/x14L9N/1"&gt;https://regex101.com/r/x14L9N/1&lt;/A&gt;)&lt;BR /&gt;
and then filter the ones with $ at the end.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| search Account_Name!=*$
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 08 Mar 2018 13:12:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-filter-users-ending-with-using-inputs-conf-on-a-UF-v6-6/m-p/335365#M62028</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2018-03-08T13:12:59Z</dc:date>
    </item>
  </channel>
</rss>

