Skip to main content

CSCTakedowns

This Integration is part of the CSCDomainSecurity Pack.#

Supported versions

Available on Cortex XSOAR, Cortex XSIAM, and Cortex XPANSE.

This is a CSCTakedowns api for organizations. This integration was integrated and tested with version v3 of the CSC Fraud Protection (Takedowns) API.

Configure CSCTakedowns in Cortex#

ParameterDescriptionRequired
Server URLThe endpoint URLTrue
API KeyThe API Key to use for connectionTrue
Trust any certificate (not secure)False
Use system proxy settingsFalse

Access and Data Security#

You request access through the CSC service team at: phishing-response@cscglobal.com. The team will gather account details and access authorization to any accounts that will be used to access the API; and the API key will be generated and returned along with login credentials to access the API.

There is no token refresh or API expiration, all that is needed is to place the API key at the end of this URL: https://apis.cscglobal.com/dbs/fraud-protection/v1/fraud-protection-api/swagger/external/docs?APIKey={YOUR API KEY HERE} and signing in with the provided credentials on said page.

CSC generates the API key and authorizes access to accounts within the organization. These authorizations are checked and verified before any information is returned to ensure data security.

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.

csctakedowns-fetchthephishkitdatawithticketid#


Fetch the phishkit data with ticketId

Base Command#

csctakedowns-fetchthephishkitdatawithticketid

Input#

Argument NameDescriptionRequired
ticketIdTicket Id to fetch phishkit.Required

Context Output#

There is no context output for this command.

Context Example#

{
"CSCTakeDowns": {
"data": {
"phishkit": [
{
"kit": "blob",
"timeStamp": "2024-06-25T13:12:32"
}
],
"ticketId": 35607910
},
"message": "Data Fetched Successfully",
"status": "success"
}
}

csctakedowns-fetchthescreenshotdatawithticketid#


Fetch the screenshot data with ticketId

Base Command#

csctakedowns-fetchthescreenshotdatawithticketid

Input#

Argument NameDescriptionRequired
ticketIdTicket Id to fetch screenshot.Required

Context Output#

There is no context output for this command.

Context Example#

{
"CSCTakeDowns": {
"data": {
"screenshot": "blob",
"screenshotTimeStamp": "2024-06-25 13:12:21.553812",
"ticketId": "123456"
},
"message": "Data Fetched Successfully",
"status": "success"
}
}

csctakedowns-gethtmlsourcecodeforaticket#


Get HTML Source Code for a Ticket

Base Command#

csctakedowns-gethtmlsourcecodeforaticket

Input#

Argument NameDescriptionRequired
ticketIdTicket ID to fetch HTML source.Required

Context Output#

PathTypeDescription
CSCTakedowns.messageString
CSCTakedowns.statusString

Context Example#

{
"CSCTakeDowns": {
"code": "Ref00-14816",
"message": "Event is not found in the application for ticketId: 1234",
"status": "error"
}
}

csctakedowns-listofworklogsforticketid#


List of work logs for ticket id

Base Command#

csctakedowns-listofworklogsforticketid

Input#

Argument NameDescriptionRequired
ticketIdTicket ID to fetch work log details.Required

Context Output#

PathTypeDescription
CSCTakedowns.messageString
CSCTakedowns.statusString

Context Example#

{
"CSCTakeDowns": {
"status": "success",
"message": "Data Fetched Successfully",
"data": [
{
"timeStamp": "2026-06-26 17:56:01",
"title": "Event status changed from Monitoring to Inprogress by External API User",
"type": "Internal Communication",
"toAddress": null
}
]
}
}

csctakedowns-listtakedownevents#


List Takedown Events

Base Command#

csctakedowns-listtakedownevents

Input#

Argument NameDescriptionRequired
fromDateStart date in YYYY-MM-DD format.Required
toDateEnd date in YYYY--MM--DD format.Required
pagepage size.Optional
limitLimit between 100 and 500, default = 100.Optional

Context Output#

PathTypeDescription
CSCTakedowns.messageString
CSCTakedowns.statusString

Context Example#

{
"CSCTakeDowns": {
"status": "success",
"message": "Data Fetched Successfully",
"data": [],
"meta": {
"currentPage": 1,
"pageSize": 101,
"total": 0,
"hasPrevious": true,
"pages": 0,
"hasNext": false,
"previousPage": 0,
"nextPage": null
}
}
}

csctakedowns-listtakedowneventswithfilters#


List Takedown events with filters

Base Command#

csctakedowns-listtakedowneventswithfilters

Input#

Argument NameDescriptionRequired
fromDateStart date in YYYY-MM-DD format.Required
toDateEnd date in YYYY--MM--DD format.Required
brandIdFilter by Brand Id.Optional
fraudTypeType of the Fraud.Optional
ticketStatusTicket Status.Optional
DetectionDateFilter by Detection date.Optional
AuthorizationDateFilter by Authorization date.Optional
CompletedDateFilter by Closed date.Optional
pagepage size.Optional
limitLimit between 100 and 500, default = 100.Optional

Context Output#

PathTypeDescription
CSCTakedowns.messageString
CSCTakedowns.statusString

Context Example#

{
"CSCTakeDowns": {
"status": "success",
"message": "Data Fetched Successfully",
"data": [],
"meta": {
"currentPage": 1,
"pageSize": 101,
"total": 0,
"hasPrevious": true,
"pages": 0,
"hasNext": false,
"previousPage": 0,
"nextPage": null
}
}
}

csctakedowns-updatetheactionwithticketid#


Update the action with ticketId

Base Command#

csctakedowns-updatetheactionwithticketid

Input#

Argument NameDescriptionRequired
actionTicket action.Required

Context Output#

There is no context output for this command.

Context Example#

{
"CSCTakeDowns": {
"status": "200",
"message": "Updated Successfully",
"data": {
"ticketId": 62406,
"action": "OPEN"
}
}
}