Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Connect Secure" API to retrieve information about attack surface domains. Specifically, the "Retrieve Attack Surface Domain" operation fetches domain-related data from the attack surface, which can be useful for security analysts or IT teams monitoring their organization's external exposure.

Common scenarios include:

  • Gathering a list of domains associated with an organization's attack surface.
  • Filtering and sorting domain data based on specific conditions.
  • Paginating through large sets of domain records.

Practical example:
A security analyst wants to retrieve all attack surface domains related to a particular user ID, filter them by certain criteria (e.g., domain status), skip the first 10 records, limit the results to 50, and order them by creation date.

Properties

Name Meaning
X USER ID User Id - a required string header used to identify the user making the request.
Condition Query Condition - a string to filter the retrieved domains based on specified criteria.
Skip Skip No of Records - number of records to skip in the result set (for pagination).
Limit Limit - maximum number of records to return.
Order By Order By - string specifying the field(s) to sort the results by.

Output

The node outputs JSON data containing the retrieved attack surface domain records. The structure corresponds to the API response for domain data, typically including domain details such as domain name, status, creation date, and other metadata relevant to the attack surface.

No binary data output is indicated.

Dependencies

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

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors.
  • Invalid query parameters: Providing malformed or unsupported values in the condition, skip, limit, or order_by fields may result in API errors or empty responses.
  • API connectivity issues: Network problems or incorrect API credentials will prevent successful data retrieval.
  • Pagination mistakes: Setting skip or limit incorrectly might lead to unexpected subsets of data or no data returned.

To resolve these:

  • Ensure the X USER ID is correctly provided.
  • Validate query parameters against the API documentation.
  • Verify API credentials and network connectivity.
  • Adjust pagination parameters carefully.

Links and References

Discussion