<?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: monitor changes to a PIX config in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/monitor-changes-to-a-pix-config/m-p/627955#M1027005</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We do it via syslog. Works well, but the biggest problem is figuring out who did it!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Feb 2007 15:08:24 GMT</pubDate>
    <dc:creator>Collin Clark</dc:creator>
    <dc:date>2007-02-02T15:08:24Z</dc:date>
    <item>
      <title>monitor changes to a PIX config</title>
      <link>https://community.cisco.com/t5/network-security/monitor-changes-to-a-pix-config/m-p/627954#M1027004</link>
      <description>&lt;P&gt;Is there an easy way to monitor what changes have been made to a PIX config? Maybe via syslog ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 09:28:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-changes-to-a-pix-config/m-p/627954#M1027004</guid>
      <dc:creator>kevburgess</dc:creator>
      <dc:date>2019-03-11T09:28:19Z</dc:date>
    </item>
    <item>
      <title>Re: monitor changes to a PIX config</title>
      <link>https://community.cisco.com/t5/network-security/monitor-changes-to-a-pix-config/m-p/627955#M1027005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We do it via syslog. Works well, but the biggest problem is figuring out who did it!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Feb 2007 15:08:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-changes-to-a-pix-config/m-p/627955#M1027005</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2007-02-02T15:08:24Z</dc:date>
    </item>
    <item>
      <title>Re: monitor changes to a PIX config</title>
      <link>https://community.cisco.com/t5/network-security/monitor-changes-to-a-pix-config/m-p/627956#M1027006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What level are you syslogging? Informational?&lt;/P&gt;&lt;P&gt;I find that the logs are huge if I go that low...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Feb 2007 15:14:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-changes-to-a-pix-config/m-p/627956#M1027006</guid>
      <dc:creator>kevburgess</dc:creator>
      <dc:date>2007-02-02T15:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: monitor changes to a PIX config</title>
      <link>https://community.cisco.com/t5/network-security/monitor-changes-to-a-pix-config/m-p/627957#M1027007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our security policy (actually security people) require debug! Yup over a gig of syslog data a day for one firewall. Obviously we use a script to parse out the commands entered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Feb 2007 15:24:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/monitor-changes-to-a-pix-config/m-p/627957#M1027007</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2007-02-02T15:24:15Z</dc:date>
    </item>
  </channel>
</rss>

