Actions21
- Digital Footprint Actions
- Dark Web Monitoring Actions
- Incident Actions
- Takedown Actions
- User Audit Logs Actions
- DRP Fraud Protection Actions
- Brand Protection Actions
Overview
This node integrates with the SOCRadar API to provide various cybersecurity-related data and services. Specifically, for the Dark Web Monitoring resource with the Get Blackmarket Data operation, it retrieves information about blackmarket activities related to a specified company. This can help security teams monitor potential threats, leaked credentials, or other malicious activities involving their organization on dark web marketplaces.
Common scenarios include:
- Monitoring if company data has been exposed or sold on dark web forums.
- Investigating suspicious activity or breaches by querying recent blackmarket listings.
- Filtering results by date range, search terms, and pagination to focus on relevant data.
Practical example: A security analyst wants to check if any sensitive company information has appeared on dark web markets in the last month. They use this node to query blackmarket data filtered by date and keywords related to their company.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company to query blackmarket data for. |
| Additional Fields | Optional filters and pagination controls: |
| - From Date | Start date to filter blackmarket data from (inclusive). |
| - To Date | End date to filter blackmarket data until (inclusive). |
| - Page | Page number for paginated results (default is 1). |
| - Limit | Number of results per page (default is 100). |
| - Search Term | Keyword or phrase to filter blackmarket data results. |
Output
The node outputs an array of JSON objects representing blackmarket data entries related to the specified company. Each entry typically contains details such as:
- Information about the blackmarket listing.
- Relevant metadata like dates, descriptions, and possibly threat indicators.
If errors occur during the API call, the output may contain error messages and additional details explaining the failure.
The node does not output binary data.
Dependencies
- Requires an active SOCRadar API key credential configured in n8n.
- Needs network access to the SOCRadar API endpoint specified by the base URL in the credentials.
- No other external dependencies are required.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect Company ID or parameters may result in empty or error responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the SOCRadar API are captured and included in the output under
erroranddetails. - If the node is set to continue on failure, these errors appear alongside the corresponding input item.
- To resolve errors, verify API credentials, parameter correctness, and network connectivity.
- Errors returned from the SOCRadar API are captured and included in the output under
Links and References
- SOCRadar Official Website
- SOCRadar API Documentation (for detailed API usage and parameters)