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 comprehensive cybersecurity data and monitoring capabilities. Specifically, for the Dark Web Monitoring resource with the Get PII Exposure operation, it retrieves information about personally identifiable information (PII) exposures related to a specified company. This is useful for organizations wanting to monitor if sensitive company data has been leaked or exposed on the dark web.
Common scenarios include:
- Security teams tracking potential data breaches involving their company.
- Compliance officers verifying exposure of sensitive customer or employee data.
- Incident response teams investigating the scope of a data leak.
Practical example: A security analyst inputs a company ID and optional filters such as date range or search terms to fetch recent PII exposure incidents from the dark web, enabling timely mitigation actions.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company for which to retrieve PII exposure data. |
| Additional Fields | Optional filters and pagination controls: |
| - From Date | Start date to filter results by exposure occurrence. |
| - To Date | End date to filter results by exposure occurrence. |
| - Page | Page number for paginated results (default 1). |
| - Limit | Number of results per page (default 100). |
| - Search Term | Text term to filter the exposure results by matching content. |
Output
The node outputs an array of JSON objects representing PII exposure records retrieved from the SOCRadar API. Each item contains details about the exposure incident, such as exposed data types, timestamps, and possibly affected entities.
If errors occur during execution, the output may include error messages and additional details explaining the failure.
No binary data output is indicated in the source code.
Dependencies
- Requires an active SOCRadar API key credential configured in n8n.
- The node makes HTTP requests to the SOCRadar API base URL using this API key.
- No other external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect or missing Company ID parameter will result in no data or errors.
- Network connectivity problems can prevent API calls.
- Pagination parameters exceeding available pages may return empty results.
Error messages:
- Errors returned from the SOCRadar API are captured and included in the output under
json.errorandjson.details. - If the node is set to continue on failure, it will output error details instead of stopping execution.
- Typical errors include authentication failures, invalid parameters, or rate limiting.
- Errors returned from the SOCRadar API are captured and included in the output under
Resolution tips:
- Verify the API key credential is correctly set up and valid.
- Ensure the Company ID is correct and corresponds to an existing entity in SOCRadar.
- Adjust pagination and date filters to valid ranges.
- Check network access and proxy settings if applicable.
Links and References
- SOCRadar Official Website
- SOCRadar API Documentation (for detailed API endpoints and parameters)
- n8n Documentation on Using Credentials