Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Check Point Infinity Portal - Endpoint

By integrating Check Point Infinity Portal Endpoint with ThreatDefence via the Infinity Portal Logs as a Service API, you can ingest your endpoint security events into ThreatDefence for centralized monitoring and response.

This integration enhances visibility into:

  • Malware, ransomware and exploit detections on your devices

  • Threat Emulation and Threat Extraction verdicts on files

  • Compliance check results across your endpoints

  • Administrator activity in the Harmony Endpoint console

It enables more effective detection of compromised endpoints, malicious files and unauthorized changes to your endpoint protection.


Before you begin

  • You need an Infinity Portal account with permission to create account API keys.

  • Your devices must be managed by Harmony Endpoint from the Infinity Portal.

  • This integration collects one dataset:

    • Endpoint Security - the detections, compliance results and console activity Harmony Endpoint records.

  • Collection reads the events already held in the Infinity Portal. Nothing is installed on your endpoints.

Note: If Harmony Endpoint is managed from an on-premises Endpoint Security Management Server rather than the Infinity Portal, contact us before onboarding.


Step 1: Prepare Harmony Endpoint

  1. Deploy Harmony Endpoint from the Infinity Portal

    • Your devices must run the Harmony Endpoint client and be managed from the Infinity Portal. Their events are then held in the Infinity Portal, with nothing further to enable.

  2. Enable the protections you want monitored

    • Events come from the protections switched on in your Harmony Endpoint policies, such as Anti-Malware, Threat Emulation, Anti-Ransomware and Anti-Bot. A protection that is off produces no events.

  3. Confirm

    • In the Infinity Portal, open Endpoint Security and select Logs from the left navigation. Events from your devices should be listed.


Step 2: Create an API key

  1. Open the API Keys page

  2. Create a new account API key

    • Click New, then select New account API key.

    • Service: select Logs as a Service.

    • Role: select Admin. Logs as a Service offers no read-only role, and the key can only be used to search logs.

    • Expiration: set an expiry date and note it, as the key must be replaced before it expires.

    • Description: enter a descriptive name, for example ThreatDefence SIEM.

    • Click Create.

  3. Copy the three values shown

    • Client ID

    • Secret Key

    • Authentication URL

Note: The service must be Logs as a Service. A key created for any other service, including the older Infinity Events service, is refused.

For more information, refer to the Check Point documentation: Infinity Portal API Keys


Step 3: Identify your region

The Authentication URL shows the region your Infinity Portal account is hosted in. Find its address in the table below and note the region code.

Authentication URL begins with
Region code

https://cloudinfra-gw.ap.portal.checkpoint.com

AU

https://cloudinfra-gw.portal.checkpoint.com

EU

https://cloudinfra-gw-us.portal.checkpoint.com

US

https://cloudinfra-gw.ae.portal.checkpoint.com

UAE

https://cloudinfra-gw.in.portal.checkpoint.com

IN


Onboarding the integration

Please follow the Managing Integrations instructions and onboard the Check Point Infinity Portal integration. You will need:

  • Region - the region code from Step 3

  • Client ID

  • Client Secret - the Secret Key from Step 2

Note: On its first run, the integration collects the last 7 days of endpoint events. After that, endpoint events are collected every hour.

Note: If the Check Point Infinity Portal integration is already onboarded for another Check Point product, do not onboard it again: it collects endpoint events with the same key from its next run.


If you encounter difficulties with onboarding, please email the following to support@threatdefence.com:

  • Client ID

  • Secret Key - please send this via a PrivateShare , not plain email

  • Authentication URL, or the region code from Step 3

Note: Collection stops when the API key expires or is deleted. Before the expiry date, create a new key and send us its values so that collection continues without a gap.

Last updated