<?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: Best Practices for acquisition in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/362894#M88306</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Depending on the size of the other networks, perhaps changing the IP subnets that the 'smallest' one is using? I know it sounds daunting, but with DHCP and planning it can be quit easy (yep had to do this a few times in the past).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good luck.&lt;/P&gt;</description>
    <pubDate>Thu, 12 Nov 2020 23:05:24 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2020-11-12T23:05:24Z</dc:date>
    <item>
      <title>Best Practices for acquisition</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/361749#M88220</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our company has recently made several acquisitions. All of them have non-palo alto firewalls. We will be migrating each of non-palo firewalls to our palos.&lt;/P&gt;&lt;P&gt;Now, for migrating the rules, we are using expedition.&amp;nbsp;&lt;/P&gt;&lt;P&gt;But, some of them have overlapping IP addressing. We are planning to resolve that problem with NAT.&lt;/P&gt;&lt;P&gt;But wanted to ask here: Is there any best practice documentation from Palo on how to handle mergers and acquisitions?&lt;/P&gt;&lt;P&gt;Would be helpful.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 10 Nov 2020 00:16:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/361749#M88220</guid>
      <dc:creator>rjdahav163</dc:creator>
      <dc:date>2020-11-10T00:16:49Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for acquisition</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/361780#M88222</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/44973"&gt;@rjdahav163&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I've never seen anything like what you are asking for, and I would honestly be pretty shocked if such a document actually exists. You need to figure out what their current networks look like and what the acquisitions requirements are, and only then can you actually build a proper network design surrounding those requirements. There's not really a cookie cutter way of how to deal with that.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Nov 2020 02:29:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/361780#M88222</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2020-11-10T02:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for acquisition</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/362006#M88258</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Agree with you 100%. There cannot be a cookie cutter way. Each acquisition is different.&lt;/P&gt;&lt;P&gt;However, would be good if there are any recommendations about overlapping IP subnets. Currently we have 2 acquisitions with same overlapping IP subnets as our internal networks. I know NATting is the way to go about it but would be nice if there is any documentation about the finer details . Let me know if you are aware of anything.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 10 Nov 2020 23:17:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/362006#M88258</guid>
      <dc:creator>rjdahav163</dc:creator>
      <dc:date>2020-11-10T23:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for acquisition</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/362894#M88306</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Depending on the size of the other networks, perhaps changing the IP subnets that the 'smallest' one is using? I know it sounds daunting, but with DHCP and planning it can be quit easy (yep had to do this a few times in the past).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good luck.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Nov 2020 23:05:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/362894#M88306</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2020-11-12T23:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for acquisition</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/382412#M89845</link>
      <description>&lt;P&gt;Would prisma access be a solution for something like this?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2021 19:42:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-acquisition/m-p/382412#M89845</guid>
      <dc:creator>Sec101</dc:creator>
      <dc:date>2021-01-27T19:42:17Z</dc:date>
    </item>
  </channel>
</rss>

