AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to update suppression information for vulnerabilities via a PATCH request. It allows users to modify specific vulnerability records by sending updated data fields, such as internal user lists or an identifier, to the target API. This operation is useful in scenarios where security teams need to suppress or adjust vulnerability details dynamically based on evolving threat assessments or remediation progress.

Practical examples include:

  • Suppressing a known false positive vulnerability by updating its suppression status.
  • Adding or modifying metadata related to internal users responsible for handling the vulnerability.
  • Adjusting vulnerability records programmatically as part of automated security workflows.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Additional Body Fields Optional additional fields to include in the request body:
- Data JSON string representing data such as internal users (default example: {"internal_users": "[]"}).
- Id Numeric identifier of the vulnerability record to update.

Output

The node outputs JSON data representing the response from the PATCH update request to the vulnerability suppression endpoint. The structure typically includes confirmation of the update, possibly the updated vulnerability record, or status messages from the API.

If the API supports binary data responses, this node would handle them accordingly, but based on the provided code and properties, the output is primarily JSON.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard ConnectSecure service.
  • Needs the base URL of the API configured in the credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building request properties and handling OpenAPI specifications.

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 the correct user ID is supplied.
  • Invalid JSON in Data field: The Data property expects a valid JSON string. Malformed JSON will cause parsing errors before sending the request.
  • Incorrect Id value: Providing an invalid or non-existent vulnerability ID may result in not found errors or failed updates.
  • API connectivity issues: Verify that the base URL and API credentials are correctly set up and that the API service is reachable.
  • Permission errors: Ensure the API key used has sufficient permissions to perform PATCH updates on vulnerabilities.

Links and References

Discussion