AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Vulnerabilities" resource of an external service, specifically performing the "Get Retrieve Suppress Vulnerability" operation. It is designed to retrieve vulnerability data based on user-supplied criteria and optional query parameters. This node is useful in scenarios where you need to fetch detailed vulnerability information for security analysis, compliance reporting, or integration into broader IT asset management workflows.

For example, a security analyst could use this node to pull a filtered list of vulnerabilities matching certain conditions, limit the number of results returned, skip a set number of records for pagination, or order the results by specific fields.

Properties

Name Meaning
X USER ID User Id required for authentication or identification in the request header.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition string.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data representing the retrieved vulnerabilities. The structure of the JSON output corresponds to the response from the external API's vulnerability retrieval endpoint. It typically includes details about each vulnerability such as identifiers, descriptions, severity, status, and other relevant metadata.

If the API supports binary data related to vulnerabilities (e.g., attachments or reports), the node would handle it accordingly, but based on the provided code and properties, the primary output is JSON-formatted vulnerability data.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external service.
  • The base URL for the API must be set in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building and execution.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure this property is correctly set.
  • Invalid query parameters: Providing malformed or unsupported values in additional query parameters like condition, skip, limit, or order_by may result in API errors or empty responses. Validate these inputs carefully.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful requests. Verify the API endpoint and network accessibility.
  • Credential errors: If the API key or authentication token is missing or expired, the node will fail to authenticate. Refresh or reconfigure credentials as needed.

Links and References

Discussion