<?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: ZeroAccess.Gen in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47370#M34825</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Don't forget to check the enable box.&amp;nbsp; The other approach is overriding the default actions globally in the policy for critical events.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Capture-test-policy.JPG" class="jive-image-thumbnail jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/5853_Capture-test-policy.JPG" width="450" /&gt;&lt;/P&gt;&lt;P&gt;Either approach will work but the prior approach (mbutt's) is a more cautious and controlled one. Just keep an eye on critical and high events and decide if you are happy with the default action being taken.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 03 Mar 2013 19:17:59 GMT</pubDate>
    <dc:creator>HITSSEC</dc:creator>
    <dc:date>2013-03-03T19:17:59Z</dc:date>
    <item>
      <title>ZeroAccess.Gen</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47368#M34823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our threat monitor shows a lot of ZeroAccess.Gen Command and Control traffic, type spyware.&amp;nbsp; The default threat action is to alert.&amp;nbsp; I want to either block or drop.&amp;nbsp; What is the best way to block traffic for a specific threat signature but to use defaults on all others with the same severity?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The threat signature categorizes zeroaccess.gen, id 13235, as botnet.&amp;nbsp; Are threat signatures used as part of the behavioral analysis in determining probable botnets?&amp;nbsp; I don't see any correlation between destination IP addresses in the threat log and in the botnet report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Feb 2013 18:05:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47368#M34823</guid>
      <dc:creator>oshcomp</dc:creator>
      <dc:date>2013-02-28T18:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: ZeroAccess.Gen</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47369#M34824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;You can create an exception in you Anti Spyware profiles to block this threat instead of alerting it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="exception.JPG" class="jive-image-thumbnail jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/5789_exception.JPG" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let us know if this resolves your issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Feb 2013 21:50:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47369#M34824</guid>
      <dc:creator>mbutt</dc:creator>
      <dc:date>2013-02-28T21:50:53Z</dc:date>
    </item>
    <item>
      <title>Re: ZeroAccess.Gen</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47370#M34825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Don't forget to check the enable box.&amp;nbsp; The other approach is overriding the default actions globally in the policy for critical events.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Capture-test-policy.JPG" class="jive-image-thumbnail jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/5853_Capture-test-policy.JPG" width="450" /&gt;&lt;/P&gt;&lt;P&gt;Either approach will work but the prior approach (mbutt's) is a more cautious and controlled one. Just keep an eye on critical and high events and decide if you are happy with the default action being taken.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Mar 2013 19:17:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47370#M34825</guid>
      <dc:creator>HITSSEC</dc:creator>
      <dc:date>2013-03-03T19:17:59Z</dc:date>
    </item>
    <item>
      <title>Re: ZeroAccess.Gen</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47371#M34826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Creating an exception for the specific threat seems to work.&amp;nbsp; I am cautious about overriding the defaults for all critical threats.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am considering a third option.&amp;nbsp; I created a rule with a "Threat name" containing the string of the threat and an action of block.&amp;nbsp; A second rule would use specify the default action for everything else.&amp;nbsp; (My example says "alert" and not default.&amp;nbsp; But that is just for testing.)&amp;nbsp; My hope is that the rules will be processed in order.&amp;nbsp; All ZeroAcess.Gen will be blocked.&amp;nbsp; All other threats should use the default action. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Comments?&lt;/P&gt;&lt;P&gt;&lt;IMG alt="" class="jiveImage" src="https://live.paloaltonetworks.com/legacyfs/online/5879_pastedImage_0.png" style="width: 918px; height: 636px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Mar 2013 15:59:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47371#M34826</guid>
      <dc:creator>oshcomp</dc:creator>
      <dc:date>2013-03-04T15:59:43Z</dc:date>
    </item>
    <item>
      <title>Re: ZeroAccess.Gen</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47372#M34827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That would work also.&amp;nbsp; I think either approach accomplishes the end result.&amp;nbsp; My understanding is that it is processed in order top down like firewall rules.&amp;nbsp; The exception in 4.1 is fileblocking profiles. &lt;A _jive_internal="true" href="https://live.paloaltonetworks.com/docs/DOC-2858"&gt;https://live.paloaltonetworks.com/docs/DOC-2858&lt;/A&gt; as a heads up if you go there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Mar 2013 17:51:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/zeroaccess-gen/m-p/47372#M34827</guid>
      <dc:creator>HITSSEC</dc:creator>
      <dc:date>2013-03-04T17:51:08Z</dc:date>
    </item>
  </channel>
</rss>

