Identity Collector - Working with a Cisco Identity Services Engine (ISE) Server

You can configure Identity CollectorClosed Check Point dedicated client agent installed on Windows Servers in your network. Identity Collector collects information about identities and their associated IP addresses and sends it to the Check Point Security Gateways for identity enforcement, you can download the Identity Collector package from the Support Center. to take identity information from Cisco ISE servers over Platform Exchange Grid (PXGrid) send it to Identity Servers for identity-based enforcement.

To configure the Identity Collector to work with Cisco ISE:

  1. In the Identity Collector, add a new Cisco ISE Server as an Identity Source.

  2. In the Identity Collector, add a new Query Pool, or edit a current Query Pool.

    See Identity Collector - Query Pools.

  3. In the Identity Collector, add a new Filter for the login events, or edit a current Filter.

    See Identity Collector - Filters for Login Events.

  4. Connect the Identity Collector to the Check Point Identity ServerClosed Check Point Security Gateway with enabled Identity Awareness Software Blade..

    See Identity Collector - Connecting to an Identity Awareness Gateway

Parsing Events with "Postured" Status as Login Events

By default, Identity Collector does not parse Cisco ISE events with "Postured" status as login events in Cisco PxGrid 2.0. To configure Identity Collector to parse such events, set values of Windows Registry parameters on the server where Identity Collector is installed. This feature is available starting from Identity Collector version 82.120.0000.

Prerequisites

  • The "state" of the Cisco ISE event must be "Postured".

  • The Cisco ISE event must include a "postureStatus" with one of these values:

    • Compliant

    • Pending

    • NonCompliant

    • Unknown

Example Event

This is an example of a "Postured" Cisco ISE event that Identity Collector can parse.

Copy
{
"sessions": [
{
...
"state": "POSTURED",
"userName": "USER",
"ipAddresses": [
"1.2.3.4"
],
...
"postureStatus": "Compliant",
...
}
],
...
}

To configure Identity Collector to parse events with "Postured" status:

  1. On the Windows server where Identity Collector is installed, stop the Identity Collector service.

  2. In the Windows registry, go to "HKLM\SOFTWARE\WOW6432Node\CheckPoint\IdentityCollector\".

  3. Set the value of the "EnableIsePosturedEvents" registry key to 1.

  4. Set the value of the "AcceptablePostureEvents" registry key to one or more posture statuses for Identity Collector to parse as login events. Put a semicolon between names of posture statuses.

    For example: Compliant;Pending;NonCompliant;Unknown

  5. Start the Identity Collector service.