AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Vulnerabilities" resource to retrieve a specific suppressed vulnerability by its ID. It is useful in scenarios where users need to fetch detailed information about a particular vulnerability that has been marked as suppressed, for example, to review or audit suppressed security issues within a system.

Practical examples include:

  • Fetching details of a suppressed vulnerability to verify its status.
  • Integrating with security dashboards to display suppressed vulnerabilities on demand.
  • Automating compliance checks by retrieving suppressed vulnerabilities and processing their data.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking purposes; must be provided as a string header.
Id Numeric identifier of the suppressed vulnerability to retrieve.

Output

The node outputs JSON data representing the retrieved suppressed vulnerability. This JSON typically includes all relevant details about the vulnerability such as its ID, status, description, suppression reason, timestamps, and any other metadata defined by the API schema.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard ConnectSecure service.
  • The base URL for the API is configured via credentials.
  • Uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building and validation.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure the "X USER ID" property is set correctly as it is required for the API call.
  • Invalid or missing Id: The "Id" property must be a valid number corresponding to an existing suppressed vulnerability.
  • Authentication errors: Verify that the API key credential is properly configured and has sufficient permissions.
  • Network or API errors: Check connectivity to the configured base URL and ensure the API endpoint is available.
  • Unexpected response structure: Confirm that the API version matches the OpenAPI spec used by the node.

Links and References

Discussion