Configuring Remote Access VPN
This section includes procedures and explanations for configuring Remote Access VPN. For configuration specific to Endpoint Security VPN, Check Point Mobile for Windows, and SecuRemote, see the Remote Access Clients Administration Guide.
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.
Configuring the Security Gateway for a Remote Access Community
Make sure that the VPN Software Blade is enabled before you configure the Remote Access community.
To configure the Security Gateway for Remote Access:
- In R80 SmartConsole, click and double-click the Security Gateway.
The gateway window opens and shows the page.
- From the navigation tree, click .
The page shows the VPN communities that the Security Gateway is participating.
- To add the Security Gateway to a community:
- Click .
- Select the community.
- Click .
- From the navigation tree, click .
- Configure the VPN Domain.
- Configure the settings for Visitor Mode.
- From the navigation tree, click .
- Configure the settings for Office Mode.
Note - Office Mode support is mandatory on the Security Gateway side.
- Click and publish the changes.
Defining Access Control Rules
Access control is a layer of security not connected with VPN. The existence of a remote access community does not mean that members of that community have free automatic access to the network. Appropriate rules need to be created in the Access Control Policy Rule Base blocking or allowing specific services.
- Create a rule in the Security Access Control Rule Base that deals with remote access connections.
- Right-click the cell in the VPN column, and select .
- Click the add button for each community that you are adding to the rule.
- Close the VPN community window.
- Define and .
- Publish the changes and install the policy.
For 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
|
Enabling a User Certificate
To enable a user certificate:
- In R80 SmartConsole, from the click .
- Create a new user or double-click an existing user.
The window opens.
- From the navigation tree, click .
- Click .
The window opens.
- Click the tab and make sure that is selected.
- Click .
- Publish the changes.
For Internally Managed Users
When a user is deleted, their certificate is automatically revoked. Certificates can be disabled or revoked at any time.
If the certificate is already active or was not completed by the user, you can revoke it by clicking Revoke in the Certificates tab of the User Properties window.
Enabling Hybrid Mode and Methods of Authentication
Hybrid mode allows the Security Gateway and remote access client to use different methods of authentication.
To enable Hybrid Mode:
- From Menu, click .
- From the navigation tree, click .
- In the section, click .
- Click .
- Publish the changes.
Defining User Authentication Methods in Hybrid Mode
To define the Hybrid Mode authentication for a user:
- From the Objects Bar, double-click the user.
The window opens.
- From the navigation tree, click .
- Select the .
- Configure the necessary settings.
- Click .
- Publish the changes.
- Give these credentials to the user.
Using a Pre-Shared Secret
When using pre-shared secrets, the remote user and Security Gateway authenticate each other by verifying that the other party knows the shared secret: the user's password.
To enable authentication with pre-shared secrets:
- From Menu, click .
- From the navigation tree, click .
- In the section, select .
- Click .
- Configure the Authentication settings for each applicable user:
- From the Objects Bar, double-click the user.
The window opens.
- From the navigation tree, click .
- Select and click .
The window opens.
- From the Authentication tab, click .
- Enter and the .
- Click .
- Publish the changes.
- Give the password to the user.
Configuring RADIUS Objects
To create a new RADIUS host object:
- In R80 SmartConsole, the tab, click .
The window opens.
- Enter the and the of the new RADIUS host object, and click .
- Publish the changes.
To configure the RADIUS server object settings:
- In R80 SmartConsole, the tab, click .
The window opens.
- Configure new server properties:
- Click .
- Publish the changes.
To configure a Security Gateway to use RADIUS authentication:
- In R80 SmartConsole, go to the view, right-click a Security Gateway object and select .
- In the gateway property window that opens, select .
- In the section, select .
- Click .
To define a RADIUS user group:
- In R80 SmartConsole, the tab, click .
The window opens.
- Enter the name of the group in this format: group_name.
Make sure the group is empty.
- Click .
- Publish the changes and install the policy.
To configure RADIUS authentication settings for users:
- Create new user profiles -
- For users with Security Gateway user accounts - in R80 SmartConsole, go to the tab and click .
- For users without Security Gateway user accounts, open the SmartDashboard - go to (or ). If you support more than one external authentication scheme, set up External User Profiles with the setting.
The window opens.
- In the tab, configure these settings:
- Enter a for the RADIUS server. (When configuring as an External User Profile, the name "" is automatically assigned)
- Set the .
- In the tab, configure these settings:
- Select from the drop-down list
- From the drop-down menu, select the RADIUS object that you configured earlier
- Click .
To complete the RADIUS authentication configuration:
- In R80 SmartConsole, create the required Access Control rules to allow access to users authenticated through the RADIUS server.
- Verify that communication between the firewall and the server is not NATed in the Address Translation Rule Base.
- Save the changes.
- Close all R80 SmartConsole windows.
- On the Security Management Server, use GuiDBedit to change the value of the attribute from
false
to true
. - Save and then close GuiDBedit.
- Open R80 SmartConsole.
- Install the policy.
- On the RADIUS server, edit the RADIUS users to include a class RADIUS attribute on the users Return list that corresponds to the user group that they access.
To use a different attribute instead of the class attribute:
- Close all R80 SmartConsole windows and clients.
- On the Security Gateway, use GuiDBedit to modify the value of the firewall_properties attribute radius_groups_attr to the new RADIUS attribute.
- Save.
- Close GuiDBedit.
- Open R80 SmartConsole.
- Install the policy.
- On the RADIUS server, make sure that you use the same RADIUS attribute on users' Return lists that corresponds to the Firewall user group that they access.
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:
- Support encryption algorithms - Select the encryption algorithms that will be supported with remote hosts.
- Use encryption algorithms - 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.
- Support Data Integrity - Select the hash algorithms that will be supported with remote hosts to ensure data integrity.
- Use Data Integrity - The hash algorithm chosen here will be given the highest priority if more than one choice is offered.
- Support Diffie-Hellman groups - Select the Diffie-Hellman groups that will be supported with remote hosts.
- Use Diffie-Hellman group - SecureClient users utilize the Diffie-Hellman group selected in this field.
- Click and publish the changes.
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 IKE Phase 2 Properties window is displayed.
- Click the Encryption tab.
- Click .
- Configure the and .
- Click and close the window.
- Publish the changes and install the policy.