<?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 Management in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-management/m-p/192456#M625597</link>
    <description>&lt;P&gt;There doesn't seem to be an ideal way to manage the PIX!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As I see it CSPM is great for creating the ACL's but it's slow when you have a large network, plus it doesn't support the newer VPN clients/commands although you can use the Epilogue to work around this. If you issue commands directly on the PIX they tend to get removed next time you approve a new config from CSPM. Also the currnet release (3.1) is the last release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX MC is very new and supports even fewer commands! I can't even import our current PIX because of this. At least you can issue commands directly to the PIX without fear of them being over written.  Wait for a release that supports more commands I suppose.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The best way I can see of managing a PIX at the moment is using PDM and direct command entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are you experiences??&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>Fri, 21 Feb 2020 06:31:03 GMT</pubDate>
    <dc:creator>SteveGodfrey</dc:creator>
    <dc:date>2020-02-21T06:31:03Z</dc:date>
    <item>
      <title>PIX Management</title>
      <link>https://community.cisco.com/t5/network-security/pix-management/m-p/192456#M625597</link>
      <description>&lt;P&gt;There doesn't seem to be an ideal way to manage the PIX!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As I see it CSPM is great for creating the ACL's but it's slow when you have a large network, plus it doesn't support the newer VPN clients/commands although you can use the Epilogue to work around this. If you issue commands directly on the PIX they tend to get removed next time you approve a new config from CSPM. Also the currnet release (3.1) is the last release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX MC is very new and supports even fewer commands! I can't even import our current PIX because of this. At least you can issue commands directly to the PIX without fear of them being over written.  Wait for a release that supports more commands I suppose.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The best way I can see of managing a PIX at the moment is using PDM and direct command entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are you experiences??&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>Fri, 21 Feb 2020 06:31:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-management/m-p/192456#M625597</guid>
      <dc:creator>SteveGodfrey</dc:creator>
      <dc:date>2020-02-21T06:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Management</title>
      <link>https://community.cisco.com/t5/network-security/pix-management/m-p/192457#M625614</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;They are exactly the same....&lt;/P&gt;&lt;P&gt;At the moment I test Solsoft!&lt;/P&gt;&lt;P&gt;Looks fine&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jan 2003 14:18:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-management/m-p/192457#M625614</guid>
      <dc:creator>rgraether</dc:creator>
      <dc:date>2003-01-24T14:18:09Z</dc:date>
    </item>
  </channel>
</rss>

