# VPN configuration work flow

VPN configuration requires several high-level steps.

This workflow contains steps for all kinds of VPN configurations. Alternative next steps are included as necessary to achieve a particular type of configuration.

1. (Optional) If you are configuring a VPN with an external device, you might want to create a custom Gateway Profile specific to the device.
2. (External VPN gateways only) Add the necessary number of External VPN Gateway elements to represent the VPN devices. External VPN Gateway elements define the VPN endpoints (gateway IP addresses) and the sites (see the next point).
   Note: One VPN Gateway elements is automatically created for each Security Engine that is managed by the Management Server and administrative Domain that you are currently connected to with your SMC Client.
3. (Policy-based VPNs only) Configure the sites. Sites define the IP addresses that can be made routable through VPNs. The sites can be adjusted in different VPNs that the gateway establishes.
4. (Optional) If the existing VPN Profiles do not have suitable settings for your new VPN, create a custom VPN Profile element. The custom VPN Profile element defines the IPsec settings (authentication, encryption, and integrity checking).
5. Define the VPN in one of the following ways:
   - Create a Policy-Based VPN element. The Policy-Based VPN element defines the topology (which gateways create tunnels with each other).
   - Create Route-based Tunnels elements to define endpoints for tunnels in route-based VPNs.
6. Create certificates, if necessary.
7. Add the necessary Access rules according to the type of VPN:
   - (Policy-based VPNs) Add the Access rules that allow traffic and select the policy-based VPN to be used. If necessary, the NAT rules for VPN traffic. Adding rules for policy-based VPNs also activates the VPN on the engines.
   - (Route-based Tunnels) Add Access rules to allow traffic between the internal network and the networks that are reachable through the Route-based Tunnels.