Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve specific attack surface results. It is designed to fetch detailed information about a particular attack surface entry by its unique identifier. This functionality is useful in cybersecurity workflows where users need to programmatically access and analyze security-related data tied to user accounts.

Practical examples include:

  • Automatically retrieving the latest attack surface details for a given user ID as part of a security monitoring pipeline.
  • Integrating attack surface data into dashboards or alerting systems to track vulnerabilities or exposures associated with specific users.

Properties

Name Meaning
X USER ID The User Id header value used for authentication or identification in the API request.
Id The numeric identifier of the attack surface result to retrieve.

Output

The node outputs JSON data representing the retrieved attack surface result corresponding to the provided Id. This JSON typically contains detailed information about the attack surface entry, such as metadata, status, and related security insights.

No binary data output is indicated in the source code.

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 defined in the bundled openapi.json file to build properties and operations.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure that the User Id is correctly set and passed as a header; otherwise, the API may reject the request.
  • Invalid or non-existent Id: Providing an incorrect attack surface ID will likely result in an error or empty response.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network issues: Confirm connectivity to the Connect Secure API endpoint.

Common error messages would relate to authorization failures, resource not found, or bad requests due to missing parameters.

Links and References

Discussion