<?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 PIX 520 syslog in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-520-syslog/m-p/522130#M500435</link>
    <description>&lt;P&gt;We have a pix 520 that I dump the syslog to Pix Firewall syslog server for record keeping. Is there a way to analyze the logs to find potential worms that might be talking through workstations to my network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 08:57:49 GMT</pubDate>
    <dc:creator>ethutchinson</dc:creator>
    <dc:date>2020-02-21T08:57:49Z</dc:date>
    <item>
      <title>PIX 520 syslog</title>
      <link>https://community.cisco.com/t5/network-security/pix-520-syslog/m-p/522130#M500435</link>
      <description>&lt;P&gt;We have a pix 520 that I dump the syslog to Pix Firewall syslog server for record keeping. Is there a way to analyze the logs to find potential worms that might be talking through workstations to my network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:57:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-520-syslog/m-p/522130#M500435</guid>
      <dc:creator>ethutchinson</dc:creator>
      <dc:date>2020-02-21T08:57:49Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 520 syslog</title>
      <link>https://community.cisco.com/t5/network-security/pix-520-syslog/m-p/522131#M500436</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I feel you can use this decoder tool to find out the exact reason and possible solution for known error logs..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/cgi-bin/Support/Errordecoder/index.cgi?action=search&amp;amp;locale=en&amp;amp;index=pixos&amp;amp;query=&amp;amp;counter=0&amp;amp;paging=5&amp;amp;links=reference&amp;amp;sa=Submit" target="_blank"&gt;http://www.cisco.com/cgi-bin/Support/Errordecoder/index.cgi?action=search&amp;amp;locale=en&amp;amp;index=pixos&amp;amp;query=&amp;amp;counter=0&amp;amp;paging=5&amp;amp;links=reference&amp;amp;sa=Submit&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also you can make use of security advisory notices to find out about known worms and the mitigation path..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/products_security_advisories_listing.html" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/products_security_advisories_listing.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2006 05:13:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-520-syslog/m-p/522131#M500436</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2006-06-14T05:13:41Z</dc:date>
    </item>
  </channel>
</rss>

