<?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: Compare firewall action to track network flow changes in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Compare-firewall-action-to-track-network-flow-changes/m-p/373140#M109755</link>
    <description>&lt;P&gt;It's awfully hard to tell from a long, complex search string like that exactly what is going awry and causing you to get 0 results. But from looking closely at your search string, I do notice this: In the first part of your search, you create fields called &lt;CODE&gt;src_acc&lt;/CODE&gt; and &lt;CODE&gt;dst_acc&lt;/CODE&gt;, and then you try to use those fields in the joined subsearch. However, those fields won't exist in the scope of your joined subsearch, so this part of the subsearch is likely to fail: &lt;CODE&gt;search index=xxx host=yyy sourcetype=opsec action=drop earliest=-1h@h latest=now src=src_acc dst=dst_acc&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Try running that part alone in a search window and see if you get results. If not, that's likely your issue. &lt;/P&gt;</description>
    <pubDate>Thu, 16 Nov 2017 19:32:19 GMT</pubDate>
    <dc:creator>elliotproebstel</dc:creator>
    <dc:date>2017-11-16T19:32:19Z</dc:date>
    <item>
      <title>Compare firewall action to track network flow changes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Compare-firewall-action-to-track-network-flow-changes/m-p/373139#M109754</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;

&lt;P&gt;I'd like to check changes on the Checkpoint firewall logs but I haven't any result :&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;index=xxx host=yyy action=accept earliest=-24h@h latest=-20h@h sourcetype=*opsec&lt;/EM&gt; | eval src_acc=src | eval dst_acc=dst | eval acc_action=action | join src,dst [search index=xxx host=yyy sourcetype=&lt;EM&gt;opsec&lt;/EM&gt; action=drop earliest=-1h@h latest=now src=src_acc dst=dst_acc | eval src_dro=src | eval dst_dro=dst | eval drop_action=action | eval before_time=strftime(_time,"%y/%m/%d %H:%M")] | table _time,src_dro,src_acc,dst_dro,dst_acc,action,before_action,before_time*&lt;/P&gt;

&lt;P&gt;Thanks for your help!&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 16:49:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Compare-firewall-action-to-track-network-flow-changes/m-p/373139#M109754</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2020-09-29T16:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: Compare firewall action to track network flow changes</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Compare-firewall-action-to-track-network-flow-changes/m-p/373140#M109755</link>
      <description>&lt;P&gt;It's awfully hard to tell from a long, complex search string like that exactly what is going awry and causing you to get 0 results. But from looking closely at your search string, I do notice this: In the first part of your search, you create fields called &lt;CODE&gt;src_acc&lt;/CODE&gt; and &lt;CODE&gt;dst_acc&lt;/CODE&gt;, and then you try to use those fields in the joined subsearch. However, those fields won't exist in the scope of your joined subsearch, so this part of the subsearch is likely to fail: &lt;CODE&gt;search index=xxx host=yyy sourcetype=opsec action=drop earliest=-1h@h latest=now src=src_acc dst=dst_acc&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Try running that part alone in a search window and see if you get results. If not, that's likely your issue. &lt;/P&gt;</description>
      <pubDate>Thu, 16 Nov 2017 19:32:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Compare-firewall-action-to-track-network-flow-changes/m-p/373140#M109755</guid>
      <dc:creator>elliotproebstel</dc:creator>
      <dc:date>2017-11-16T19:32:19Z</dc:date>
    </item>
  </channel>
</rss>

