09-24-2019 03:11 PM
I have a vendor that I need to set up a site to site vpn with and they want me to use public IPs in the encryption domain. Can anyone explain why they would want to do this or if it offers any security benefits or weaknesses?
09-24-2019 03:21 PM
Hi,
I imagine they are probably natting on their end, thus hiding the real (private) ip address from you.
If you wanted to, you can restrict access to what that IP address can access, apply a VPN Filter.
HTH
09-25-2019 01:00 AM
09-25-2019 06:31 AM
Another scenario is that you have a DMZ with a public IP network because the server in this DMZ needs communication to the internet without NAT. If this DMZ is accessed through the VPN, you have public IPs in your encryption domain.
But more likely, whenever accessing a public service through VPNs, the public IPs make sure there is no overlap with your own addresses.
09-25-2019 08:45 AM
So, to elaborate on my initial question, my client is a hospital. I already have an ikev1 tunnel established to their older juniper SRX. After the Medstar ransomware incident, they started to beef up their security. They went and got themselves a shiny new fortigate and want to establish a new tunnel to that using route based ikev2. I already know what their private IPs are so I'm trying to figure out why they suddenly want to start using private IPs. We have a /28 at our datacenter that's only got a few usable IPs left so I don't want to waste them. I honestly can't see what security benefit they would gain by moving to public IPs.
09-25-2019 08:59 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide