Check Point Harmony

Connect Check Point Harmony to collect endpoint detection & response evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Check Point Harmony:

   1. In the Check Point Infinity Portal, go to Global Settings › API Keys.
   2. Click New › New account API key.
   3. In the Create a New API Key window, select the Harmony Endpoint service as the Service.
   4. If a Role list is shown for the service, pick the most restrictive read-only role offered.
   5. Set an expiration date and time, and optionally a Description, then create the key.
   6. Copy the Client ID and Secret Key (paste the Secret Key into Safeguard's Access key field), and note the Authentication URL.

   Where to find the other values:

   • Client ID: Shown as Client ID in the Create a New API Key window, and in the API Keys list.
   • Region: The Authentication URL shown when the key is created identifies the regional gateway for your tenant; choose the matching region in Safeguard.

   Check Point Harmony shows the secret only once, so copy it before you leave the page.

   Check Point Harmony's public documentation does not cover every step.

   The Secret Key and Authentication URL cannot be retrieved after the Create a New API Key window closes; the Client ID stays visible in the API Keys table. The fetched page does not list the service names or the role names for the Harmony Endpoint service.

   Source: sc1.checkpoint.com, checked 2026-10-07.

   The permissions Safeguard needs: Endpoint: Read-only.

2. On Compliance › Connectors, open Check Point Harmony, click Connect, choose API token and fill in:

   Field	What to enter
   Region	Required.
   Client ID	Required.
   Access key	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Check Point Harmony and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Endpoint Detection & Response connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks