Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Suppress Vulnerability, is designed to fetch suppressed vulnerability records from a Connect Secure API. It allows users to query and retrieve specific vulnerability suppression data based on various filtering and pagination parameters. This can be useful in security workflows where you want to analyze or report on vulnerabilities that have been marked as suppressed, helping teams focus on active issues or audit suppression history.

Practical examples:

  • Retrieve a list of suppressed vulnerabilities filtered by certain conditions (e.g., severity, date).
  • Paginate through large sets of suppressed vulnerabilities using skip and limit.
  • Order the results by specific fields to prioritize review or reporting.

Properties

Name Meaning
X USER ID User Id header required for authentication or identification in the API request.
Condition Query condition string to filter suppressed vulnerabilities (e.g., status, type).
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return in the response.
Order By Field name(s) to order the returned suppressed vulnerabilities by (e.g., date, severity).

Output

The node outputs JSON data representing the retrieved suppressed vulnerabilities. The structure typically includes an array of vulnerability suppression records matching the query parameters. Each record contains details about the suppressed vulnerability such as identifiers, suppression reasons, timestamps, and related metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API endpoint that supports retrieving suppressed vulnerabilities.
  • Proper configuration of the API credentials within n8n is necessary for successful requests.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure it is provided and correct.
  • Invalid query parameters: Incorrect values for condition, skip, limit, or order_by may cause errors or empty responses.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Pagination issues: Setting skip or limit incorrectly might result in no data or repeated data; adjust accordingly.
  • Network or connectivity problems: Ensure n8n can reach the Connect Secure API endpoint without firewall or proxy issues.

Links and References

Discussion