<?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: Threat Defense Model Migration in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371311#M1124518</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1494970"&gt;@davparker&lt;/a&gt;&amp;nbsp;if the FTD is managed by an FMC you can just configure the basic to establish network connectivity and then apply the same policies already in use on the existing firewall.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Feb 2026 17:57:09 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2026-02-19T17:57:09Z</dc:date>
    <item>
      <title>Threat Defense Model Migration</title>
      <link>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371272#M1124515</link>
      <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;Does anyone have experience using the Threat Defense Model Migration? We are migrating from a 2110 in HA to a 3105 in HA. We are debating whether to do this manually or is it less error prone to use the migration utility built into FMC?&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;David&lt;/P&gt;</description>
      <pubDate>Thu, 19 Feb 2026 16:07:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371272#M1124515</guid>
      <dc:creator>davparker</dc:creator>
      <dc:date>2026-02-19T16:07:38Z</dc:date>
    </item>
    <item>
      <title>Re: Threat Defense Model Migration</title>
      <link>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371303#M1124516</link>
      <description>&lt;P&gt;check the model migration guide :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/migration/threat-defense/b_secure-firewall-threat-defense-model-migration.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/migration/threat-defense/b_secure-firewall-threat-defense-model-migration.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Feb 2026 17:44:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371303#M1124516</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2026-02-19T17:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: Threat Defense Model Migration</title>
      <link>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371309#M1124517</link>
      <description>&lt;P&gt;Thanks, I have the guide. I just have not tried this yet. If it works well, it looks like it would be a time saver. If it tends too be buggy, I&amp;nbsp; think I'd rather manually do the migration to avoid delays with opening TAC cases.&lt;/P&gt;&lt;P&gt;Thannks,&lt;BR /&gt;David&lt;/P&gt;</description>
      <pubDate>Thu, 19 Feb 2026 17:54:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371309#M1124517</guid>
      <dc:creator>davparker</dc:creator>
      <dc:date>2026-02-19T17:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: Threat Defense Model Migration</title>
      <link>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371311#M1124518</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1494970"&gt;@davparker&lt;/a&gt;&amp;nbsp;if the FTD is managed by an FMC you can just configure the basic to establish network connectivity and then apply the same policies already in use on the existing firewall.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Feb 2026 17:57:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371311#M1124518</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2026-02-19T17:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: Threat Defense Model Migration</title>
      <link>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371315#M1124519</link>
      <description>&lt;P&gt;Thanks, it is. I'm leaning this way. Seems like the outcome might be more predictable. I've stood up enough of these lately. Also I can't find much of anything on user's experience using the Migrate tool. If it could migrate certificates I'd take a crack at it, but it&amp;nbsp; looks like we'll need to re-enroll those no matter which way we go.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Feb 2026 18:07:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371315#M1124519</guid>
      <dc:creator>davparker</dc:creator>
      <dc:date>2026-02-19T18:07:11Z</dc:date>
    </item>
    <item>
      <title>Re: Threat Defense Model Migration</title>
      <link>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371317#M1124520</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1494970"&gt;@davparker&lt;/a&gt;&amp;nbsp;it's simple enough to export/import the certificates - or better create new if internally signed certificate. Most of the time I prefer manual migrations (any vendor) as it's a good chance to get tweak the implementation and not migrate poor configuration.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Feb 2026 18:17:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/threat-defense-model-migration/m-p/5371317#M1124520</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2026-02-19T18:17:28Z</dc:date>
    </item>
  </channel>
</rss>

