Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Update Suppress Vulnerability, is designed to update suppression settings for a specific vulnerability in a system that tracks vulnerabilities. It allows users to modify which internal users are associated with suppressing a particular vulnerability by sending updated data to the API.

Common scenarios where this node would be beneficial include:

  • Automatically updating suppression details when a vulnerability is acknowledged or resolved internally.
  • Integrating with ticketing or incident management systems to reflect changes in vulnerability status.
  • Managing user access or responsibility related to vulnerability suppression in bulk or via automation workflows.

For example, a security team could use this node to update the list of internal users who have suppressed a vulnerability after an investigation, ensuring the system reflects current suppression status.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Data JSON object containing suppression details; typically includes an array of internal users to associate with the vulnerability suppression. Example: { "internal_users": [] }
Id Numeric identifier of the vulnerability to update suppression information for.

Output

The node outputs JSON data representing the response from the API after attempting to update the suppression information for the specified vulnerability. This typically includes confirmation of the update or details about the updated suppression state.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • The node depends on the external Connect Secure API endpoint that manages vulnerability suppression.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this property is set correctly.
  • Invalid JSON in Data property: The data field must be valid JSON; malformed JSON will cause errors.
  • Incorrect vulnerability Id: Providing an invalid or non-existent vulnerability ID may result in not found errors.
  • API authentication failures: Ensure the API key credential is configured and has sufficient permissions.
  • Network or connectivity issues: Verify network access to the Connect Secure API endpoint.

Common error messages might include:

  • Unauthorized or 401 errors indicating missing or invalid authentication.
  • 400 Bad Request errors due to malformed JSON or missing required fields.
  • 404 Not Found if the vulnerability ID does not exist.

Resolving these usually involves verifying input properties, checking API credentials, and confirming the target vulnerability exists.

Links and References

Discussion