Actions222
- Application Baseline Actions
- Attack Surface Actions
- Backup Software Actions
- EDR Actions
- Tags Actions
- PII Actions
- External Scan Actions
- Settings Actions
- Compliance Assessment Actions
- Reports Actions
- Compliance Actions
- Jobs Actions
- Active Directory Actions
- Retrieve Ad Roles
- Retrieve Ad User Licenses
- Retrieve Azure Licenses
- Retrieve Azure Ad Logs
- Retrieve Azure Secure Score
- Retrieve Ad Password Policies
- Retrieve Ad Groups View
- Retrieve Ad Ous View
- Retrieve Ad Gpos View
- Retrieve Ad Computers View
- Retrieve Ad Users View
- Retrieve Ad Domain Details
- Retrieve Ad Gpos Details
- Retrieve Get Ous Details
- Retrieve Get Groups Details
- Retrieve Ad Group Users
- Retrieve Ad Group Computers
- Retrieve Get User Details
- Retrieve Get Computer Details
- Retrieve Ad Roles Details
- Retrieve Ad Roles Member
- Retrieve Ad Basic Info
- Audit Log Actions
- Ad Audit Actions
- Asset Data Actions
- Retrieve Bios Info
- Retrieve Bio Info
- Retrieve Browser Extensions
- Retrieve Browser Extension
- Retrieve Ciphers View
- Retrieve Cipher View
- Retrieve Windows Protection Status
- Retrieve Window Protection Status
- Retrieve Asset Compliance Report Card
- Retrieve Asset Firewall Policy
- Retrieve Asset Installed Drivers
- Retrieve Asset Installed Driver
- Retrieve Asset Interface
- Retrieve Asset Msdt
- Retrieve Asset Ports
- Retrieve Asset Port
- Retrieve Asset Security Report Data
- Retrieve Asset Security Report Datum
- Retrieve Asset Shares
- Retrieve Asset Share
- Retrieve Asset Storages
- Retrieve Asset Storage
- Retrieve Asset Unqouted Services
- Retrieve Asset Unqouted Service
- Retrieve Asset User Shares
- Retrieve Asset User Share
- Retrieve Asset Video Info
- Retrieve Asset Windows Reboot Required
- Retrieve Asset Window Reboot Required
- Vulnerabilities Actions
- Firewall Actions
- Integration Actions
- Retrieve Integration Credentials
- Retrieve Integration Credential
- Create Integration Credential
- Update Integration Credential
- Delete Integration Credential
- Retrieve Integration Rules
- Retrieve Integration Rule
- Create Integration Rule
- Update Integration Rule
- Delete Integration Rule
- Retrieve Company Mappings
- Retrieve Company Mapping
- Create Company Mapping
- Update Company Mapping
- Delete Company Mapping
- Event Set Actions
- Ticket Template Actions
- Scheduler Actions
- Credentials Actions
- Asset Actions
- Retrieve Records
- Retrieve Assets
- Retrieve Asset
- Create Asset
- Update Asset
- Delete Asset
- Retrieve Asset Stats
- Retrieve Asset Stat
- Retrieve Asset View
- Retrieve Cron Jobs
- Retrieve Kernel Modules
- Retrieve Suid Permissions
- Retrieve Ufw Firewall Rules
- Retrieve Selinux Settings
- Retrieve Asset Iptables Rules
- Retrieve Asset Users
- Retrieve Asset Processes Running
- Retrieve Asset Services
- Retrieve Asset Patches Info
- Retrieve Asset Firewall Rules
- Retrieve Asset Registry Misconfiguration
- Retrieve Asset Open Ports
- Retrieve Notification Tickets View
- Retrieve System Events View
- Discovery Settings Actions
- Retrieve Discovery Settings
- Retrieve Discovery Setting
- Create Discovery Setting
- Update Discovery Setting
- Delete Discovery Setting
- Retrieve Agent Discoverysettings Mapping
- Retrieve Agent Discoverysetting Mapping
- Create Agent Discoverysetting Mapping
- Update Agent Discoverysetting Mapping
- Delete Agent Discoverysetting Mapping
- Auth Actions
- Company Actions
- Agent Actions
Overview
This node operation, Retrieve Remediated Vulnerabilities, is designed to fetch a list of vulnerabilities that have been remediated from the Connect Secure API. It allows users to query and retrieve detailed information about vulnerabilities that are no longer active due to remediation efforts.
Common scenarios where this node would be beneficial include:
- Security teams tracking the status of previously identified vulnerabilities to verify remediation.
- Automated reporting systems that generate compliance or security posture reports based on remediated issues.
- Integration with ticketing or incident management systems to update or close vulnerability-related tickets once remediation is confirmed.
Practical example:
- A security analyst wants to pull all remediated vulnerabilities for a specific user within a certain timeframe, ordered by severity, to review the effectiveness of recent patching activities.
Properties
| Name | Meaning |
|---|---|
| X USER ID | User Id header required to identify the user context for the API request. |
| Condition | Query condition string to filter the vulnerabilities (e.g., by date, severity, etc.). |
| Skip | Number of records to skip in the result set (for pagination). |
| Limit | Maximum number of records to return. |
| Order By | Field name(s) to order the results by (e.g., "date", "severity"). |
Output
The node outputs JSON data representing the retrieved remediated vulnerabilities. Each item in the output typically contains details about a single vulnerability, such as its identifier, description, remediation status, timestamps, and other relevant metadata provided by the Connect Secure API.
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 structured JSON data.
Dependencies
- Requires an API key credential for authenticating with the Connect Secure API.
- The node depends on the Connect Secure API being accessible and properly configured.
- No additional external dependencies beyond the bundled OpenAPI client and lodash library are indicated.
Troubleshooting
- Missing or invalid X USER ID: The API requires a valid user ID header; ensure this property is correctly set.
- Invalid query conditions: If the
Conditionparameter is malformed or unsupported by the API, the request may fail or return no results. - Pagination issues: Incorrect use of
SkipandLimitcan lead to unexpected empty results or incomplete data sets. - Order By errors: Specifying invalid fields in
Order Bymay cause the API to reject the request. - Authentication failures: Ensure the API key credential is valid and has sufficient permissions.
- Network or API downtime can also cause failures; verify connectivity and API status.
Links and References
- Connect Secure API documentation (refer to your organization's internal or vendor-provided docs).
- n8n documentation on using HTTP Request nodes and custom API integrations.
- General best practices for querying paginated APIs and handling API authentication.