Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Vulnerabilities" resource of the Connect Secure API, specifically to retrieve details about a suppressed vulnerability. It is useful in scenarios where users need to fetch information about vulnerabilities that have been marked as suppressed, for example, to review or audit suppressed security issues within an environment.

A practical example would be a security analyst automating the retrieval of suppressed vulnerability details by specifying the user ID and the vulnerability ID, enabling integration into broader security workflows or dashboards.

Properties

Name Meaning
X USER ID The User Id header value to authenticate or identify the user making the request.
Id The numeric identifier of the suppressed vulnerability to retrieve details for.

Output

The node outputs JSON data representing the details of the specified suppressed vulnerability. This typically includes all relevant fields returned by the Connect Secure API for that vulnerability, such as its status, description, suppression metadata, and any other associated information.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and the user having appropriate permissions to retrieve suppressed vulnerability data.
  • The node uses an OpenAPI specification internally to define operations and properties.

Troubleshooting

  • Missing or invalid X USER ID: If the "X USER ID" header is not provided or incorrect, the API may reject the request. Ensure this property is set correctly.
  • Invalid or non-existent vulnerability Id: Providing an incorrect Id will result in errors or empty responses. Verify the Id corresponds to a valid suppressed vulnerability.
  • Authentication errors: Make sure the API key credential is configured properly and has sufficient permissions.
  • Network or API availability issues: Check connectivity to the Connect Secure API endpoint.

Common error messages might include unauthorized access, resource not found, or bad request due to missing parameters. Resolving these involves verifying credentials, input values, and network conditions.

Links and References

  • Connect Secure API documentation (refer to official vendor resources)
  • n8n documentation on creating and using API credentials
  • OpenAPI Specification used internally by the node (not publicly linked here)

Discussion