<?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: Firewall configuration provided as a .txt file? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4921650#M1104173</link>
    <description>&lt;P&gt;This is the API GET output for the FTD configuration.&amp;nbsp; Technically you could just change what you need to in these files and then send them vial a POST call to the new FTD and you are good to go.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Sep 2023 20:41:04 GMT</pubDate>
    <dc:creator>Marius Gunnerud</dc:creator>
    <dc:date>2023-09-11T20:41:04Z</dc:date>
    <item>
      <title>Firewall configuration provided as a .txt file?</title>
      <link>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4921622#M1104168</link>
      <description>&lt;P&gt;I have a customer who wants a new site to have the same firepower firewall configuration (except the site-specific items) as another properly functioning site.&amp;nbsp; When asked for the firewall configuration information, they sent a 34MB .txt file that looks like what I have pasted below.&amp;nbsp; I haven't seen this before, and the other network engineer on my team is also confused by this.&amp;nbsp; Can anyone help?&lt;BR /&gt;&lt;BR /&gt;{"metadata":{"Exported version":"6.6.5-81","Generated on":"08-24-2023","Masked":true}}&lt;BR /&gt;{"version":"cllh35qmc4bq2","hardwareName":"Ethernet1/3","monitorInterface":true,"ipv4":{"ipType":"STATIC","defaultRouteUsingDHCP":false,"dhcp":false,"addressNull":true,"type":"interfaceipv4"},"ipv6":{"enabled":false,"autoConfig":false,"dhcpForManagedConfig":false,"dhcpForOtherConfig":false,"enableRA":false,"dadAttempts":1,"linkLocalAddress":&lt;/P&gt;</description>
      <pubDate>Mon, 11 Sep 2023 19:44:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4921622#M1104168</guid>
      <dc:creator>acfreema</dc:creator>
      <dc:date>2023-09-11T19:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall configuration provided as a .txt file?</title>
      <link>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4921650#M1104173</link>
      <description>&lt;P&gt;This is the API GET output for the FTD configuration.&amp;nbsp; Technically you could just change what you need to in these files and then send them vial a POST call to the new FTD and you are good to go.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Sep 2023 20:41:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4921650#M1104173</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2023-09-11T20:41:04Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall configuration provided as a .txt file?</title>
      <link>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4921955#M1104179</link>
      <description>&lt;P&gt;Assuming they are managed by the same FMC, you could also just onboard the new firewall with a basic config, add the full set of device specific details in FMC and then associate the same Access Control, NAT and platform policies to the new firewall.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Sep 2023 09:50:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4921955#M1104179</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2023-09-12T09:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall configuration provided as a .txt file?</title>
      <link>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4922043#M1104184</link>
      <description>&lt;P&gt;Thanks guys, that helps, but I'm still really confused.&amp;nbsp; The first hurdle is "change what you need".&amp;nbsp; This is my first exposure to a firepower firewall configuration, and without any contact with the firewall from which this configuration was pulled, so I don't know what would need to be changed.&amp;nbsp; How do I find what I need to change?&amp;nbsp; How is it arranged?&amp;nbsp; After applying this configuration, would the firewall still be accessible to make changes that I didn't make prior to uploading the configuration?&amp;nbsp; If it matters, these are both using FTD.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Sep 2023 12:29:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4922043#M1104184</guid>
      <dc:creator>acfreema</dc:creator>
      <dc:date>2023-09-12T12:29:26Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall configuration provided as a .txt file?</title>
      <link>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4922065#M1104186</link>
      <description>&lt;P&gt;The answers to your questions depends on how you intend to configure the firewall.&amp;nbsp; Through the GUI or through API.&amp;nbsp; If you are going to configure via API I suggest looking at the API page and then look at the POST examples for each area you are going to configure.&amp;nbsp; In FDM there is a link to the API page on the dashboard and in FMC add /api/api-explorer to the end of the FMC IP.&lt;/P&gt;
&lt;P&gt;FDM and FMC APIs have slight differences in naming standards but for the most part they have the same structure.&lt;/P&gt;
&lt;P&gt;So, this will not be a plain copy paste into the CLI, if you intend to use APIs you will need to do a separate API call for each configuration (interfaces, security zones, objects, NAT, Routing, etc.).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are not used to using APIs and programming this should not be a big deal, if not it looks more difficult than it actually is.&amp;nbsp; It might take a little time to get used to the structure of the APIs but once that is down i goes like a breeze.&lt;/P&gt;
&lt;P&gt;You can also have a look at the developer page for some insight into the firewall APIs.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://developer.cisco.com/secure-firewall/" target="_blank"&gt;https://developer.cisco.com/secure-firewall/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Sep 2023 13:16:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-configuration-provided-as-a-txt-file/m-p/4922065#M1104186</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2023-09-12T13:16:10Z</dc:date>
    </item>
  </channel>
</rss>

