ReliaquestTakedown

This is Reliaquest DRP Takedown integration. It enables xsoar user to create and manage takedowns.

Vulnerability Management · ReliaQuest Digital Risk Protection

Details

IDReliaquestTakedown
ProviderReliaQuest
CategoryVulnerability Management
From Version6.9.0
Docker Imagedemisto/python3:3.12.13.10116658
Supported ModulesAgentix XSIAM

README

This is Reliaquest DRP Takedown integration. It enables xsoar user to create and manage takedowns.
This integration was integrated and tested with version 6.9.0 of ReliaquestTakedown.

This is the default integration for this content pack when configured by the Data Onboarder in Cortex XSIAM.

Configure ReliaquestTakedown in Cortex

Parameter Description Required
DS SearchLight API URL Enter the Digital Shadows SearchLight API URL. True
Account ID Account ID associated with this account. True
API Key Enter the API Key for this account. True
API Secret Enter the API Secret for this account. True
Trust any certificate (not secure) Verify certificate. False
First fetch timestamp (<number> <time unit>, e.g., 12 hours, 7 days, 2 months, 1 years or datetime in “%Y-%m-%d %H:%M:%S” format) First fetch False
Fetch Limit The maximum number of takedown to fetch. True
Takedown This controls how often the integration will perform a fetch takwdown command. False
Incident type   False
Fetch incidents   False

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.

rq-takedown-create


Create takedown command takes brand id, type, target and portal shortcode (optional) and returns the created takedown in response.

Base Command

rq-takedown-create

Input

Argument Name Description Required
brand_id Brand Id. Required
type Takedown Type. Required
target Target URL. Required
portal_id Portal shortcode. Optional

Context Output

There is no context output for this command.

rq-takedown-list-brand


Returns list of allowed brand details for takedown.

Base Command

rq-takedown-list-brand

Input

| Argument Name | Description | Required |
| — | — | — |

Context Output

There is no context output for this command.

rq-takedown-create-comment


Create comment for a takedown.

Base Command

rq-takedown-create-comment

Input

Argument Name Description Required
comment Comment for takedown. Default is Investigate the tekedown. Required
takedown_id Takedown id. Default is UUID. Required

Context Output

There is no context output for this command.

rq-takedown-upload-attachment


Uploads attachment for takedown.

Base Command

rq-takedown-upload-attachment

Input

Argument Name Description Required
file_id No description provided. Required
takedown_id No description provided. Required

Context Output

There is no context output for this command.

rq-takedown-download-attachment


Downloads attachment for takedown.

Base Command

rq-takedown-download-attachment

Input

Argument Name Description Required
attachment_id No description provided. Required

Context Output

There is no context output for this command.

Incident Mirroring

You can enable incident mirroring between Cortex XSOAR incidents and ReliaquestTakedown corresponding events (available from Cortex XSOAR version 6.0.0).
To set up the mirroring:

  1. Enable Fetching incidents in your instance configuration.

Newly fetched incidents will be mirrored in the chosen direction. However, this selection does not affect existing incidents.
Important Note: To ensure the mirroring works as expected, mappers are required, both for incoming and outgoing, to map the expected fields in Cortex XSOAR and ReliaquestTakedown.

Configuration parameters

  • searchLightUrl — DS SearchLight API URL (required)
  • accountId — Account ID (required)
  • apiKey — (required)
  • apiSecret — (required)
  • insecure — Trust any certificate (not secure)
  • first_fetch — First fetch timestamp (<number> <time unit>, e.g., 12 hours, 7 days, 2 months, 1 years or datetime in "%Y-%m-%d %H:%M:%S" format)
  • max_fetch — Fetch Limit (required)
  • incidentFetchInterval — Takedown
  • incidentType — Incident type
  • isFetch — Fetch incidents

Commands (5)

  • rq-takedown-create

    Create takedown command takes brand id, type, target and portal shortcode (optional) and returns the created takedown in response.

  • rq-takedown-create-comment

    Create comment for a takedown.

  • rq-takedown-download-attachment

    Downloads attachment for takedown.

  • rq-takedown-list-brand

    Returns list of allowed brand details for takedown.

  • rq-takedown-upload-attachment

    Uploads attachment for takedown.

#### Integration Author: ReliaQuest
Support and maintenance for this integration are provided by the author. Please use the following contact details:
- **Email**: [drpsupport@reliaquest.com](mailto:drpsupport@reliaquest.com)
- **URL**: [https://www.reliaquest.com/](https://www.reliaquest.com/)
***
This is Reliaquest DRP Takedown integration. It enables xsoar user to create and manage takedowns.

This integration fetches takedown.

## ReliaQuest GreyMatter DRP Takedown
ReliaQuest's Managed Takedown service provides customers with end-to-end takedown management that quickly removes infringing content, domains, documents and mobile applications. 
 
Working with ReliaQuest's GreyMatter Digital Risk Protection, the Managed Takedown service removes malicious or infringing content from various websites, platforms, stores and domain registrars. Left unresolved, these issues can lead to a loss of revenue, brand damage and loss of customer trust. ReliaQuest removes the burden of takedown management, enabling organizations to easily take swift action that minimizes their digital risk. 
Contact your ReliaQuest GreyMatter DRP representative to obtain API credentials.

### Overview: 
- **Submit a takedown**
- **Add comments to a takedown** 
- **Attach evidence and attachments to a takedown** 
- **Activity log and takedown status** 

To authenticate the integration, you must have a username, password and account ID. To get the account ID, see [here](https://portal-digitalshadows.com/api/stored-objects/portal/searchlight-api-docs/SearchLightAPI_APIKey_AccountId2.pdf).