<?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 Splunk Enterprise Security: SA-NetworkProtection -- Can we update a CSV to include src_up and dest_ip columns? in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-SA-NetworkProtection-Can-we-update-a/m-p/318851#M2930</link>
    <description>&lt;P&gt;Pondering if the prohibited_traffic.csv lookup used by SA-NetworkProtection in Enterprise Security could be updated to have the src_ip and dest_ip columns to allow me to define acceptable usage of a port currently deemed prohibited.  &lt;/P&gt;

&lt;P&gt;Current header for the csv file is: &lt;/P&gt;

&lt;P&gt;transport,src_category,dest_category,src_pci_domain,dest_pci_domain,dest_port,is_prohibited,is_secure,note&lt;/P&gt;

&lt;P&gt;Proposing: &lt;/P&gt;

&lt;P&gt;transport,src_ip,dest_ip,src_category,dest_category,src_pci_domain,dest_pci_domain,dest_port,is_prohibited,is_secure,note&lt;/P&gt;

&lt;P&gt;Setup the example: &lt;/P&gt;

&lt;P&gt;Let’s say we have two systems on our internal network, 172.1.1.15 (desktop) and 172.1.2.15(server).  Bob, who uses the desktop 172.1.1.15 RDP’s to 172.1.2.15 once a month to do a report. Under the current configuration, Bob’s RDP access generates a notable event.  We want to be able to put acceptable usage of a protocol in the lookup, so traffic that notable events are not created for acceptable usage.  Also, would using wildcards possibly work on the src_ip and dest_ip values (example 172.1.1.0/24 or 172.1.1.*).&lt;/P&gt;

&lt;P&gt;Example of default prohibited port definition: &lt;/P&gt;

&lt;P&gt;tcp,unknown,*,,,3389,true,,deny_inbound_rdp_from_unknown&lt;/P&gt;

&lt;P&gt;Example of proposed: &lt;/P&gt;

&lt;P&gt;tcp,172.1.1.15,172.1.2.15,unknown,*,,,3389,false,,prohibit_inbound_rdp_from_unknown&lt;/P&gt;

&lt;P&gt;Please let me know if more information is needed or there is a better way to address this item.  Thank you in advance for your time.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 16:21:10 GMT</pubDate>
    <dc:creator>donaldwayne1975</dc:creator>
    <dc:date>2020-09-29T16:21:10Z</dc:date>
    <item>
      <title>Splunk Enterprise Security: SA-NetworkProtection -- Can we update a CSV to include src_up and dest_ip columns?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-SA-NetworkProtection-Can-we-update-a/m-p/318851#M2930</link>
      <description>&lt;P&gt;Pondering if the prohibited_traffic.csv lookup used by SA-NetworkProtection in Enterprise Security could be updated to have the src_ip and dest_ip columns to allow me to define acceptable usage of a port currently deemed prohibited.  &lt;/P&gt;

&lt;P&gt;Current header for the csv file is: &lt;/P&gt;

&lt;P&gt;transport,src_category,dest_category,src_pci_domain,dest_pci_domain,dest_port,is_prohibited,is_secure,note&lt;/P&gt;

&lt;P&gt;Proposing: &lt;/P&gt;

&lt;P&gt;transport,src_ip,dest_ip,src_category,dest_category,src_pci_domain,dest_pci_domain,dest_port,is_prohibited,is_secure,note&lt;/P&gt;

&lt;P&gt;Setup the example: &lt;/P&gt;

&lt;P&gt;Let’s say we have two systems on our internal network, 172.1.1.15 (desktop) and 172.1.2.15(server).  Bob, who uses the desktop 172.1.1.15 RDP’s to 172.1.2.15 once a month to do a report. Under the current configuration, Bob’s RDP access generates a notable event.  We want to be able to put acceptable usage of a protocol in the lookup, so traffic that notable events are not created for acceptable usage.  Also, would using wildcards possibly work on the src_ip and dest_ip values (example 172.1.1.0/24 or 172.1.1.*).&lt;/P&gt;

&lt;P&gt;Example of default prohibited port definition: &lt;/P&gt;

&lt;P&gt;tcp,unknown,*,,,3389,true,,deny_inbound_rdp_from_unknown&lt;/P&gt;

&lt;P&gt;Example of proposed: &lt;/P&gt;

&lt;P&gt;tcp,172.1.1.15,172.1.2.15,unknown,*,,,3389,false,,prohibit_inbound_rdp_from_unknown&lt;/P&gt;

&lt;P&gt;Please let me know if more information is needed or there is a better way to address this item.  Thank you in advance for your time.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 16:21:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-SA-NetworkProtection-Can-we-update-a/m-p/318851#M2930</guid>
      <dc:creator>donaldwayne1975</dc:creator>
      <dc:date>2020-09-29T16:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security: SA-NetworkProtection -- Can we update a CSV to include src_up and dest_ip columns?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-SA-NetworkProtection-Can-we-update-a/m-p/318852#M2931</link>
      <description>&lt;P&gt;You can add additional fields to extend the capability of the lookups in ES. If/when you do this you will also want to do a couple additional things using the rough outline provided below: &lt;BR /&gt;
1. Configure additional Fields in lookups and schedule lookup creation - &lt;A href="http://docs.splunk.com/Documentation/ES/4.7.3/Admin/Createsearchdrivenlookups"&gt;http://docs.splunk.com/Documentation/ES/4.7.3/Admin/Createsearchdrivenlookups&lt;/A&gt; &lt;BR /&gt;
2. Configure Correlations searches to leverage lookup and scheduled Correlations Searches to create Notable Events -&lt;BR /&gt;
 &lt;A href="http://docs.splunk.com/Documentation/ES/4.7.3/Admin/Configurecorrelationsearches"&gt;http://docs.splunk.com/Documentation/ES/4.7.3/Admin/Configurecorrelationsearches&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 21 Oct 2017 17:15:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-SA-NetworkProtection-Can-we-update-a/m-p/318852#M2931</guid>
      <dc:creator>nsmalley_splunk</dc:creator>
      <dc:date>2017-10-21T17:15:37Z</dc:date>
    </item>
  </channel>
</rss>

