Configuring Policy for Remote Access VPN
Configuring Remote Access Policy
Configure Remote Access VPN policy in the Unified Access Control Policy Rule Base.
Make sure that:
- All Remote Access Gateways are part of a Remote Access VPN Community.
- The Remote Access Community is included in the column of the rule.
For R80.x gateways, you can include Remote Access and VPN clients in rules as the of the rule. To do this create an Access Role for each client.
Creating and Configuring the Security Gateway
- Create a Security Gateway network object.
- On the page, select .
- Initialize a secure communication channel between the VPN module and the Security Management Server by clicking
- On the page, define the interfaces and the VPN domain.
The ICA automatically creates a certificate for the Security Gateway.
Defining a Remote Access Community
To define the VPN Remote Access community and its participants:
- From the Objects Bar, click .
- Double-click .
The window opens.
- On the Participating Gateways page, click the Add button and select the Security Gateways that are in the Remote Access Community.
- On the Participating User Groups page, click the Add button and select the group that contains the Remote Access users.
- Click .
- Publish the changes.
Defining Access Control Rules
Access control is a layer of security not connected with VPN. When there is a Remote Access Community, it does not mean that members of that community have free, automatic access to the network. Security rules have to be created in the Access Control Policy Rule Base blocking or allowing specific services.
Create a rule in the Access Control Rule Base that handles with remote access connections.
- Go to and right-click the cell in the VPN column.
- Select .
- Choose the community and click the add button ().
- Close the VPN community window.
- Define and columns.
- Install the policy.
Example:
To allow remote access users to access the organization's SMTP server, called SMTP_SRV, create the following rule:
Source
|
Destination
|
VPN
|
Service
|
Action
|
Track
|
Any
|
SMTP_SRV
|
Remote_Access_ Community
|
SMTP
|
Accept
|
Log
|
Access Roles for Remote Access
For R80.x gateways, create Access Roles for Remote Access and VPN Clients to include them in rules in the Access Control Rule Base. This applies to Mobile Access and IPsec clients. When an Access Role for a client is in the column of a rule, the rule applies to traffic that originates from that client.
You can also use an Access Role in the column.
You must enable Identity Awareness on each gateway that is an installation target for rules with Access Roles.
Creating Access Roles for Remote Access and VPN Clients
To create an Access Role for a new Remote Access or VPN client:
- Open a window in one of these ways:
- In the object tree, click .
- From the column of the Access Control policy Rule Base: Click
> click
> select .
- Enter a for the access role.
- Optional: Enter a or click the down arrow to select a for the object.
- From the left pane, select .
- Expand the list and click >
- Click
to select a client and enter an object name. - Click .
- Optional: To make the Access Role include only specified users, select from the left pane and define the allowed users.
- Click .
Policy Definition for Remote Access
There must be a rule in the Security Policy Rule Base that grants remote users access to the LAN. Consider which services are allowed. Restrict those services that need to be restricted with an explicit rule in the Security Policy Rule Base.
Modifying Encryption Properties for Remote Access VPN
The encryption properties of the users participating in a Remote Access community are set by default. If you must modify the encryption algorithm, the data integrity method and/or the Diffie-Hellman group, you can either do this globally for all users or configure the properties per user.
To modify the user encryption properties globally:
- From Menu, click .
- From the navigation tree, click .
- From the section, click .
The window opens.
- In the tab, configure the applicable settings:
- - Select the encryption algorithms that will be supported with remote hosts.
- - Choose the encryption algorithm that will have the highest priority of the selected algorithms. If given a choice of more than one encryption algorithm to use, the algorithm selected in this field will be used.
- - Select the hash algorithms that will be supported with remote hosts to ensure data integrity.
- - The hash algorithm chosen here will be given the highest priority if more than one choice is offered.
- - Select the Diffie-Hellman groups that will be supported with remote hosts.
- - Client users utilize the Diffie-Hellman group selected in this field.
- Click .
- Install policy.
To configure encryption policies for specified users:
- Open , and click .
- From the section, click .
- In the window, click the tab.
- Clear .
- Click and close the window.
- For each user:
- From the Objects Bar, double-click the user.
- From the navigation tree, click .
- Click .
The window is displayed.
- Click the tab.
- Click .
- Configure the and .
- Click and close the window.
- Install policy.
Installing the Policy
Install the policy and instruct the users to create or update the site topology.
IPsec and IKE for Remote Access
For Remote users, the IKE settings are configured in Global Properties > Remote Access > VPN Authentication and Encryption.
IKEv2 is not supported for Remote Access.
For more information about IPsec and IKE, see the VPN Site to Site Administration Guide.