In This Section: |
To successfully manage security for a large network, we recommend that you first set up your administrative team, and delegate tasks.
We recommend that you create administrator accounts in SmartConsole, with the procedure below or with the First Time Configuration Wizard.
If you create it through the SmartConsole, you can choose one of these authentication methods:
To create an administrator account using SmartConsole:
The Administrators pane shows by default.
The New Administrators window opens.
Note - This parameter is case-sensitive.
Note - If you do not do this, the administrator will not be able to log in to SmartConsole.
To define an Authentication Method:
In the Authentication Method section, select a method and follow the instructions in Configuring Authentication Methods for Administrators.
To create a Certificate - If you want to use a certificate to log in:
In the Certificate Information section, click Create, and follow the instructions in Configuring Certificates for Administrators.
The default expiration date shows, as defined in the Default Expiration Settings. After the expiration date, the account is no longer authorized to access network resources and applications.
To change an existing administrator account:
The Administrators properties window opens.
Creating an administrator with cpconfig
We do not recommend creating an administrator with cpconfig
, the Check Point Configuration Tool. Use it only if there is no access to SmartConsole or the Gaia Portal. If you use cpconfig
to create an administrator:
When you define an administrator, you must configure the authentication credentials for the administrator.
The authentication credentials for the administrator can be one of the supported authentication methods, or a certificate, or the two of them.
You can create a certificate file in SmartConsole. The administrator can use this file to log in to SmartConsole using the Certificate File option. The administrator must provide the password for the certificate file.
You can import the certificate file to the CryptoAPI (CAPI) certificate repository on the Microsoft Windows SmartConsole computer. The administrator can use this stored certificate to log in to SmartConsole using the CAPI Certificate option. The SmartConsole administrator does not need to provide a password.
To create a certificate file:
The certificate file is in the PKCS #12 format, and has a .p12
extension.
Note - Give the certificate file and the password to the SmartConsole administrators. The administrator must provide this password when logging in to SmartConsole with the Certificate File option.
To Import the certificate file to the CAPI repository:
If you want to use the same expiration settings for multiple accounts, you can set the default expiration for administrator accounts. You can also choose to show notifications about the approaching expiration date at the time when an administrator logs into SmartConsole or one of the SmartConsole clients. The remaining number of days, during which the account will be alive, shows in the status bar.
To configure the default expiration settings:
Use the SmartConsole in a secure manner, and enforce secure usage for all administrators. Setting a SmartConsole timeout is a basic requirement for secure usage. When an administrator is not using the SmartConsole, it logs out.
To set the SmartConsole timeout:
When a SmartConsole is idle after this number of minutes, the SmartConsole automatically logs out the connected administrator, but all changes are preserved.
To make sure your environment is secure, the best practice is to delete administrator accounts when personnel leave or transfer.
To remove an administrator account:
The Administrators pane shows by default.
If an administrator that authenticates through a certificate is temporarily unable to fulfill administrator duties, you can revoke the certificate for the account. The administrator account remains, but no one can authenticate to the Security Management Server with the certificate. However, if the account has an additional authentication method (a password, for example), that method can be used to authenticate to the account.
To revoke an administrator certificate:
A permission profile is a predefined set of Security Management Server and SmartConsole administrative permissions that you can assign to administrators. You can assign a permission profile to more than one administrator. Only Security Management Server administrators with the Manage Administrators permission in the profile can create and manage permission profiles.
To learn about permission profiles for Multi-Domain Security Management administrators, see the R80.10 Multi-Domain Security Management Administration Guide.
Administrators with Super User permissions can edit, create, or delete permission profiles.
These are the predefined, default permission profiles. You cannot change or delete the default permission profiles. You can clone them, and change the clones:
To change the permission profile of an administrator:
The Administrators properties window opens.
To change a permission profile:
To create a new permission profile:
The New Profile window opens.
To delete a permission profile:
You cannot delete a profile that is assigned to an administrator. To see which administrators use a profile, in the error message, click Where Used.
If the profile is not assigned to administrators, a confirmation window opens.
Configure administrator permissions for Gateways, Access Control, Threat Prevention, Others, Monitoring and Logging, Events and Reports, Management. For each resource, define if administrators that are configured with this profile can configure the feature or only see it.
Permissions:
Note - If you cannot clear a feature selection, the administrator access to it is mandatory.
Some features have Read and Write Options. If the feature is selected:
To configure customized permissions:
You can simplify the management of the Access Control Policy by delegating ownership of different Layers to different administrators.
To do this, assign a permission profile to the Layer. The permission Profile must have this permission: Edit Layer by the selected profiles in a layer editor.
An administrator that has a permission profile with this permission can manage the Layer.
Workflow:
To give Layer permissions to an administrator profile:
To assign a permission profile to a Layer:
In the Profile object, select the features and the Read or Write administrator permissions for them.
Access Control
To edit a Layer, a user must have permissions for all Software Blades in the Layer.
Threat Prevention
In the Profile object, select the features and the Read or Write administrator permissions for them.
Monitoring and Logging Features
These are some of the available features:
Events and Reports Features
These are the permissions for SmartEvent:
By default, any authenticated administrator can connect to the Security Management Server from any computer. To limit the access to a specified list of hosts, can configure Trusted Clients. You can configure Trusted Clients in these ways:
Administrators with Super User permissions can add, edit, or delete trusted clients.
To add a new trusted client:
The New Trusted Client window opens.
To change trusted client settings:
To delete a trusted client:
The confirmation window opens.
For administrators that login to the Security Management Server using a Check Point password, you can configure these login restrictions:
To configure login restrictions:
Note - these restrictions apply only to administrators that authenticate to the Security Management Server using a Check Point password.
An administrator who has the Manage Administrators permission can unlock another administrator if the locked administrator authenticates to the Security Management Server using a Check Point password.
To unlock an administrator:
Or:
Use the unlock administrator API command.
Note - the Unlock Administrator feature does not apply to administrators using other authentication methods.
Multiple administrators can work with SmartConsole on the same Security Management Server with the same policies at the same time. To avoid configuration conflicts, every administrator has their own username, and works in a session that is independent of the other administrators.
When an administrator logs in to the Security Management Server through SmartConsole, a new editing session starts. The changes that the administrator makes during the session are only available to that administrator. Other administrators see a lock icon on object and rules that are being edited. Changes are saved automatically.
Usually, an administrator will make changes to the policy in a private session and publish the changes when finished.
To make your changes available to other administrators, and to save the database before installing a policy, you must publish the session. When you publish a session, a new database version is created.
When you select Install Policy, you are prompted to publish all unpublished changes in the current session. You cannot install a policy if the included changes in the session are not published. Unpublished changes from other sessions will not be included in the policy installation.
Before you publish the session, you can add some informative attributes to it.
There is no need to save changes when working on a session. Changes are saved automatically. You can exit SmartConsole without publishing your changes from the session. You will see the changes next time you log into SmartConsole.
To publish a session:
In the SmartConsole toolbar, click Publish.
When a session is published, a new database version is created and shows in the list of database revisions.
To add a name or description to a session:
The Session Details window opens.
The validations pane in SmartConsole shows configuration error messages. Examples of errors are object names that are not unique, and the use of objects that are not valid in the Rule Base.
To publish, you must fix the errors.
You can see information about the SmartConsole sessions that are connected to the Security Management Server.
When an administrator changes objects, they are saved and locked. Another administrator with Manage Sessions permissions can unlock the changed objects, by publishing, or discarding the session. This allows other administrators to work with those objects. You can also publish, discard, or take over sessions that are disconnected. Disconnecting a session does not unlock the locked objects.
To see session information:
Click Manage & Settings > Sessions > View Sessions.
To unlock a session that is locked by another administrator:
Note - Publish your changes before you take over a session of another administrator, if you want to keep them. Otherwise, you lose those changes.
These instructions show how to configure authentication methods for administrators. For users, see Configuring Authentication Methods for Users.
For background information about the authentication methods, see Authentication Methods for Users and Administrators.
These instructions show how to configure Check Point Password authentication for administrators.
To configure a Check Point password for a SmartConsole administrator:
These instructions show how to configure OS Password Authentication for administrators.
To configure an OS password for a SmartConsole administrator:
These instructions show how to configure a RADIUS server for SmartConsole administrators. To learn how to configure a RADIUS server, refer to the vendor documentation.
To configure a RADIUS Server for a SmartConsole administrator:
The New Administrator window opens.
These instructions show how to configure a SecurID server for SmartConsole administrators. To learn how to configure a SecurID server, refer to the vendor documentation.
To configure the Security Management Server for SecurID:
sdconf.rec
file to the /var/ace/
folder If the folder does not exist, create the folder.
sdconf.rec
file full permissions. Run:chmod 777 sdconf.rec
To configure a SecurID Server for a SmartConsole administrator:
sdconf.rec
file. This must be a copy of the file that is on the Security Management Server.The New Administrator window opens.
These instructions show how to configure a TACACS server for SmartConsole administrators. To learn how to configure a TACACS server, refer to the vendor documentation.
To configure a TACACS Server for a SmartConsole administrator:
The New Administrator window opens.