<?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 Signature Update S842.0  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029138#M42734</link>
    <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;Signature Update S842.0&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;That's a pretty old signature file. &amp;nbsp;The latest one is S987 (Release Date 22 June 2017).&lt;/P&gt;
&lt;P&gt;Signature file &lt;A href="https://tools.cisco.com/security/center/content/CiscoSecurityResponse/cisco-sr-20170515"&gt;S982 &lt;/A&gt;has been released to address WannaCry/WannaCrypt so I'd say signature file S842 is not covered. &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 29 Jun 2017 00:37:27 GMT</pubDate>
    <dc:creator>Leo Laohoo</dc:creator>
    <dc:date>2017-06-29T00:37:27Z</dc:date>
    <item>
      <title>IPS | Petya Ransomware</title>
      <link>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029135#M42731</link>
      <description>&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: 'courier new', courier, monospace; color: #000000;"&gt;Hello Team,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: 'courier new', courier, monospace; color: #000000;"&gt;We would like to know what signature we need to update on our IPS for us to mitigate the petya ransomware?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:52:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029135#M42731</guid>
      <dc:creator>John</dc:creator>
      <dc:date>2019-03-10T13:52:18Z</dc:date>
    </item>
    <item>
      <title>New Ransomware Variant</title>
      <link>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029136#M42732</link>
      <description>&lt;H3 itemprop="name"&gt;&lt;A href="http://blog.talosintelligence.com/2017/06/worldwide-ransomware-variant.html" rel="nofollow"&gt;New Ransomware Variant "Nyetya" Compromises Systems Worldwide&lt;/A&gt;&lt;/H3&gt;</description>
      <pubDate>Wed, 28 Jun 2017 21:02:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029136#M42732</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2017-06-28T21:02:31Z</dc:date>
    </item>
    <item>
      <title>Hello Leo,</title>
      <link>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029137#M42733</link>
      <description>&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: 'courier new', courier, monospace;"&gt;Hello Leo,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: 'courier new', courier, monospace;"&gt;How about in IPS we're using Cisco Intrusion Prevention System, Version 7.1(8p1)E4&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: 'courier new', courier, monospace;"&gt;Host:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: 'courier new', courier, monospace;"&gt; Realm Keys key1.0&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: 'courier new', courier, monospace;"&gt;Signature Definition:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: 'courier new', courier, monospace;"&gt; Signature Update S842.0&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: 'courier new', courier, monospace;"&gt;OS Version: 2.6.29.1&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: 'courier new', courier, monospace;"&gt;Platform: ASA5525-IPS&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: 'courier new', courier, monospace;"&gt;what version of signature that we need to upgrade for us to mitigate na ransomware?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2017 23:22:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029137#M42733</guid>
      <dc:creator>John</dc:creator>
      <dc:date>2017-06-28T23:22:13Z</dc:date>
    </item>
    <item>
      <title>Signature Update S842.0 </title>
      <link>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029138#M42734</link>
      <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;Signature Update S842.0&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;That's a pretty old signature file. &amp;nbsp;The latest one is S987 (Release Date 22 June 2017).&lt;/P&gt;
&lt;P&gt;Signature file &lt;A href="https://tools.cisco.com/security/center/content/CiscoSecurityResponse/cisco-sr-20170515"&gt;S982 &lt;/A&gt;has been released to address WannaCry/WannaCrypt so I'd say signature file S842 is not covered. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 00:37:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029138#M42734</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2017-06-29T00:37:27Z</dc:date>
    </item>
    <item>
      <title>Hi John </title>
      <link>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029139#M42735</link>
      <description>&lt;P&gt;Hi John&amp;nbsp;&lt;/P&gt;
&lt;P&gt;please see below link and snort rules you can enable, depending on your base policy the rules may or may not be enabled.&lt;/P&gt;
&lt;P&gt;On Firesight Manager you can enable these rules to drop / alert or just alert (via policies &amp;gt; intrusion)&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;http://blog.talosintelligence.com/2017/06/worldwide-ransomware-variant.html &amp;nbsp; &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;42944 - OS-WINDOWS Microsoft Windows SMB remote code execution attempt&lt;BR /&gt;42340 - OS-WINDOWS Microsoft Windows SMB anonymous session IPC share access attempt&lt;BR /&gt;41984 - OS-WINDOWS Microsoft Windows SMBv1 identical MID and FID type confusion attempt&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;BR /&gt;5718 - OS-WINDOWS Microsoft Windows SMB-DS Trans unicode Max Param/Count OS-WINDOWS attempt&lt;BR /&gt;1917 - INDICATOR-SCAN UPnP service discover attempt&lt;BR /&gt;5730 - OS-WINDOWS Microsoft Windows SMB-DS Trans Max Param OS-WINDOWS attempt&lt;BR /&gt;26385 - FILE-EXECUTABLE Microsoft Windows executable file save onto SMB share attempt&lt;BR /&gt;43370 - NETBIOS DCERPC possible wmi remote process launch&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jul 2017 09:05:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029139#M42735</guid>
      <dc:creator>#TCN</dc:creator>
      <dc:date>2017-07-03T09:05:08Z</dc:date>
    </item>
    <item>
      <title>@Jim B  </title>
      <link>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029140#M42736</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://supportforums.cisco.com/users/boydjames"&gt;boydjames&lt;/A&gt;&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Snort rules are for FirePOWER appliances or modules in the Cisco world.&lt;/P&gt;
&lt;P&gt;The OP indicated he is running the classic Cisco IPS (with a VERY old signature file).&lt;/P&gt;
&lt;P&gt;Thus Leo's advice was correct.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jul 2017 13:41:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-petya-ransomware/m-p/3029140#M42736</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-07-03T13:41:01Z</dc:date>
    </item>
  </channel>
</rss>

