<?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: Filter wineventlog:security by eventcode, Account_Name and Source_Network_Address in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700755#M10449</link>
    <description>&lt;P&gt;Log Name: Security&lt;BR /&gt;EventCode: 4624&lt;BR /&gt;EventType: 0&lt;BR /&gt;ComputerName: MY_ComputerName&lt;BR /&gt;SourceName: Microsoft Windows security auditing.&lt;BR /&gt;Type: Information&lt;BR /&gt;RecordNumber: 93370261535&lt;BR /&gt;Keywords: Audit Success&lt;BR /&gt;TaskCategory: Logon&lt;BR /&gt;OpCode: Info&lt;BR /&gt;Message: An account was successfully logged on.&lt;/P&gt;&lt;P&gt;Subject:&lt;BR /&gt;Security ID: S-1-0-0&lt;BR /&gt;Account Name: -&lt;BR /&gt;Account Domain: -&lt;BR /&gt;Logon ID: 0x0&lt;/P&gt;&lt;P&gt;Logon Information:&lt;BR /&gt;Logon Type: 3&lt;BR /&gt;Restricted Admin Mode: No&lt;BR /&gt;Virtual Account: No&lt;BR /&gt;Elevated Token: Yes&lt;BR /&gt;Impersonation Level: Impersonation&lt;/P&gt;&lt;P&gt;New Logon:&lt;BR /&gt;Security ID: S-1-5-21-877741627-2216037581-1742749770-81699&lt;BR /&gt;Account Name: MY_Account Name&lt;BR /&gt;Account Domain: MY_Account Domain&lt;BR /&gt;Logon ID: 0x2153A91CB&lt;BR /&gt;Linked Logon ID: 0x0&lt;BR /&gt;Network Account Name: -&lt;BR /&gt;Network Account Domain: -&lt;BR /&gt;Logon GUID: {-}&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;Source Network Address: MY_Source Network Address&lt;BR /&gt;Source Port: Port&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.&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.&lt;/P&gt;&lt;P&gt;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. 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 impersonation level field indicates the extent to which a process in the logon session can impersonate.&lt;/P&gt;&lt;P&gt;The authentication information fields provide detailed information about this specific logon request. Logon GUID is a unique identifier that can be used to correlate this event with a KDC event. Transited services indicate which intermediate services have participated in this logon request. Package name indicates which sub-protocol was used among the NTLM protocols. Key length indicates the length of the generated session key. This will be 0 if no session key was requested.&lt;/P&gt;</description>
    <pubDate>Wed, 02 Oct 2024 09:12:11 GMT</pubDate>
    <dc:creator>Alex_Rus</dc:creator>
    <dc:date>2024-10-02T09:12:11Z</dc:date>
    <item>
      <title>Filter wineventlog:security by eventcode, Account_Name and Source_Network_Address</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700640#M10441</link>
      <description>&lt;P&gt;Hi Splunk community!&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to filter events from the Splunk_ta_Windows application by the EventCode, Account_Name and Source_Network_Address fields. Tell me, in what form should props.conf and transform.conf be written and in what folder should they be located?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2024 09:53:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700640#M10441</guid>
      <dc:creator>Alex_Rus</dc:creator>
      <dc:date>2024-10-01T09:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Filter wineventlog:security by eventcode, Account_Name and Source_Network_Address</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700643#M10442</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/271616"&gt;@Alex_Rus&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;let me understand: you want to filter events on the Universal Forwarder, is it correct?&lt;/P&gt;&lt;P&gt;see blacklists and whiteslists in Splunk_TA_Windows documentation that guides you:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf#Event_Log_filtering" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf#Event_Log_filtering&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2024 10:07:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700643#M10442</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-10-01T10:07:21Z</dc:date>
    </item>
    <item>
      <title>Re: Filter wineventlog:security by eventcode, Account_Name and Source_Network_Address</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700646#M10443</link>
      <description>&lt;P&gt;App on deployment-server. I think, filtering by props and transform is better, but maybe I'm wrong)&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2024 10:15:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700646#M10443</guid>
      <dc:creator>Alex_Rus</dc:creator>
      <dc:date>2024-10-01T10:15:06Z</dc:date>
    </item>
    <item>
      <title>Re: Filter wineventlog:security by eventcode, Account_Name and Source_Network_Address</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700647#M10444</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/271616"&gt;@Alex_Rus&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;yes, it's possible modifying inputs.conf on your Splunk_TA_Windows adding whitelists and/or blacklists to filter your events.&lt;/P&gt;&lt;P&gt;Otherwise it's possible to filter events, using props.conf and transfroms.conf on the Indexers following the instrauctions at&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/latest/Forwarding/Routeandfilterdatad#Filter_event_data_and_send_to_queues" target="_blank"&gt;https://docs.splunk.com/Documentation/SplunkCloud/latest/Forwarding/Routeandfilterdatad#Filter_event_data_and_send_to_queues&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If possible it's better the first solution (inputs.conf), otherwise you can use the second one.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2024 10:19:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700647#M10444</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-10-01T10:19:11Z</dc:date>
    </item>
    <item>
      <title>Re: Filter wineventlog:security by eventcode, Account_Name and Source_Network_Address</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700753#M10447</link>
      <description>&lt;P&gt;If I use blacklist, how can I filter by multiple events at once? I need to filter by Account_Name, Source_Network_Address and eventcode. How stanza will look?&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2024 08:26:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700753#M10447</guid>
      <dc:creator>Alex_Rus</dc:creator>
      <dc:date>2024-10-02T08:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: Filter wineventlog:security by eventcode, Account_Name and Source_Network_Address</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700754#M10448</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/271616"&gt;@Alex_Rus&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;you have to find a regex to filter your events, you can test your regex using the regex command.&lt;/P&gt;&lt;P&gt;then put the regex in inputs.conf:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;blacklist = key=regex&lt;/LI-CODE&gt;&lt;P&gt;if you want more help, please share a sample of the logs to filter.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2024 08:47:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700754#M10448</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-10-02T08:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: Filter wineventlog:security by eventcode, Account_Name and Source_Network_Address</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700755#M10449</link>
      <description>&lt;P&gt;Log Name: Security&lt;BR /&gt;EventCode: 4624&lt;BR /&gt;EventType: 0&lt;BR /&gt;ComputerName: MY_ComputerName&lt;BR /&gt;SourceName: Microsoft Windows security auditing.&lt;BR /&gt;Type: Information&lt;BR /&gt;RecordNumber: 93370261535&lt;BR /&gt;Keywords: Audit Success&lt;BR /&gt;TaskCategory: Logon&lt;BR /&gt;OpCode: Info&lt;BR /&gt;Message: An account was successfully logged on.&lt;/P&gt;&lt;P&gt;Subject:&lt;BR /&gt;Security ID: S-1-0-0&lt;BR /&gt;Account Name: -&lt;BR /&gt;Account Domain: -&lt;BR /&gt;Logon ID: 0x0&lt;/P&gt;&lt;P&gt;Logon Information:&lt;BR /&gt;Logon Type: 3&lt;BR /&gt;Restricted Admin Mode: No&lt;BR /&gt;Virtual Account: No&lt;BR /&gt;Elevated Token: Yes&lt;BR /&gt;Impersonation Level: Impersonation&lt;/P&gt;&lt;P&gt;New Logon:&lt;BR /&gt;Security ID: S-1-5-21-877741627-2216037581-1742749770-81699&lt;BR /&gt;Account Name: MY_Account Name&lt;BR /&gt;Account Domain: MY_Account Domain&lt;BR /&gt;Logon ID: 0x2153A91CB&lt;BR /&gt;Linked Logon ID: 0x0&lt;BR /&gt;Network Account Name: -&lt;BR /&gt;Network Account Domain: -&lt;BR /&gt;Logon GUID: {-}&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;Source Network Address: MY_Source Network Address&lt;BR /&gt;Source Port: Port&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.&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.&lt;/P&gt;&lt;P&gt;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. 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 impersonation level field indicates the extent to which a process in the logon session can impersonate.&lt;/P&gt;&lt;P&gt;The authentication information fields provide detailed information about this specific logon request. Logon GUID is a unique identifier that can be used to correlate this event with a KDC event. Transited services indicate which intermediate services have participated in this logon request. Package name indicates which sub-protocol was used among the NTLM protocols. Key length indicates the length of the generated session key. This will be 0 if no session key was requested.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2024 09:12:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700755#M10449</guid>
      <dc:creator>Alex_Rus</dc:creator>
      <dc:date>2024-10-02T09:12:11Z</dc:date>
    </item>
    <item>
      <title>Re: Filter wineventlog:security by eventcode, Account_Name and Source_Network_Address</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700756#M10450</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/271616"&gt;@Alex_Rus&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;please try this regex in the blacklist option,&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;(?ms)EventCode: 4624.*Account Name: MY_Account Name.*Source Network Address: MY_Source Network Address&lt;/LI-CODE&gt;&lt;P&gt;otherwise, please try it in the transpose.conf (on Indexers) to filter events.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2024 09:19:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Filter-wineventlog-security-by-eventcode-Account-Name-and-Source/m-p/700756#M10450</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-10-02T09:19:58Z</dc:date>
    </item>
  </channel>
</rss>

