About IKEv2 Policies

When you configure a mobile VPN, the Firebox automatically creates two types of policies:

Connect policy

The connect policy allows the VPN to establish. For Mobile VPN with IKEv2, the connect policy is named Allow-IKE-to-Firebox. This policy is hidden, which means it does not appear in the Firebox policies list.

In the global VPN settings, the Enable built-in IPSec policy setting controls this policy. Do not clear the Enable built-in IPSec policy check box. For more information about global VPN settings, see About Global VPN Settings.

Access policy

The access policy allows Mobile VPN with IKEv2 groups and users to get access to resources on your network. For Mobile VPN with IKEv2, the access policy is named Allow IKEv2-Users.

By default, the Allow IKEv2-Users policy allows users to access all network resources. This occurs because the To list in the Allow IKEv2-Users policy includes only the alias Any.

Only the IKEv2-Users group appears in the From list of the Allow IKEv2-Users policy. The IKEv2-Users group includes any users and groups that you add to the Mobile VPN with IKEv2 configuration. Users and groups that you add to the Mobile VPN with IKEv2 configuration do not appear in the From list of the Allow IKEv2-Users policy. However, the policy still applies to those users and groups.

Authentication Groups and IKEv2 Policies

It is important to understand that Firebox policies control which resources that mobile VPN users can access. VPNs are not considered to be part of the Trusted or Optional zones. When users connect to the VPN, they are not considered to be trusted users on the local network.

This means that Firebox policies with the Trusted or Optional aliases in the From list do not apply to traffic from mobile VPN users unless you add mobile VPN groups or users to those policies. Or, you can create new policies for traffic from mobile VPN groups and users.

For example, this policy does not apply to traffic from Mobile VPN with IKEv2 users because the From list includes only the alias Any-Trusted:

This policy does apply to traffic from Mobile VPN with IKEv2 users because the From list includes a Mobile VPN with IKEv2 user group:

This policy also applies to traffic from Mobile VPN with IKEv2 users because the RADIUS user group TestGroup1 is specified in the Mobile VPN with IKEv2 configuration:

Carefully consider which user groups you add to Firebox policies. For example, if you add RADIUS user groups to the authentication configuration on your Firebox, and you add the same groups to your Mobile VPN with IKEv2 configuration, consider adding the RADIUS groups to Firebox policies rather than the default IKEv2-Users group. The IKEv2-Users group includes all groups and users that you add to the Mobile VPN with IKEv2 configuration. If you add the IKEv2-Users group to a Firebox policy, all mobile users have access to resources specified in that policy, which might not be your intention.

Virtual IP address pools do not affect whether VPN users are considered as trusted users on the local network. For example, if you specify an IP address pool for Mobile VPN with IKEv2 that overlaps with the IP address range of your local network, mobile VPN users are still not considered as trusted users on the local network.

Best Practices for IKEv2 Policies

We recommend that you limit which network resources Mobile VPN with IKEv2 users can access through the VPN. To do this, you can replace the Allow IKEv2-Users policy.

To replace the Allow IKEv2-Users policy:

  1. Determine the ports and protocols your users require. To determine this, assess your network with baseline tests and view logs.
  2. Add Mobile VPN with IKEv2 groups and users to existing Firebox polices that specify those ports and protocols. For example, you can add Mobile VPN with IKEv2 groups and users to policies for web traffic.
  3. If required, add new policies:
    1. When you select a policy type for the new policy, you can specify a protocol and port.
    2. In the From list of the policy, specify users or groups. You must specify groups or users included in the Mobile VPN with IKEv2 configuration. For example, you can specify the default IKEv2-Users group. Or, specify groups and users that you added to the Mobile VPN with IKEv2 configuration.
    3. In the To list of the policy, remove the Any alias and add other destinations.
  4. Before you disable the Allow IKEv2-Users policy, make sure your policies allow Mobile VPN with IKEv2 users to access all required network resources.
  5. Disable the Allow IKEv2-Users policy.

See Also

Edit the Mobile VPN with IKEv2 Configuration

About Mobile VPN with IKEv2 User Authentication

Troubleshoot Mobile VPN with IKEv2