<?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: Pix config backup in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78608#M652405</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The point here is to do this AUTOMATICALLY.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Sep 2002 13:16:35 GMT</pubDate>
    <dc:creator>dharp</dc:creator>
    <dc:date>2002-09-18T13:16:35Z</dc:date>
    <item>
      <title>Pix config backup</title>
      <link>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78604#M652401</link>
      <description>&lt;P&gt;What methods are people using to automatically backup PIX configs?  I'm putting together a script to SSH to the PIX and issue a 'write net' to a predefined tftp server.  However, this is difficult and there are some issues in doing this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are others doing?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:13:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78604#M652401</guid>
      <dc:creator>dharp</dc:creator>
      <dc:date>2020-02-21T06:13:11Z</dc:date>
    </item>
    <item>
      <title>Re: Pix config backup</title>
      <link>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78605#M652402</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What you're doing is probably the best way, there's really not many ways to do it.  Keep in mind that when you do a "write net" I believe the config is sent in the clear over the network , regardless of whether the "write net" was issued via an SSH or a Telnet session.  I wouldn't recommend doing this to an external TFTP server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Really there's not many people doing this, at least not what I've heard.  The new PIX Management Console due out soon will allow you to do this more securely, but you probably don't want to spend 000's of dollars just for that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could also use PDM to get the config, although it's not automatic it is more secure cause the config will be transferred over the &lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt; connection.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Sep 2002 06:19:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78605#M652402</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2002-09-03T06:19:37Z</dc:date>
    </item>
    <item>
      <title>Re: Pix config backup</title>
      <link>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78606#M652403</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just connect to my firewall, do a copy, and paste it into a document on a secured server.  If you have to restore your config, then all you have to do is copy the config again, and paste it into the command line.&lt;/P&gt;&lt;P&gt;If you do it via SSH, then your security is only as good as your server you store it on.&lt;/P&gt;&lt;P&gt;Thoughts, comments?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;&lt;EDITED by="" user=""&gt;&amp;gt;&amp;gt;&lt;/EDITED&gt;&lt;/P&gt;&lt;P&gt;Ooops, sorry ... I didn't see the part of "automatically".  This wouldn't work too well.  My apologies&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Sep 2002 00:06:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78606#M652403</guid>
      <dc:creator>apaxson</dc:creator>
      <dc:date>2002-09-05T00:06:09Z</dc:date>
    </item>
    <item>
      <title>Re: Pix config backup</title>
      <link>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78607#M652404</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To do tftp from a pix, you need tftp server at inside interface. Then do tftp as usual.&lt;/P&gt;&lt;P&gt;--ejaj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Sep 2002 13:01:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78607#M652404</guid>
      <dc:creator>ejaj</dc:creator>
      <dc:date>2002-09-18T13:01:01Z</dc:date>
    </item>
    <item>
      <title>Re: Pix config backup</title>
      <link>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78608#M652405</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The point here is to do this AUTOMATICALLY.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Sep 2002 13:16:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-config-backup/m-p/78608#M652405</guid>
      <dc:creator>dharp</dc:creator>
      <dc:date>2002-09-18T13:16:35Z</dc:date>
    </item>
  </channel>
</rss>

