Best Practices for acquisition

[rjdahav163]

Hi Guys,

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.

Now, for migrating the rules, we are using expedition. 

But, some of them have overlapping IP addressing. We are planning to resolve that problem with NAT.

But wanted to ask here: Is there any best practice documentation from Palo on how to handle mergers and acquisitions?

Would be helpful.

Thanks!

[BPry]

@rjdahav163,

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. 

[rjdahav163]

@BPry 

Agree with you 100%. There cannot be a cookie cutter way. Each acquisition is different.

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.

Thanks!

[OtakarKlier]

Hello,

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).

Good luck.

[Sec101]

Would prisma access be a solution for something like this?