Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Connect Secure" API to retrieve attack surface results. It is designed to query and fetch data related to an organization's external attack surface, which can include vulnerabilities, exposed assets, or other security-related findings. This node is beneficial for security analysts, IT teams, or automated workflows that need to monitor and analyze attack surface data continuously.

Practical examples:

  • Automatically retrieving the latest attack surface scan results to feed into a security dashboard.
  • Filtering attack surface data based on specific conditions (e.g., severity, asset type) for targeted alerts.
  • Paginating through large result sets by skipping and limiting records to manage data volume.

Properties

Name Meaning
X USER ID User Id header required for authentication or identification in the API request.
Condition Query condition to filter the attack surface results (e.g., filtering criteria).
Skip Number of records to skip, useful for pagination.
Limit Maximum number of records to return, controls the size of the result set.
Order By Field(s) to order the results by, allowing sorting of the returned data.

Output

The node outputs JSON data representing the retrieved attack surface results from the API. The structure typically includes details about each attack surface item such as identifiers, attributes, status, timestamps, and any metadata provided by the Connect Secure API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure service being accessible and properly configured.
  • The node uses an OpenAPI specification internally to build its properties and handle requests.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this is correctly set.
  • Empty or malformed query conditions: Invalid query strings may cause the API to reject the request or return no results.
  • Pagination issues: Incorrect use of skip and limit might lead to unexpected empty responses or repeated data.
  • API connectivity problems: Network issues or incorrect credentials will prevent successful data retrieval.
  • Order By field errors: Using unsupported fields in the order_by parameter may cause API errors.

To resolve these, verify all input parameters, confirm API credentials, and check network connectivity.

Links and References

Discussion