Managing Users and Objects
This section describes how to set up and manage users (User Awareness, users, administrators, and authentication servers) and network resources.
Users
In the > page you can create local users and user groups. To use these objects in the Access Policy, make sure to activate User Awareness.
User objects are used to define the different terms under which users can operate. These include:
- The time frame during which users are allowed to access the network.
- If users can work remotely.
To add a new local user:
- Click > .
- Enter a , , and (optional). You cannot use these characters when you enter a password or shared secret: { } [ ] ` ~ | ‘ " # + \
- For temporary or guest users, click .
Enter the expiration date and time.
- To give the user remote access permissions, select .
- Click .
The user is added to the table on the page.
To add a new local users group with remote access permissions:
- Click > .
- Enter a .
- To give the group remote access permissions, select .
- To select initial users to add to the group, click the relevant checkboxes from the user list or click to create new users.
You can see a summary of the group members above the user list.
- To remove a user, click the X next to the user name.
- Click .
The group is added to the table on the page.
To automatically delete expired local users:
- Go to > .
- Select .
- Click .
The window opens.
- Click the checkbox for .
- Click .
Expired local users are automatically deleted every 24 hours (after midnight).
To edit a user or group:
- Select the user or group from the list.
- Click .
- Make the relevant changes and click .
To delete a user or group:
- Select the user or group from the list.
- Click .
- Click in the confirmation message.
The user or group is deleted.
Administrators
The > page lists the Check Point Appliance administrators and lets you:
- Create new local administrators
- Configure the session timeout
- Limit login failure attempts
Administrators can also be defined in a remote RADIUS server and you can configure the appliance to allow them access. Authentication of those remotely defined administrators is done by the same RADIUS server.
Administrator Roles:
- Super Administrator - All permissions. Super Administrators can create new locally defined administrators and change permissions for others.
- Read Only Administrator - Limited permissions. Read Only Administrators cannot update appliance configuration but can change their own passwords or run a traffic monitoring report from the Tools page.
- Networking Administrator - Limited permissions. Networking Administrators can update or modify operating system settings. They can select a service or network object but cannot create or modify it.
Two administrators with write permissions cannot log in at the same time. If an administrator is already logged in, a message shows. You can choose to log in with Read-Only permission or to continue. If you continue the login process, the first administrator session ends automatically.
The correct Administrator Role must be configured to perform the operations listed below. If not, a message shows.
To create a local administrator:
- Click .
The page opens.
- Configure the parameters (name, password, and password confirmation). The hyphen (-) character is allowed in the administrator name. You cannot use these characters when you enter a password or shared secret: { } [ ] ` ~ | ‘ " # + \
- Select the.
- Click .
The name and Administrator Role is added to the table. When logged in to the WebUI, the administrator name and role is shown at the top of the page.
To edit the details of locally defined administrators:
- Select the administrator from the table and click .
- Make the relevant changes.
- Click .
To delete a locally defined administrator:
- Select an administrator from the list.
- Click .
- Click in the confirmation message.
Note - You cannot delete an administrator who is currently logged in.
To allow access for administrators defined in a remote RADIUS server:
- Make sure administrators are defined in the remote RADIUS server.
- Make sure a RADIUS server is defined on the appliance. If there is no server, click the link at the top of this page. You must configure the IP address and shared secret used by the RADIUS server.
Note - 1100 appliances only support IPv4 addresses. 1200R and 1400 appliances support both IPv4 and IPv6 addresses.
- When you have a configured RADIUS server, click.
The window opens.
- Click the checkbox.
is selected by default.
- Configure the role for each user on the RADIUS server. See additional details below.
Note - A user without role definition will get a login error.
- If you select , select the :
- Super Admin
- Read only
- Networking Admin
- To define groups, click and enter the RADIUS groups separated by a comma.
- Click .
To set the Session Timeout value for both local and remotely defined administrators:
- Click .
The window opens.
- Configure the session timeout (maximum time period of inactivity in minutes). The maximum value is 999 minutes.
- To limit login failure attempts, click the checkbox.
- Enter the number of allowed before an administrator is locked out.
- In , enter the time (in seconds) that must pass before a locked out administrator can attempt to log in again.
- To enforce password complexity on administrators, click the checkbox and enter the number of days for the password to expire.
- Click .
Note - This page is available from the and tabs.
Configuring a RADIUS Server for non-local Check Point Appliance users:
Non-local users can be defined on a RADIUS server and not in the Check Point Appliance. When a non-local user logs in to the appliance, the RADIUS server authenticates the user and assigns the applicable permissions. You must configure the RADIUS server to correctly authenticate and authorize non-local users.
Note - The configuration of the RADIUS Servers may change according to the type of operating system on which the RADIUS Server is installed.
Note - If you define a RADIUS user with a null password (on the RADIUS server), the appliance cannot authenticate that user.
To configure a Steel-Belted RADIUS server for non-local appliance users:
- Create the dictionary file
checkpoint.dct
on the RADIUS server, in the default dictionary directory (that contains radius.dct
). Add these lines to the file:
@radius.dct
MACRO CheckPoint-VSA(t,s) 26 [vid=2620 type1=%t% len1=+2 data=%s%]
ATTRIBUTE CP-Gaia-User-Role CheckPoint-VSA(229, string) r
ATTRIBUTE CP-Gaia-SuperUser-Access CheckPoint-VSA(230, integer) r
|
- Add the following lines to the
vendor.ini
file on RADIUS server (keep in alphabetical order with the other vendor products in this file):
vendor-product = Check Point Appliance
dictionary = nokiaipso
ignore-ports = no
port-number-usage = per-port-type
help-id = 2000
|
- Add to the
dictiona.dcm
file the line:
“@
checkpoint.dct”
- Add this Check Point Vendor-Specific Attribute to users in your RADIUS server user configuration file:
CP-Gaia-User-Role =
<role>
Where <role> allowed values are:
Administrator Role
|
Value
|
Super Admin
|
adminrole
|
Read only
|
monitorrole
|
Networking Admin
|
networkingrole
|
To configure a FreeRADIUS server for non-local appliance users:
- Create the dictionary file
dictionary.
checkpoint
in /etc/freeradius/
on the RADIUS server:
#
# Check Point dictionary file for freeradius AAA server
#
VENDOR CheckPoint 2620
ATTRIBUTE CP-Gaia-User-Role 229 string CheckPoint
ATTRIBUTE CP-Gaia-SuperUser-Access 230 integer CheckPoint
|
- Add to
/etc/freeradius/dictionary
the line:
“$INCLUDE dictionary.
checkpoint”
- Add this Check Point Vendor-Specific Attribute to users in your RADIUS server user configuration file:
CP-Gaia-User-Role =
<role>
Where <role> is the name of the administrator role that is defined in the WebUI.
Administrator Role
|
Value
|
Super Admin
|
adminrole
|
Read only
|
monitorrole
|
Networking Admin
|
networkingrole
|
To configure an OpenRADIUS server for non-local appliance users:
- Create the dictionary file
dict.
checkpoint
in
/etc/openradius/subdicts/
on the RADIUS server:
# Check Point Gaia vendor specific attributes
# (Formatted for the OpenRADIUS RADIUS server.)
# Add this file to etc/openradius/subdicts/ and add the line
# "$include subdicts/dict.checkpoint" to etc/openradius/dictionaries
# right after dict.ascend.
$add vendor 2620 CheckPoint
$set default vendor=CheckPoint
space=RAD-VSA-STD
len_ofs=1 len_size=1 len_adj=0
val_ofs=2 val_size=-2 val_type=String
nodec=0 noenc=0
$add attribute 229 CP-Gaia-User-Role
$add attribute 230 CP-Gaia-SuperUser-Access val_type=Integer val_size=4
|
- Add the line
$include subdicts/dict.
checkpoint
to
/etc/openradius/dictionaries
immediately after dict.ascend
- Add this Check Point Vendor-Specific Attribute to users in your RADIUS server user configuration file:
CP-Gaia-User-Role =
<role>
Where <role> is the name of the administrator role that is defined in the WebUI.
Administrator Role
|
Value
|
Super Admin
|
adminrole
|
Read only
|
monitorrole
|
Networking Admin
|
networkingrole
|
To log in as a Super User:
A user with super user permissions can use the Check Point Appliance shell to do system-level operations, including working with the file system.
- Connect to the Check Point Appliance platform using an SSH client or serial console client.
- Log in to the clish shell using your user name and password.
- Run
Expert
- Enter the expert password.
Authentication Servers
In the > page you can define and view different authentication servers where users can define both an external user database and the authentication method for administrators in that database.
You can define this type of authentication server:
- RADIUS server - Define the details of a primary and secondary RADIUS server. The Check Point Appliance can connect to these servers and recognize administrators defined in them and authenticated by them. See the > page.
To add a RADIUS server:
- Click .
- In the Primary tab, enter this information:
- - Where the RADIUS server is deployed.
- - The port number to which the RADIUS server communicates with clients. The default is 1812.
- Shared secret - The secret between the RADIUS server and the Check Point Appliance.
- - Displays the shared secret.
- (seconds) - A timeout value in seconds.
- Repeat step 2 for a Secondary RADIUS server if applicable.
- Click .
The primary and/or secondary servers are added to the RADIUS section on the page.
To edit a RADIUS server:
- Click the IP address link of the RADIUS server you want to edit.
- Make the necessary changes.
- Click Apply.
The changes are updated in the RADIUS server.
To delete a RADIUS server:
Click the link next to the RADIUS server you want to delete.
The RADIUS server is deleted.
Services
The > page lists the system services configured in the system. In this page you can add new services, edit services, and delete services.
You use service objects to easily define the different network protocols. This is usually with IP protocol and ports (used by the TCP and UDP IP protocols).
You can use these objects to define policy based routing in the > page.
To create a new service:
- Click .
- In the tab, enter information in the fields that apply to the type of service you select. Note that not all fields may show:
- - Enter the service's name.
- - Select the service type from the list:
- - Select this option if it is necessary to represent a specified option in the ICMP protocol. Note that this is an advanced option.
- - Select this option to represent any IP protocol other than TCP or UDP.
- - Enter the port(s) if you selected Type - TCP or UDP. Port numbers and/or ranges can be entered by separating with commas.
- - Enter the IP protocol if you selected Type - Other.
- and - Enter the ICMP type and code that you want the service object to represent as listed in RFC 792. This option is only relevant if you selected Type - ICMP.
- - Enter an optional comment.
- – Select this checkbox to disable deep inspection of traffic matching this service. This option is only available for built-in services.
- Click .
To edit a service:
- Select a service from the list.
- Click .
- Make the necessary changes. Note that not all fields can be edited.
- Click .
To delete a service:
- Select the service from the list. Note that you can only delete a user defined service.
- Click .
- Click in the confirmation message.
To filter for a specified service:
- In the box, enter the service name or part of it.
- As you enter text, the list is filtered and shows matching results.
Service Groups
The > page lists the service groups defined in the system. In this page you can add new service groups, and edit or delete existing service groups.
There are built in service groups for common services.
To create a new service group:
- Click .
The New Service Group window opens.
- Enter a for the group and (optional).
- Click to show the full list of available services and select the relevant checkboxes.
- Click if the existing list does not contain the services you need. For information on creating a new service object, see the > page.
- Click .
The New Service Group window opens and shows the services you selected.
- You can also click from the New Service Group window.
- To remove a service object from the group list, select it and click .
- Click .
The service group is added to the list of groups.
To edit a service group:
- Select a group from the list.
- Click .
- Make the necessary changes.
- Click .
To delete a service group:
- Select the group from the list.
- Click .
- Click in the confirmation message.
To filter for a specified service group:
- In the box, enter the service group name or part of it.
- As you enter text, the list is filtered and shows matching results.
Network Objects
The > page lists the network objects defined in the system. In this page you can add new network objects, edit network objects, and delete network objects. In most cases, the most common use for these objects is to define a security policy and exceptions to it. These objects can be used as hosts for the internal DNS service and their IP addresses can be configured as fixed for the internal DHCP service.
Note - 1100 appliances support only IPv4 addresses. 1200R and 1400 appliances support both IPv4 and IPv6 addresses.
These are the available network object types:
- - A network object that represents a device with a single IP address.
- - A network object that represents a range of IP addresses.
- - A network object that represents a network.
To create a Single IP network object:
- Click .
The New Network Object window opens.
- In , select .
- Enter anand.
- Select or clear these options as necessary:
- When the gateway is the DNS server for your internal networks, the name of the server/network object is translated to its IP address.
- The internal DHCP service does not distribute the configured IP address of this server/network object to anyone.
- - The internal DHCP service distributes the configured IP address only to this server/network object based on its MAC address.
- Enter the This is required for IP reservation. When you create the object from the Active Computers page, the MAC address is detected automatically.
- Click .
To create an IP Range network object:
- Click .
The New Network Object window opens.
- In , select .
- In the and fields, enter the IP addresses that represent the start of the IP range and end of the IP range.
- Enter the .
- Select or clear this option as necessary:
- - The internal DHCP service does not distribute the configured IP range to anyone.
- Click .
To create a Network type network object:
- Click .
The New Network Object window opens.
- In , select .
- Enter aand .
- Enter the .
- Click .
To edit a network object:
- Select a network object from the list.
- Click .
- Make the necessary changes.
- Click .
To delete a network object:
- Select the network object from the list.
- Click .
- Click in the confirmation message.
To filter for a specified network object:
- In the box, enter the name of the network object or part of it.
- As you enter text, the list is filtered and shows matching results.
URL Lists
The > page lets you override central management's URL filtering policy in your local Check Point Appliance. Use this feature to define URL blacklists and whitelists exceptions to the global policy, whose content can be edited per gateway. Before you use this feature, the system administrator of the Security Management Server that centrally manages this gateway must complete prerequisite steps.
You can use this page to manage URLs lists:
- Add new URLs/IP addresses or regular expressions to URLs lists.
- Edit existing URLs/IP addresses or regular expressions from URLs lists.
- Delete existing entries in URLs lists.
- Enable and disable this feature.
Prerequisite steps for the system administrator of the Security Management Server:
- Turn on the Application Control blade for the gateway object that represents this Check Point Appliance.
- Configure custom applications in SmartDashboard with these guidelines:
- Use the prefix: LOCAL_ (case-sensitive) when naming a custom application.
For example, LOCAL_whitelist or LOCAL_blacklist. - Enter at least one URL for this custom application, it can be a dummy URL. The actual list of URLs to allow or block is defined locally in the Check Point Appliance.
- Create rules in the Application Control Rule Base using the custom defined applications with the LOCAL_ prefix. Make sure to add the rules in positions that make sense in the Rule Base.
- Install policy (on the specified gateway).
Steps for the system administrator of this Check Point Appliance:
- On this page, set to .
- Add URLs/IP addresses or regular expressions to the predefined URLs lists (the custom applications defined in Security Management Server).
Note - The names of the predefined URLs lists does NOT show the LOCAL_ prefix that was used to define the application in Security Management Server.
For example, LOCAL_whitelist is shown as just whitelist.

|
Important -
- If Application Control is turned off or no custom applications have been defined in the Security Management Server, this page is empty and shows a message that informs that local URLs can only be defined after URLs lists are predefined in the appliance's security policy.
- If a list was removed or renamed in the Security Management Server, a warning shows above the table and next to the URLs List in the table.
|
To create a new URLs list entry:
- Click .
- Select or .
The New URL/IP Address or New Regular Expressions window opens.
- Select the applicable from the list.
- Enter a or a for the URLs list.
- Click .
The URL is added to the list of entries for the specified URLs list in the table.
To edit a URLs list entry:
- Select an entry from the list.
- Click .
- Make the necessary changes.
- Click .
To delete a URLs list entry:
- Select an entry from the list.
- Click .
- Click in the confirmation message.
To filter for a specified URLs list:
Do one of these:
- In the box, select the URLs list.
- In the field, enter the URLs list name to shows matching results.