SOCRadar icon

SOCRadar

Comprehensive SOCRadar API integration
Join our community

Actions21

Overview

This node integrates with the SOCRadar API to create takedown requests specifically for source code leaks. It allows users to report URLs where sensitive or proprietary source code has been exposed publicly, enabling organizations to initiate takedown procedures to protect their intellectual property and prevent unauthorized access.

Common scenarios include:

  • Detecting and reporting leaked source code repositories or files on public websites.
  • Automating the submission of takedown requests when a source code leak is identified by monitoring tools.
  • Prioritizing takedown requests based on severity to streamline incident response workflows.

Practical example:

  • A security team detects a URL hosting leaked company source code. Using this node, they submit a takedown request with relevant details such as company ID, URL, takedown type (e.g., data leak), and priority level to initiate removal actions via SOCRadar.

Properties

Name Meaning
Company ID The unique identifier of the company for which the takedown request is being created.
URL The web address where the source code leak is located and needs to be taken down.
Takedown Type The category of the takedown request. Options: Phishing, Malware, Brand Infringement, Data Leak.
Priority The urgency level of the takedown request. Options: Low, Medium, High, Critical.
Additional Fields Optional extra information including:
- Description: Details about the takedown request.
- Tags: Comma-separated tags associated with the request.

Output

The node outputs JSON data representing the result of the takedown creation request. This typically includes confirmation details from the SOCRadar API such as the status of the takedown request, identifiers, timestamps, and any messages returned by the service.

No binary data output is involved in this operation.

Dependencies

  • Requires an active SOCRadar API key credential configured in n8n.
  • Network connectivity to the SOCRadar API endpoint.
  • Proper configuration of the node with valid company IDs and URLs.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect or malformed URLs may lead to request rejections.
    • Missing required fields like Company ID or URL will prevent request submission.
    • Network issues can cause timeouts or unreachable errors.

  • Error Messages:

    • Errors returned from the SOCRadar API are captured and included in the output JSON under error and details.
    • If the node is set to continue on failure, it will return error details per item instead of stopping execution.
    • Common resolution steps include verifying API keys, ensuring all required parameters are provided, and checking network connectivity.

Links and References

Discussion