-
Notifications
You must be signed in to change notification settings - Fork 57
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1390 from SEKOIA-IO/feature/vg_checkpoint_harmony
Checkpoint Harmony docs
- Loading branch information
Showing
5 changed files
with
50 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
49 changes: 49 additions & 0 deletions
49
docs/xdr/features/collect/integrations/endpoint/checkpoint_harmony.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
uuid: ff53e0db-059b-4e16-ba90-8c4dbf5cee35 | ||
name: Checkpoint Harmony | ||
type: intake | ||
|
||
## Overview | ||
|
||
Check Point Harmony is the industry's first unified security solution for users devices and access. | ||
|
||
!!! warning | ||
Important note - This format is currently in beta. We highly value your feedback to improve its performance. | ||
|
||
{!_shared_content/operations_center/detection/generated/suggested_rules_ff53e0db-059b-4e16-ba90-8c4dbf5cee35_do_not_edit_manually.md!} | ||
|
||
{!_shared_content/operations_center/integrations/generated/ff53e0db-059b-4e16-ba90-8c4dbf5cee35.md!} | ||
|
||
## Configure | ||
|
||
### Create authentication credentials | ||
|
||
1. Login to your Checkpoint Harmony account and navigate to `Profile > Global Settings` | ||
|
||
![Global settings](/assets/instructions/checkpoint/checkpoint_global_settings.png) | ||
|
||
2. Go to `API Keys` and click on `New` | ||
|
||
![API Keys](/assets/instructions/checkpoint/checkpoint_new_key.png) | ||
|
||
3. Update required fields with next information and create `API Key`: | ||
* Service: Harmony Mobile (1) | ||
* Expiration: If you pass an empty field, it means that API Key will not expire until you delete it. (2) | ||
* Description: You can specify any description that you want. (3) | ||
* Roles: `Read-Only` | ||
|
||
![API Key Form](/assets/instructions/checkpoint/checkpoint_api_key_form.png) | ||
|
||
4. Copy values of `Client ID`, `Secret Key` and `Authentication URL` and save them for the configuration of the connector. | ||
|
||
### Create the intake | ||
|
||
To create the intake, go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format `Checkpoint Harmony`. | ||
|
||
### Pull events | ||
|
||
To start to pull events, you have to: | ||
|
||
1. Go to the [playbooks page](https://app.sekoia.io/operations/playbooks) and create a new playbook with the [Checkpoint Harmony](../../../automate/library/checkpoint.md) trigger | ||
2. Set up the module configuration with the Client ID, Client Secret and Authentication URL. | ||
3. Set up the trigger configuration with the intake key | ||
4. Start the playbook and enjoy your events |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters