Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to update Endpoint Detection and Response (EDR) settings. Specifically, the "Update Edr" operation allows users to modify properties of an existing EDR record by specifying its ID and providing updated data fields. This is useful in scenarios where security configurations need to be adjusted dynamically, such as toggling firewall or anti-ransomware protections on endpoints.

Practical examples include:

  • Updating an endpoint's security profile to enable or disable firewall rules.
  • Adjusting detection parameters like regex matching for threat signatures.
  • Modifying anti-ransomware settings based on new threat intelligence.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking purposes in the API request header.
Data JSON object containing the EDR configuration fields to update. Options include:
- regex (boolean): Enable or disable regex matching.
- is_firewall (boolean): Enable or disable firewall protection.
- is_antirandsome (boolean): Enable or disable anti-ransomware protection.
Id Numeric identifier of the EDR record to update.

Output

The node outputs JSON data representing the response from the Connect Secure API after updating the specified EDR record. The structure typically includes confirmation of the update and possibly the updated EDR details. There is no indication that binary data is returned by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure service being accessible.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID in the request headers. Ensure this property is set correctly; otherwise, the request may be rejected.
  • Invalid or missing EDR Id: The numeric ID must correspond to an existing EDR record. Using an incorrect ID will result in errors or no updates applied.
  • Malformed JSON in Data: The Data field must be valid JSON. Improper formatting can cause parsing errors.
  • API Authentication Errors: If the API key credential is missing or invalid, the node will fail to authenticate.
  • Network Issues: Connectivity problems with the Connect Secure API endpoint will prevent successful updates.

Links and References

  • Connect Secure API documentation (refer to official vendor resources for detailed API specs).
  • n8n documentation on creating and using custom nodes with API credentials.

Discussion