# Example VPN configuration 3: create a VPN Profile element

You must create a custom VPN Profile element to define the settings for VPN clients.

##

Note: This configuration scenario does not explain all settings related to authenticating VPN client users.

For more details about the product and how to configure features, click Help or press F1.

## Steps

1. Select Secure SD-WAN.
2. In the element tree, browse to Other Elements > Profiles > VPN Profiles.
3. Right-click Suite-B-GCM-128 and select New > Duplicate.
   The settings from the default profile are copied into the VPN Profile Properties dialog box that opens.
4. In the Name field, enter a unique name.
5. On the IKE SA tab, configure the IKE SA settings.
   1. In the Version drop-down list, select the IKE version.
      You can select IKEv1, IKEv2, or both. If both versions are selected, IKEv2 is tried first in the negotiations, and IKEv1 is only used if the remote gateway does not support IKEv2.
   2. (Only if IKEv1 is selected) Make sure IKEv1 Negotiation Mode is set to Main.
      Using Main mode helps guarantee that the user names and passwords of the VPN client users remain confidential.
6. On the IPsec Client tab, configure the VPN client settings.
   1. Make sure that the Authentication Method is set to RSA Signatures.
   2. Select Allow Hybrid/EAP Authentication.
      Hybrid authentication is used with IKEv1. EAP (Extensible Authentication Protocol) is used with IKEv2.
   3. Make sure IPsec Security Association Granularity for Tunnel Mode is set to SA Per Net.
7. Click OK.

## Next steps

Create a Policy-Based VPN element.

## VPN Profile Properties dialog box

Use this dialog box to define the properties of a VPN Profile.

Option | Definition
--- | ---
General tab
Name | The name of the element.
Comment (Optional) | A comment for your own reference.
Overview section | A preview of the selections made on the other tabs is shown.

Option | Definition
--- | ---
IKE SA tab
Versions | Select the IKE version. Note: If both versions are selected, IKEv2 is tried first in the negotiations, and IKEv1 is only used if the remote gateway does not support IKEv2. IKEv1 — Internet Key Exchange version 1. IKEv2 — Internet Key Exchange version 2.
Cipher Algorithms | Select encryption methods that are appropriate for the sensitivity of the transferred information and any regulations that you might have to follow. We recommend that you limit the selection if possible, preferably using only one. If you select several options, multiple proposals are sent in IKE negotiations. AES-GCM-256 — Advanced Encryption Standard (AES) and Galois/Counter Mode (GCM) encryption algorithm with a 256-bit key size. Recommended for high-speed networks. Note: This is the recommended option, and other options are for compatibility with older deployments and equipment. AES-CBC-256 — Advanced Encryption Standard (AES) and Cipher Blocking Chaining (CBC) encryption algorithm with a 256-bit key size. AES-CBC-128 — Advanced Encryption Standard (AES) and Cipher Blocking Chaining (CBC) encryption algorithm with a 128-bit key size. 3DES — Triple DES algorithm. Applies the DES cipher algorithm three times to each data block. This option has a high overhead compared to other protocols with a comparable level of security. It is not a good choice when high throughput is required. DES — Data Encryption Standard algorithm. Do not select this option unless you are required to do so. DES is no longer considered secure because it is relatively easy to break DES encryption with modern computers. Blowfish — Blowfish cipher algorithm. Note: The restricted (-R) product version has no strong encryption algorithms.
Integrity / Pseudorandom Function Algorithms | Used for integrity checking and key derivation. We recommend that you select just one of these options if you have no specific reason to select more. SHA-2 — The SHA-2 hash function. Define the minimum length according to the security requirements for the tunnel. Note: This is the recommended option, and other options are for compatibility with older deployments. SHA-1 — The SHA-1 hash function. MD5 — The MD5 message-digest algorithm.
Key Exchange Methods | Select one or more groups for key exchange. We recommend that you select from groups 14-21 according to the security requirements for the tunnel. Note: Groups 1, 2, and 5 are not considered sufficiently secure in all cases, although they might be required for interoperability with legacy systems. 21 (ECP 521 bits) — Diffie-Hellman key exchange with 521-bit elliptic curve. 20 (ECP 384 bits) — Diffie-Hellman key exchange with 384-bit elliptic curve. 19 (ECP 256 bits) — Diffie-Hellman key exchange with 256-bit elliptic curve. 18 (8192 bits) — Diffie-Hellman key exchange with a 8192-bit modulus. 17 (6144 bits) — Diffie-Hellman key exchange with a 6144-bit modulus. 16 (4096 bits) — Diffie-Hellman key exchange with a 4096-bit modulus. 15 (3072 bits) — Diffie-Hellman key exchange with a 3072-bit modulus. 14 (2048 bits) — Diffie-Hellman key exchange with a 2048-bit modulus. 5 (1536 bits) — Diffie-Hellman key exchange with a 1536-bit modulus. 2 (1024 bits) — Diffie-Hellman key exchange with a 1024-bit modulus. 1 (768 bits) — Diffie-Hellman key exchange with a 768-bit modulus.
Authentication Method | The method that gateways in the VPN use to authenticate to each other. Pre-Shared Key — Requires that you periodically change the pre-shared keys for each tunnel in the VPN elements to be secure. RSA Signatures — Requires that each Gateway has a valid certificate. DSS Signatures — Requires that each Gateway has a valid certificate. ECDSA Signatures — Requires that each Gateway has a valid certificate. The authentication method you select here is used for site-to-site tunnels. Mobile VPNs have separate settings on the IPsec Client tab.
IKEv2 PPK | Select one of the following options for Post-quantum Pre-Shared Key (PPK): Not in use — PPK is not enabled. Enabled — PPK is enabled to use with IKEv2 protocol for the tunnel but is not mandatory. For example, if we want to establish a tunnel between Gateway A and Gateway B. Gateway A has PPK enabled and configured but Gateway B does not support PPK feature or PPK is not configured. Then the tunnel can still be established without the PPK. Mandatory — PPK is enabled and is mandatory to use with IKEv2 protocol for the tunnel to be established. For example, if we want to establish a tunnel between Gateway A and Gateway B. Gateway A has PPK enabled and configured but Gateway B does not support PPK feature or PPK is not configured. Then the tunnel cannot be established without the PPK configured on both gateways. Note: PPK is only supported on engine version 7.3 and later. A single PPK element is defined for the gateway-to-gateway tunnel, and the element is auto-generated if both are internal gateways.
SA Lifetime in Minutes | The time limit after which IKE SA negotiations are done again in a continuously used tunnel. This setting also defines the authentication timeout for the Forcepoint VPN Client. Change this setting only if you have a specific reason to do so. The SA lifetime must match the settings of the external gateway device. This setting affects tunnels that carry traffic continuously. Tunnels that are not used are closed after a short delay regardless of the lifetime set. Re-negotiations improve security, but might require heavy processing. The default lifetime is 1440 minutes.
IKEv1 Negotiation Mode (Only if the Version is IKEv1) | The negotiation mode for IKEv1 key exchange. Main — Main negotiation mode (recommended) protects the identity information of the Gateways so that malicious parties cannot gain information about the Gateway's identity by launching IKE negotiations with the gateway. Aggressive — Aggressive negotiation mode skips some steps that are included in the main mode, resulting in quicker negotiations. For security reasons, we recommend that you do not use the aggressive negotiation mode if you use pre-shared keys for authentication. Select Aggressive mode for tunnels that involve a gateway with a dynamic IP address. In this case, we recommend that you use certificates for authentication rather than pre-shared keys.
Always Keep Tunnels Established | When selected, the Security Engine keeps the IPsec tunnels established even when no traffic is sent through the tunnel. When the value for the SA Lifetime in Minutes option (for IKE SA) or the value for the IPsec Tunnel Lifetime (for IPsec SA) option is exceeded, the tunnel is automatically renegotiated even if there is no traffic in the VPN tunnel.

Option | Definition
--- | ---
IPsec SA tab
IPsec Type | Select one or more options to define integrity checking and data origin authentication for IP datagrams. ESP — (Recommended) Encapsulating Security Payload. The communications are encrypted. AH — Authentication Header. Usually, AH alone is not a valid option. The AH setting disables encryption for the tunnel, fully exposing all traffic that uses the tunnel to anyone who intercepts it in transit. You can use AH to authenticate and check the integrity of communications without encrypting them.
Cipher Algorithms | The tunnel encryption method. We recommend that you limit the selection to as few choices as possible, preferably only one. AES-GCM-256 — Advanced Encryption Standard Galois/Counter Mode encryption algorithm with a 256-bit key size. Recommended for high-speed networks. AES-GCM-128 — Advanced Encryption Standard Galois/Counter Mode encryption algorithm with a 128-bit key size. Recommended for high-speed networks. AES-256 — Advanced Encryption Standard algorithm with a 256-bit key size. AES-128 — Advanced Encryption Standard cipher algorithm with a 128-bit key size. AES-GCM-256 — Advanced Encryption Standard Galois/Counter Mode encryption algorithm with a 256-bit key size. Recommended for high-speed networks. 3DES — Triple DES algorithm. Applies the DES cipher algorithm three times to each data block. This option has a high overhead compared to other protocols with a comparable level of security. It is not a good choice when high throughput is required. DES — Data Encryption Standard algorithm. Do not select this option unless you are required to do so. DES is no longer considered secure because it is relatively easy to break DES encryption with modern computers. Blowfish — Blowfish cipher algorithm. Null — Do not select this option unless you want to disable encryption. This option fully exposes all traffic that uses the tunnel to anyone who intercepts it in transit. You can use Null encryption to authenticate and check the integrity of communications without encrypting them. Note: The restricted (-R) product version has no strong encryption algorithms.
Integrity Algorithms | Used for integrity checking, except when authenticated encryption such as AES-GCM is used. We recommend that you select just one of these options if you have no specific reason to select more. SHA-2 — The SHA-2 hash function. Define the minimum length according to the security requirements for the tunnel. Note: This is the recommended option, and other options are for compatibility with older deployments. SHA-1 — The SHA-1 hash function. AES-XCBC-MAC — The AES-XCBC-MAC Message Authentication Code hash function. MD5 — The MD5 message-digest algorithm.
Compression Algorithm | Options for compressing the data in the tunnel to reduce the bandwidth use on congested links. None — (Recommended for most environments) Sends the data without compressing it. Provides better performance when bandwidth congestion for tunneled traffic is not a constant issue or if there is significant processor load. Deflate — Compresses the data. This compression requires processing and memory resources, which increases latency. Latency might also increase for non-tunneled traffic. Do not select this option if the resource utilization is high. Gateways at both ends of each tunnel involved must support the option.
IPsec Tunnel Lifetime (Optional) | Limits after which IPsec SA negotiations are done again in a continuously used tunnel. Reaching either the time or data amount limits triggers new IPsec SA negotiations, which must happen at regular intervals to guarantee security. This setting affects tunnels that carry traffic continuously. Tunnels that are not used are closed after a short delay regardless of the lifetime set here. IPsec SA negotiations are lighter on the processor than IKE SA negotiations, but still require some processing. Too frequent re-negotiations can reduce performance down to unacceptable levels. Note: There is a separate setting for the SA Lifetime on the IKE SA tab. The SA Lifetime must be longer than the IPsec Tunnel Lifetime. The default is 480 minutes with no limit on the amount of transferred data.
Security Association Granularity | Defines the level at which security associations (SA) are created. SA per Net — Creates an SA for each network from which connections are made through the tunnel. This setting reduces the overhead when there are many hosts making connections through the tunnel. SA per Host — Creates an SA for each host that makes connections through the tunnel. This setting might provide more even load balancing in clusters than the per net setting, but increases the overhead, because per host usually requires more SAs to be negotiated.
Use PFS (Optional) | Enables the Perfect Forward Secrecy (PFS) feature. Important: When the PFS feature is enabled. By default, the Same as in IKE option is selected for the PFS Key Exchange Method.
Use PFS Exchange Method | By default, the Same as in IKE option is selected for the PFS Key Exchange Method. You can select one of the Diffie-Hellman groups. We recommend that you select from groups 14-21 according to the security requirements for the tunnel. Note: Groups 1, 2, and 5 are not considered sufficiently secure in all cases, although they might be required for interoperability with legacy systems. By default, the Same as in IKE option is selected. This means the Diffie-Hellman groups that are selected for IKE exchange in the IKE SA tab are also applicable for the IPsec SA. If an option other than the Same as in IKE option is selected, an error message that states "Explicit PFS Key Exchange Method selection will be deprecated in a future version. Change selection to ‘Same as in IKE’ in Profile configuration." is displayed during the policy upload. When you use this option, the gateways calculate new values for key negotiations when renegotiating the SAs instead of deriving the values from previously negotiated keying material. This setting increases security if a key is compromised.
Disable Anti Replay Window (Optional) | The anti-replay window feature provides protection against attacks in which packets are replayed. When enabled, the gateway keeps track of the sequence numbers of the arriving packets, and discards any packet whose number matches the number of a packet that has already arrived. It is usually recommended to leave the anti-replay window enabled. However, if QoS is applied to ESP/AH traffic, some of the ESP packets (for the same SA) might be delayed due to the classification and arrive at the destination so late that the anti-replay window has moved too far. This behavior causes the packets to be dropped. In this case, it might be necessary to disable the anti-replay window.
Disable Path MTU Discovery (Optional) | Prevents the gateway from sending ICMP "Fragmentation needed" messages to the originator when the packet size (including the headers added for IPsec) exceeds the Ethernet-standard 1500 bytes. If this option is selected, packets might be fragmented for transport across the tunnel and reassembled at the receiving gateway. Selecting the option might be necessary if ICMP messages do not reach the other gateway or the other gateway does not react to them correctly.

Option | Definition
--- | ---
IPsec Client tab If a VPN Profile that contains IPsec client settings is used in a Route-based Tunnels, the IPsec Client settings are ignored.
Authentication Method | Enables certificate-based authentication. This option is always used for the Gateway certificates for the Gateways involved in mobile VPNs, and if certificate authentication is used, also for the client. Certificate authentication does not need separate activation. However, you must configure the issuing authority separately as trusted and you must create certificates for the VPN clients in a manual process. RSA Signatures — Requires that each Gateway has a valid certificate. DSS Signatures — Requires that each Gateway has a valid certificate. ECDSA Signatures — Requires that each Gateway has a valid certificate.
Allow Hybrid / EAP Authentication (Optional) (Forcepoint VPN Client only) | Allows users of the Forcepoint VPN Client to authenticate by filling in a user name and password or a similar authentication scheme provided by an external authentication server. The gateway still authenticates itself to the VPN clients using a certificate.
Allow CN Authentication (Optional) (Certificate authentication only) | Allows using the common name (CN) of the certificates for authentication. The CN is checked against a value entered in User elements.
Allow Pre-Shared Key Authentication with IKEv1 (Optional) | Select this option if you have third-party VPN clients that use a pre-shared key for authenticating the VPN clients and the gateway. The pre-shared key is defined in the properties of User elements that have Pre-Shared Key Method as an authentication method. The Forcepoint VPN Client does not support this method. CAUTION: The pre-shared key option requires aggressive mode IKE negotiations in the mobile VPN. In aggressive mode, user information is not protected, so we recommend that you take precautions, such as not using the same user name for the users as they have when they access other services in your internal network.
IPsec Security Association Granularity for Tunnel Mode | Defines the level at which security associations (SA) are created in Tunnel Mode. The Forcepoint VPN Client supports only SA per Net. SA per Net — Creates a security association (SA) for each network from which connections are made through the tunnel. This setting reduces the overhead when there are many hosts making connections through the tunnel. Allow SA to Any Network — (Valid only for third-party IPsec VPN Clients) Select this option together with SA per Net to support both the Forcepoint VPN Client and any third-party VPN clients that only support SAs negotiated per Host. SA per Host — Creates an SA for each host that makes connections through the tunnel. This setting might provide more even load balancing in clusters than the per net setting, but increases the overhead, because per host usually requires more SAs to be negotiated.

Option | Definition
--- | ---
Certificate Authorities tab
Trust All | The gateway trusts all certificate authorities, unless restricted in the VPN element. This option is the default setting.
Trust only selected | The gateway trusts only the certificate authorities that you select in the table. You can also restrict trusted CAs in VPN Gateway and External VPN Gateway elements. If you restrict trusted CAs in both the gateway and the VPN Profile, make sure that any two gateways that form a VPN tunnel trust the same CA after all defined restrictions are applied.