---
title: Configuring Check Point Next-Generation Firewall
slug: configuring-check-point-next-generation-firewall
createdAt: 2026-07-27T04:11:10.540Z
---

Check Point firewall detects traffic from an endpoint that matches a configured security policy using the access roles. It determines the role(s) associated with that user, and allows or denies the traffic based on the actions configured in the security policy.

The network interfaces are configured on the Check Point Next-Generation firewall and the remaining configurations are done on the Check Point Smart Console.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/stZLT1ehMpgNjPh8BEfu2_configuringcheckpointnextgenerationfirewall.png" position="flex-start" size="80" width="1591" height="691" initialPath="images/configuring_check_point_next_generation_firewall.png" githubPath="images/configuring_check_point_next_generation_firewall.png" darkWidth="1591" darkHeight="691" showCaption="false"}

### Configuring Identity Awareness in SmartConsole

The Identity Awareness lets you easily configure network access and auditing based on network location, identity of user, and identity of the device. When Identity Awareness identifies a source or destination, it shows the IP address of the user or computer with a name. For example, this lets you create firewall rules with any of these properties. You can define a firewall rule for specific users when they send traffic from specific computers or a firewall rule for a specific user regardless of which computer they send traffic from.

To enable Identity awareness:

1. Login to the Check Point SmartConsole.
2. From the **Security & Gateways view**, double-click the Security Gateway on which to enable identity awareness.:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/MWNFv6Qq0tMeVxAiC33X-_smartconsole.png" alt caption size="80" width="1026" height="559"}
3. Create an object for IPS. Select **Objects > New Host&#x20;**&#x61;nd enter the IPS IP address. Under Servers, enable Web Server and click **OK**.:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/5Hxu7NWOrBrlgoE4DXV-V_host.png" alt caption size="80" width="1063" height="354"}
4. Select **Gateways & Servers > Identity Awareness** and enable the following options:
   - **Terminal Servers**- Note down the pre-shared secret key.
   - **Identity Web API-** Click **Settings** and add the IPS device as Authorised Clients.

:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/4jx7h881tS5QMuflxA9wd_identityawareness.png" alt caption size="80" width="995" height="695"}

5. Click **Install Policy.**
6. From the Object Explorer create an object for Identity matching by creating user roles. Select Objects > Object Explorer and Click **New > Users > Access Role**.

:::hint{type="info"}
The role names must match with the Role names created on IPS.
:::

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/R8uPp9iafDLQ2oKXtBlFV_creatingaccessroles.png" position="flex-start" size="61" width="611" height="404" initialPath="images/creating_access_roles.png" githubPath="images/creating_access_roles.png" showCaption="false"}

1. From the SmartConsole, create a security policy by keeping the Access Role in Source column. Select **Security Policies > Access Control > Policy** and then configure the required policies. For example, Full\_Access policy allows traffic from Client with Full\_Access role, Limited\_Access role policy denies traffic from Client with Limited\_Acces role, and default\_allow policy which allows all traffic. The Full\_Access role is on the top of the list since it should be considered first. :inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/wU81pFDoLI0MD6EHI5WkJ_securitypolicybasedonaccessroles.png" alt caption size="80" width="1031" height="305"}
2. Click **Install Policy**.
