AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation allows updating an Attack Surface Domain by sending a PATCH request with specified fields. It is useful for scenarios where you need to modify details of an existing attack surface domain, such as toggling scan settings or updating domain-specific data. For example, you might use this node to mark a domain for later scanning or update its metadata dynamically within an automated security workflow.

Properties

Name Meaning
X USER ID The user identifier required in the request header to authenticate or track the request.
Additional Body Fields Optional fields to include in the PATCH request body:
- Data JSON object representing additional data to update on the attack surface domain (e.g., {"scanlater": true}).
- Id Numeric identifier of the attack surface domain to update.

Output

The node outputs JSON data representing the response from the PATCH request to update the attack surface domain. This typically includes confirmation of the updated fields or the current state of the domain after the update. There is no indication that binary data is returned.

Dependencies

  • Requires an API key credential for authentication.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in the node credentials.
  • Depends on the external AvantGuard ConnectSecure service to process the PATCH request.

Troubleshooting

  • Missing or invalid X USER ID: The request will fail if the user ID header is not provided or incorrect. Ensure the "X USER ID" property is set correctly.
  • Invalid JSON in Data field: If the JSON in the "Data" field is malformed, the request may be rejected. Validate JSON syntax before input.
  • Incorrect Id value: Providing an invalid or non-existent domain ID will cause the update to fail. Verify the domain ID exists.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful requests. Check API endpoint and network access.
  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions.

Links and References

Discussion