Loading

Check Point Harmony Endpoint

<div class="condensed-table">
| | |
| --- | --- |
| Version | 0.2.1 [beta] (View all) |
| Compatible Kibana version(s) | 8.14.0 or higher |
| Supported Serverless project types
What’s this? | Security
Observability |
| Subscription level
What’s this? | Basic |
| Level of support
What’s this? | Elastic |

</div>
The Check Point Harmony Endpoint integration allows you to ingest data from Harmony Endpoint management service(https://www.checkpoint.com/harmony/endpoint/).

Harmony Endpoint EPMaaS (Endpoint Management as a Service) is the cloud service to manage policies and deployments for Endpoint Security. It provides advanced threat prevention and detection capabilities to safeguard endpoints from malware, ransomware, and other sophisticated attacks. The solution offers real-time protection through behavioral analysis, machine learning, and threat intelligence.

For details please refer to the Harmony Endpoint Admin guide

  1. Server URL
  2. Client ID
  3. Secret key

To use this integration generate an API Key. API key consists of Client ID and Secret Key. Users can create API Keys by browsing to Infinity Portal at GLOBAL SETTINGS > API Keys. When creating an API Key, make sure that Service is set to Logs as a Service.

To create an API key please refer to Check Point’s Infinity API Guide. A list of servers can also be found there.

  1. Initial Interval: Initial interval for which existing logs will be pulled.
  2. Interval: Interval at which new logs will be pulled.
  3. Limit: Sets the number of results to return per API search query.
  4. Page Limit: Sets the number of results to return per page, in API search query.
  1. In Kibana go to Management > Integrations
  2. In "Search for integrations" search bar, type Check Point Harmony Endpoint
  3. Click on the "Check Point Harmony Endpoint" integration from the search results.
  4. Click on the "Add Check Point Harmony Endpoint" button to add the integration.
  5. Add all the required integration configuration parameters, such as Server URL, Client ID, Secret Key. For all data streams, these parameters must be provided in order to retrieve logs.
  6. Save the integration.
  1. Anti-bot: This is behavioral protection against bots. A single bot can create multiple threats. Cybercriminals often use bots in Advanced Persistent Threat (APT) attacks to target specific individuals or organizations.
  2. Anti-Malware: Protects computers from viruses, spyware, and other malicious software. It uses real-time and scheduled scans to detect and neutralize threats before they can harm your computer.
  3. Forensics: This component monitors file operations, processes, and network activity for suspicious behavior. It analyzes attacks detected by other client components or the Check Point Security Gateway and applies remediation to malicious files.
  4. Threat Emulation: Detects zero-day and unknown attacks. Files on the endpoint computer are sent to a sandbox for emulation to uncover evasive zero-day attacks.
  5. Threat Extraction: Proactively protects users from downloaded malicious files. It quickly delivers safe files while inspecting the originals for potential threats.
  6. URL Filtering: Defines which websites are accessible within your organization. The URL Filtering policy consists of selected sites and the mode of operation applied to them.
  7. Zero-phishing: Examines various website characteristics to ensure a site isn’t impersonating another to maliciously collect personal information. It generates alerts for potential phishing sites.

This is Anti-bot dataset.

A range of ECS fields are also exported. They are described in the ECS documentation.

This is Anti-Malware dataset.

A range of ECS fields are also exported. They are described in the ECS documentation.

This is Forensics dataset.

A range of ECS fields are also exported. They are described in the ECS documentation.(/ecs/docs/reference/ecs/ecs-field-reference.md)

This is Threat Emulation dataset.

A range of ECS fields are also exported. They are described in the ECS documentation.(/ecs/docs/reference/ecs/ecs-field-reference.md)

This is Threat Extraction dataset.

A range of ECS fields are also exported. They are described in the ECS documentation.(/ecs/docs/reference/ecs/ecs-field-reference.md)

This is URL Filtering dataset.

A range of ECS fields are also exported. They are described in the ECS documentation.(/ecs/docs/reference/ecs/ecs-field-reference.md)

This is Zero-Phishing dataset.

A range of ECS fields are also exported. They are described in the ECS documentation.(/ecs/docs/reference/ecs/ecs-field-reference.md)