SOCRadar icon

SOCRadar

Comprehensive SOCRadar API integration

Overview

This node integrates with the SOCRadar API to perform various security-related operations. Specifically, for the Digital Footprint resource and the Toggle Monitoring operation, it allows users to enable or disable monitoring on a specific digital asset associated with a company. This can be useful in scenarios where an organization wants to start or stop tracking certain assets for security events or changes in their digital footprint.

Practical examples include:

  • Temporarily disabling monitoring on an asset that is under maintenance.
  • Re-enabling monitoring after resolving a false positive alert.
  • Managing which assets are actively tracked to optimize alerting and resource usage.

Properties

Name Meaning
Company ID The unique identifier of the company whose digital footprint assets are being managed.
Asset ID The unique identifier of the specific asset within the company's digital footprint to toggle monitoring on or off.

Output

The node outputs JSON data representing the result of the toggle monitoring action on the specified asset. This typically includes confirmation of the updated monitoring status or any relevant metadata returned by the SOCRadar API.

If an error occurs, the output JSON will contain an error field with the message and possibly additional details about the failure.

The node does not output binary data.

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.
  • Proper network connectivity to the SOCRadar service is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Incorrect Company ID or Asset ID may result in "not found" errors from the API.
    • Network connectivity problems can lead to request timeouts or unreachable host 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 fail, these errors do not stop execution but are reported per item.
    • To resolve errors, verify credentials, input IDs, and network access.

Links and References

Discussion