Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Attack Surface" resource of the Connect Secure API, specifically to update an existing attack surface domain. It allows users to modify properties of a domain related to their security posture or asset inventory by sending updated data to the API.

Common scenarios include:

  • Marking a domain for later scanning (scanlater flag).
  • Updating domain metadata or configuration dynamically.
  • Automating domain management as part of a security workflow.

For example, a user might set "scanlater": true to defer scanning of a domain until a later time, helping prioritize resources.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Data JSON object containing the fields and values to update on the attack surface domain. Example: { "scanlater": true }.
Id Numeric identifier of the attack surface domain to update.

Output

The node outputs the JSON response from the API after updating the attack surface domain. This typically includes confirmation of the update, the updated domain details, or error information if the update failed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the external Connect Secure service being accessible.
  • Uses the OpenAPI specification bundled within the node for request construction.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure this property is correctly set.
  • Invalid domain Id: Providing a non-existent or incorrect domain Id will cause update failures.
  • Malformed JSON in Data: The data property must be valid JSON; otherwise, the request body will be rejected.
  • API connectivity issues: Network problems or incorrect credentials can cause errors connecting to the Connect Secure API.

Error messages usually come directly from the API and should be checked for hints such as authentication failure, validation errors, or permission issues.

Links and References

Discussion