<?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: How to build an external static lookup table for Firewall ACL auditing to match on dst_port and determine if the port matches an existing ACL rule? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-build-an-external-static-lookup-table-for-Firewall-ACL/m-p/173038#M49626</link>
    <description>&lt;P&gt;Do you already have the lookup working for the matching ones? If yes, just use a &lt;CODE&gt;| fillnull -value "any_any" rule_name&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 20 Oct 2014 23:46:58 GMT</pubDate>
    <dc:creator>musskopf</dc:creator>
    <dc:date>2014-10-20T23:46:58Z</dc:date>
    <item>
      <title>How to build an external static lookup table for Firewall ACL auditing to match on dst_port and determine if the port matches an existing ACL rule?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-build-an-external-static-lookup-table-for-Firewall-ACL/m-p/173037#M49625</link>
      <description>&lt;P&gt;Hello Splunk Answers,&lt;/P&gt;

&lt;P&gt;I am looking to build a static lookup table for Firewall ACL lookup. Essentially, I would like the lookup to match on dst_port and determine if the port matches an existing acl rule name. I have an any-any rule that I'm trying to clean-up and the idea is to have Splunk tell me if the dst_port matches an existing acl rule entry. If no rule match is made, then the connection is permitted via an any-any rule.&lt;/P&gt;

&lt;P&gt;I'm looking to match on dst_port. In this example, traffic connections on 80, 53 would match rule_name like in the example below. &lt;BR /&gt;
fields:&lt;BR /&gt;
dst_port, rule_name&lt;BR /&gt;
80, permit_web&lt;BR /&gt;
53, permit_dns&lt;/P&gt;

&lt;P&gt;The idea is, if traffic connections do not match on a specific entry, then state something like this:&lt;BR /&gt;
dst_port, rule_name&lt;BR /&gt;
8748, any_any&lt;/P&gt;

&lt;P&gt;I appreciate the assistance.&lt;BR /&gt;
-ktang&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 17:57:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-build-an-external-static-lookup-table-for-Firewall-ACL/m-p/173037#M49625</guid>
      <dc:creator>ktang</dc:creator>
      <dc:date>2020-09-28T17:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to build an external static lookup table for Firewall ACL auditing to match on dst_port and determine if the port matches an existing ACL rule?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-build-an-external-static-lookup-table-for-Firewall-ACL/m-p/173038#M49626</link>
      <description>&lt;P&gt;Do you already have the lookup working for the matching ones? If yes, just use a &lt;CODE&gt;| fillnull -value "any_any" rule_name&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Oct 2014 23:46:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-build-an-external-static-lookup-table-for-Firewall-ACL/m-p/173038#M49626</guid>
      <dc:creator>musskopf</dc:creator>
      <dc:date>2014-10-20T23:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: How to build an external static lookup table for Firewall ACL auditing to match on dst_port and determine if the port matches an existing ACL rule?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-build-an-external-static-lookup-table-for-Firewall-ACL/m-p/173039#M49627</link>
      <description>&lt;P&gt;That worked! thanks musskopf&lt;/P&gt;</description>
      <pubDate>Fri, 14 Nov 2014 19:20:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-build-an-external-static-lookup-table-for-Firewall-ACL/m-p/173039#M49627</guid>
      <dc:creator>ktang</dc:creator>
      <dc:date>2014-11-14T19:20:15Z</dc:date>
    </item>
  </channel>
</rss>

