<?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 When you backup the in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592548#M205874</link>
    <description>&lt;P&gt;When you backup the certificates using the ASDM tool, it creates a &lt;A href="http://en.wikipedia.org/wiki/PKCS_12"&gt;PKCS12 file&lt;/A&gt;. That file format includes both the certificate and associated private key. Assuming that's your default RSA key (which it usually is but doesn't need to be) you &amp;nbsp;will have it there.&lt;/P&gt;&lt;P&gt;If you didn't use your RSA key to sign your self-signed certificates (or your CSR in the event of 3rd party certificates) then you won't have a backup copy of it. But&amp;nbsp;if it's not tied to any certificates, it's no&amp;nbsp;real loss to recreate it fresh on a new unit in the event of hardware replacement.&lt;/P&gt;</description>
    <pubDate>Fri, 17 Oct 2014 19:55:40 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2014-10-17T19:55:40Z</dc:date>
    <item>
      <title>ASA backup and restore</title>
      <link>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592545#M205871</link>
      <description>&lt;P&gt;What is the process to backup the configurations from a bad ASA to a new one (same model)?&lt;/P&gt;&lt;P&gt;I am asking specifically for certificates and keys for VPNs.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:57:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592545#M205871</guid>
      <dc:creator>miras</dc:creator>
      <dc:date>2019-03-12T04:57:11Z</dc:date>
    </item>
    <item>
      <title>If you use ASDM, the "Tools &gt;</title>
      <link>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592546#M205872</link>
      <description>&lt;P&gt;If you use ASDM, the "Tools &amp;gt; Backup configurations" menu choice allows you to backup not only the configuration file but identity certificates, plain text keys, etc. You can also&amp;nbsp;select only those bits if that's all you want.&lt;/P&gt;&lt;P&gt;Note also that if you pull your configuration from the cli using "more system:running-config" you will get plaintext snmp community strings (v1 and v2 but not v3 credentials) and pre-shared keys.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Oct 2014 18:49:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592546#M205872</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-17T18:49:43Z</dc:date>
    </item>
    <item>
      <title>What about the RSA keys? are</title>
      <link>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592547#M205873</link>
      <description>&lt;P&gt;What about the RSA keys? are those backed up and restored as well?&lt;/P&gt;&lt;P&gt;Another question, kinda off the topic is that, what if there is an IPS module installed in it?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Oct 2014 19:03:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592547#M205873</guid>
      <dc:creator>miras</dc:creator>
      <dc:date>2014-10-17T19:03:24Z</dc:date>
    </item>
    <item>
      <title>When you backup the</title>
      <link>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592548#M205874</link>
      <description>&lt;P&gt;When you backup the certificates using the ASDM tool, it creates a &lt;A href="http://en.wikipedia.org/wiki/PKCS_12"&gt;PKCS12 file&lt;/A&gt;. That file format includes both the certificate and associated private key. Assuming that's your default RSA key (which it usually is but doesn't need to be) you &amp;nbsp;will have it there.&lt;/P&gt;&lt;P&gt;If you didn't use your RSA key to sign your self-signed certificates (or your CSR in the event of 3rd party certificates) then you won't have a backup copy of it. But&amp;nbsp;if it's not tied to any certificates, it's no&amp;nbsp;real loss to recreate it fresh on a new unit in the event of hardware replacement.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Oct 2014 19:55:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592548#M205874</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-17T19:55:40Z</dc:date>
    </item>
    <item>
      <title>By backing up the startup</title>
      <link>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592549#M205875</link>
      <description>&lt;P&gt;By backing up the startup config of the existing ASA and restoring it to the new one, does that also backup and restore the RSA keys or do i have to recreate them again?&lt;/P&gt;&lt;P&gt;And if i have to recreate them, how do i know what modulus has been used?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Oct 2014 20:59:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592549#M205875</guid>
      <dc:creator>miras</dc:creator>
      <dc:date>2014-10-17T20:59:03Z</dc:date>
    </item>
    <item>
      <title>As I noted earlier, only when</title>
      <link>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592550#M205878</link>
      <description>&lt;P&gt;As I noted earlier, only when you backup certificates will it restore the RSA keys. The running-config does not include the RSA key.&lt;/P&gt;&lt;P&gt;If the current key&amp;nbsp;has not been used to sign any certificates, you can recreate it as you need on any new hardware or even create it anew on the current hardware - for instance if the previous admin neglected to use a 2048-bit key as may be required for a current audit or just just to keep up with best practices.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Oct 2014 21:03:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592550#M205878</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-17T21:03:06Z</dc:date>
    </item>
    <item>
      <title>The thing is that, how do i</title>
      <link>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592551#M205879</link>
      <description>&lt;P&gt;The thing is that, how do i recreate the exact copy of RSA? Because when we generate RSA, it has some inputs, like domain name, modulus size, etc.&lt;/P&gt;&lt;P&gt;How do i check modulus size so i can recreate the exact copy of RSA so i can use to sign my certificates that i already backed up.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Oct 2014 21:12:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592551#M205879</guid>
      <dc:creator>miras</dc:creator>
      <dc:date>2014-10-17T21:12:11Z</dc:date>
    </item>
    <item>
      <title>Backup the certificates using</title>
      <link>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592552#M205880</link>
      <description>&lt;P&gt;Backup the certificates using the ASDM backup tool. That will combine the certificate itself along with the signing RSA private&amp;nbsp;key. When you restore a&amp;nbsp;certificate&amp;nbsp;using the backed up PKCS file, it will restore both items.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Oct 2014 21:14:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-backup-and-restore/m-p/2592552#M205880</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-10-17T21:14:46Z</dc:date>
    </item>
  </channel>
</rss>

