VPN setup to integrate datacenters Your instance supports direct integrations with any number of data sources over the Internet. When configuring an integration that uses an encrypted protocol, such as Lightweight Directory Access Protocol (LDAP) or HTTPS, it is good practice to use the Internet as a transport mechanism. However, there may be security or network architecture requirements that dictate the use of a site-to-site Internet Protocol Security (IPSEC) Virtual Private Network (VPN) connection between the datacenters and your business networks. The VPN supports the necessary encrypted communication between the instance and your network. This video describes how to locate the IP addresses for each of your company's instances. My IP Information Create an address for VPN communicationTo prevent conflict or overlap with internal ServiceNow networks or with another customer's internal IP address schemes, the instance requires that all tunneled traffic in the encryption domain use non-RFC-1918 addresses on both sides of the tunnel. Alternatives to using a VPNThere are alternatives to using a VPN that you might want to consider. Addresses for VPN communicationTo prevent conflict or overlap with internal ServiceNow networks or with another internal IP address schemes in your network, all tunneled traffic in the encryption domain must use non-RFC-1918 addresses on both sides of the tunnel.Redundant tunnelsIf you are using a VPN, you can create redundant tunnels.ServiceNow VPN connectionsThe ServiceNow VPN infrastructure uses pairs of Cisco adaptive security appliance (ASA) devices that serve as VPN termination points.VPN setupFrom the time that a VPN request is submitted, it typically takes one week or less to complete the VPN build. Request a VPN serviceFor all VPN requests, including provisioning, modifications, or general questions, use the Service Catalog VPN Request form.