Identity Cache Mode for Identity Sharing Protocols

Overview

Identity AwarenessClosed Check Point Software Blade on a Security Gateway that enforces network access and audits data based on network location, the identity of the user, and the identity of the computer. Acronym: IDA. operates with a default setting that adheres to a stringent approach to handle acute error flows.

This involves implementing the "prefer to delete" principle, which leads to the widespread deletion of identities in specific error scenarios.

The outcome of the behavior described above:

  • No Identity-based enforcement, and connectivity is broken.

  • Performance impact as a result of running and propagating the massive identity deletion logic.

  • Lack of resiliency, even in cases where the environment was designed to have alternative identity propagation paths.

  • In large scale environments, it may take hours until the system is fully recovered.

Identity Awareness Gateway R82 and higher uses the Identity Cache Mode for Identity Sharing protocols.

Important - In R82 and higher, the Identity Cache Mode is enabled by default with a cache duration of 1 hour.

The Identity Cache Mode follows the "prefer to keep" principle, enabling Identity Awareness to regain stability without causing the aforementioned disruptions.

This approach prioritizes maintaining system integrity while addressing the issues highlighted earlier.

  • Instead of conducting extensive deletions, the relevant identities are kept in the database.

    • PDP-to-PEP sharing - By default, 24 hours.

    • PDP-to-PDP sharing - By default, 1 hour (configurable).

  • Allows identity propagation from alternative paths to overrun existing information at all times.

    • Conciliation decision for the existing relevant Identity Sessions is "overwrite".

  • Upon the restoration of connectivity, assuming that the Identity Session has not been overwritten, the pertinent Identity Sessions undergo a "refresh" process, reverting to their initial state and logic.

Upgrade from the R81.20 Jumbo Hotfix Accumulator to R82

The Identity Cache Mode feature is available in the R81.20 Jumbo Hotfix AccumulatorClosed Collection of hotfixes combined into a single package. Acronyms: JHA, JHF, JHFA., Take 70 and higher.

In the R81.20 Jumbo HotfixClosed Software package installed on top of the current software version to fix a wrong or undesired behavior, and to add a new behavior. Accumulator, this feature is disabled by default and has a different default timeout for PDP-to-PDP sharing (24 hours).

During an upgrade to R82, the previous configuration is preserved.

Viewing the Current Status of the Identity Cache Mode

Configuring the Identity Cache Mode on All Security Gateways

The default configuration for all Identity Awareness Gateways managed by a Security Management ServerClosed Dedicated Check Point server that runs Check Point software to manage the objects and policies in a Check Point environment within a single management Domain. Synonym: Single-Domain Security Management Server. / Domain Management ServerClosed Check Point Single-Domain Security Management Server or a Multi-Domain Security Management Server.:

  1. The Identity Cache Mode is enabled.

  2. The timeout for the PDP-to-PDP sharing protocol (Identity Broker) is 60 minutes.

You can change the global configuration in SmartConsoleClosed Check Point GUI application used to manage a Check Point environment - configure Security Policies, configure devices, monitor products and events, install updates, and so on. or with the Management API.

Configuring the Identity Cache Mode on Specific Security Gateways

You can override the global Identity Cache Mode configuration on each managed Security Gateway / ClusterClosed Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing. / Scalable Platform Security Group / VSNext Virtual Gateway / Legacy VSX Virtual System.

Important:

  • To override the global configuration, you must use the Management API to configure the applicable Identity Awareness Gateway object.

  • After you change the configuration of an Identity Awareness Gateway object, you must install the Access Control Policy on that object.