<?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: Honey pot signature in Custom Signatures</title>
    <link>https://live.paloaltonetworks.com/t5/custom-signatures/honey-pot-signature/m-p/67284#M3</link>
    <description>&lt;P&gt;Good afternoon, Viren!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Given the nature of our custom signature engine, I cannot think of a way to design a signature to accomplish what you are looking for.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, what you are asking for may be possible with a Zone Protection profile under Reconnaissance Protection.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please see this article for reference:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Block-an-IP-for-a-Specific-Period-upon-Detecting-Port/ta-p/65523" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Block-an-IP-for-a-Specific-Period-upon-Detecting-Port/ta-p/65523&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
    <pubDate>Mon, 26 Oct 2015 18:00:47 GMT</pubDate>
    <dc:creator>rcole</dc:creator>
    <dc:date>2015-10-26T18:00:47Z</dc:date>
    <item>
      <title>Honey pot signature</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/honey-pot-signature/m-p/67282#M2</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; I have certain subnets that are currently not in use in our domain, I wanted to ip-block for 30 minutes all ips that access any of these subnets. Is it possible to creat a threat signature for this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; VIREN&lt;/P&gt;</description>
      <pubDate>Mon, 26 Oct 2015 17:19:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/honey-pot-signature/m-p/67282#M2</guid>
      <dc:creator>viren.parasram</dc:creator>
      <dc:date>2015-10-26T17:19:14Z</dc:date>
    </item>
    <item>
      <title>Re: Honey pot signature</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/honey-pot-signature/m-p/67284#M3</link>
      <description>&lt;P&gt;Good afternoon, Viren!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Given the nature of our custom signature engine, I cannot think of a way to design a signature to accomplish what you are looking for.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, what you are asking for may be possible with a Zone Protection profile under Reconnaissance Protection.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please see this article for reference:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Block-an-IP-for-a-Specific-Period-upon-Detecting-Port/ta-p/65523" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Configuration-Articles/How-to-Block-an-IP-for-a-Specific-Period-upon-Detecting-Port/ta-p/65523&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
      <pubDate>Mon, 26 Oct 2015 18:00:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/honey-pot-signature/m-p/67284#M3</guid>
      <dc:creator>rcole</dc:creator>
      <dc:date>2015-10-26T18:00:47Z</dc:date>
    </item>
    <item>
      <title>Re: Honey pot signature</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/honey-pot-signature/m-p/67301#M4</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Thanks for your suggestion, I will look into that. What I've been trying is to set up strict vulneabilities av virus url profiles with default block and applying them to the policy. I have a request for enhancement to allow for block ip at the group level but in the mean time I've added ip block to some brute force matches to get the desired effect. Waiting to see if this works.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;THANKS,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; VIREN&lt;/P&gt;</description>
      <pubDate>Tue, 27 Oct 2015 13:22:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/honey-pot-signature/m-p/67301#M4</guid>
      <dc:creator>viren.parasram</dc:creator>
      <dc:date>2015-10-27T13:22:37Z</dc:date>
    </item>
    <item>
      <title>Re: Honey pot signature</title>
      <link>https://live.paloaltonetworks.com/t5/custom-signatures/honey-pot-signature/m-p/67487#M5</link>
      <description>&lt;P&gt;Viren,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To use custom signatures you need to tirgger on a defined traffic patten based on the contexts you have available for our use when creating a signature. &amp;nbsp;Since you want a honeypot trigger the challenge you would have is what traffic are you going to trigger on? &amp;nbsp;Might I suggest you create a security rule for you honeynet and use a logging profile that can alert you via txt message or email immediately upon being triggered.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thought I would throw that out for your thoughts.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Phil&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Oct 2015 00:17:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/custom-signatures/honey-pot-signature/m-p/67487#M5</guid>
      <dc:creator>HITSSEC</dc:creator>
      <dc:date>2015-10-30T00:17:55Z</dc:date>
    </item>
  </channel>
</rss>

