Group-IB Digital Risk Protection
Pack helps to integrate Group-IB Digital Risk Protection and get violations incidents directly into Cortex XSOAR.
Data Enrichment & Threat Intelligence · Group-IB Digital Risk Protection
Details
| ID | Group-IB Digital Risk Protection |
|---|---|
| Category | Data Enrichment & Threat Intelligence |
| From Version | 6.10.0 |
| Docker Image | demisto/vendors-sdk:1.0.0.10120494 |
README
Pack helps to integrate Group-IB Digital Risk Protection and get violations incidents directly into Cortex XSOAR.
This integration was integrated and tested with version 1.0 of Group-IB Digital Risk Protection.
Configure Group-IB Digital Risk Protection in Cortex
| Parameter | Description | Required |
|---|---|---|
| GIB DRP URL | True | |
| Fetch incidents | False | |
| Incident type | False | |
| Trust any certificate (not secure) | False | |
| Use system proxy settings | False | |
| Incidents Fetch Interval | False | |
| Username | True | |
| Password | True | |
| Violation Section to filter the received Violation | False | |
| Brands to filter the received Violation | Brands for filtering received violations. The list of available brands can be obtained with the command !gibdrp-get-brands in the menu WarRoom -> Playground. After getting the brands you must specify the brand ID for which you want to receive violations. Attention! Currently filtering is available only by one brand in one Instance | False |
| Incidents first fetch | Date to start fetching incidents from. | False |
| Download images | Enables or disables loading of each image in each violation. Can significantly affect the speed of data collection if the parameter is enabled, i.e. set to True | False |
| Getting Typosquatting only | Allows for the collection of offenses suitable only for Typo Squatting | False |
| Number of requests per collection | A number of requests per collection that integration sends in one fetch iteration (each request picks up to 30 incidents). If you face some runtime errors, lower the value. | True |
Commands
You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.
gibdrp-get-brands
Receive all configured brands.
Base Command
gibdrp-get-brands
Input
| Argument Name | Description | Required |
| — | — | — |
Context Output
| Path | Type | Description |
|---|---|---|
| GIBDRP.OtherInfo | string | List of configured brands. |
| GIBDRP.OtherInfo.brands.name | string | Brand name. |
| GIBDRP.OtherInfo.brands.id | string | Brand ID. |
Command example
#### Context Example
```json
{
"GIBDRP": {
"OtherInfo": {
"brands": [
{
"id": "PvY1BZUBSFbLZGo2x8TA",
"name": "Example Brand"
}
]
}
}
}
Human Readable Output
Installed Brands
Name Id Example Brand PvY1BZUBSFbLZGo2x8TA
gibdrp-get-subscriptions
Receive all configured subscriptions.
Base Command
gibdrp-get-subscriptions
Input
| Argument Name | Description | Required |
| — | — | — |
Context Output
| Path | Type | Description |
|---|---|---|
| GIBDRP.OtherInfo | string | List of configured subscriptions. |
| GIBDRP.OtherInfo.subscriptions | string | Subscriptions list. |
Command example
#### Context Example
```json
{
"GIBDRP": {
"OtherInfo": {
"subscriptions": [
"scam"
]
}
}
}
Human Readable Output
Purchased subscriptions
Subscriptions scam
gibdrp-get-violation-by-id
Getting a single violation by its ID.
Base Command
gibdrp-get-violation-by-id
Input
| Argument Name | Description | Required |
|---|---|---|
| id | ID violation. | Required |
Context Output
| Path | Type | Description |
|---|---|---|
| GIBDRP.Violation.id | string | Violation ID. |
| GIBDRP.Violation.title | string | Violation title. |
| GIBDRP.Violation.description | string | Violation description. |
| GIBDRP.Violation.status | string | Violation status. |
| GIBDRP.Violation.violation_uri | string | Violation URI. |
| GIBDRP.Violation.source | string | Violation source section. |
| GIBDRP.Violation.detected | date | Detected timestamp. |
gibdrp-change-violation-status
Changing the status of a single violation.
Base Command
gibdrp-change-violation-status
Input
| Argument Name | Description | Required |
|---|---|---|
| id | ID violation. | Required |
| status | What status to change to. Possible values are: approve, reject. | Required |
Context Output
There is no context output for this command.
Configuration parameters
url— GIB DRP URL (required)isFetch— Fetch incidentsincidentType— Incident typeinsecure— Trust any certificate (not secure)proxy— Use system proxy settingsincidentFetchInterval— Incidents Fetch Intervalcredentials— Username (required)violationSection— Filter by Violation Typebrands— Filter by Brandfirst_fetch— Incidents first fetchdownload_images— Download imagesonly_typosquatting— Get Typosquatting Onlymax_fetch— Number of requests per collection (required)
Commands (4)
-
gibdrp-change-violation-statusChanging the status of a single violation.
-
gibdrp-get-brandsReceive all configured brands.
-
gibdrp-get-subscriptionsReceive all configured subscriptions.
-
gibdrp-get-violation-by-idGetting a single violation by its ID.
### Group-IB Digital Risk Protection - This section explains how to configure the **Digital Risk Protection** instance in **Cortex XSOAR**. #### Step 1: Open the Group-IB TI Web Interface 1.1 Go to [https://drp.group-ib.com](https://drp.group-ib.com). #### Step 2: Authentication 2.1 In the new interface: - Log in to your account on DRP: [drp.group-ib.com](drp.group-ib.com) - Go to the your profile settings [direct link](https://drp.group-ib.com/p/info/api). - Click the big blue button **Generate API key**. Then an API key will show up nearby. - Don’t forget to save API key during generation. Success! Now you can use it with HTTP Basic Auth, where login is your email and password is your API token. #### Step 3: Set Up Connection Details 3.1 **Server URL:** Use your **DRP web interface URL**. 3.2 **Username:** The email address used to log in to the web interface. #### Step 4: Configure Classifier and Mapper 4.1 Set the **Classifier** and **Mapper** using the **Group-IB Digital Risk Protection** classifier and mapper. Note: Alternatively, you may configure your own setup if needed. #### Step 5: Configure Pre-Processing Rules 5.1 Navigate to **Settings → Integrations → Pre-Processing Rules**. If a rule already exists, open it and verify it performs the following action. Otherwise, create a new rule: - **Condition**: `"gibdrpid" is not empty (General)`. - **Action**: `Run a script`. - **Script**: `GIBDRPIncidentUpdate` – updates existing incidents without reopening those that were previously closed. #### Step 6: Whitelist Your Cortex XSOAR IP 6.1 Contact **Group-IB support** to add your **Cortex XSOAR IP** or the **proxy public IP** used with Cortex to the allowlist.