AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to update an Endpoint Detection and Response (EDR) record by sending a PATCH request with specified fields. It allows users to modify certain attributes of an EDR entry, such as flags related to firewall status, ransomware protection, or regex usage, identified by an ID. This operation is useful in scenarios where security configurations or metadata about endpoints need to be updated dynamically based on new information or policy changes.

Practical examples include:

  • Updating the firewall status of an endpoint after a security audit.
  • Modifying detection rules or flags for ransomware protection on specific devices.
  • Adjusting regex-based detection parameters for endpoint monitoring.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API header.
Additional Body Fields Optional fields to include in the PATCH request body:
- Data: JSON object containing boolean flags such as regex, is_firewall, is_antirandsome.
- Id: Numeric identifier of the EDR record to update.

Output

The node outputs the JSON response returned from the PATCH request to the EDR API. This typically includes the updated EDR record details reflecting the changes made. The output does not explicitly handle binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard ConnectSecure service.
  • Needs the base URL of the API configured in the credentials.
  • Uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is provided and correctly formatted.
  • Invalid or missing EDR record ID: The id field must correspond to an existing EDR record; otherwise, the API may return a not found or validation error.
  • Malformed JSON in Data field: The data property expects valid JSON; syntax errors will cause request failures.
  • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • API connectivity issues: Check network access to the configured base URL and ensure the API service is reachable.

Links and References

Discussion