Nessus

Overview

This node integrates with the Nessus vulnerability scanner API, allowing users to manage and interact with scans programmatically within n8n workflows. Specifically, the Scan - Delete operation enables users to delete an existing scan by specifying its name or ID. This is useful for automating cleanup of outdated or unnecessary scans, managing scan lifecycle, or integrating scan management into broader security automation pipelines.

Practical examples include:

• Automatically deleting scans after their results have been exported and processed.
• Cleaning up scans that are no longer relevant based on certain workflow conditions.
• Integrating scan deletion as part of a scheduled maintenance routine.

Properties

The property "Scan Name or ID" uses a dynamic dropdown populated by available scans fetched from the Nessus API, showing scan names along with their status and creation date for easier identification.

Output

The output of this operation is a JSON object representing the response from the Nessus API after attempting to delete the specified scan. Typically, this will confirm successful deletion or provide error details if the operation failed.

The structure is:

{
  // API response data confirming deletion or error information
}

No binary data is produced by this operation.

Dependencies

• Requires an active connection to the Nessus API using an API key credential configured in n8n.
• The node depends on the NessusApi helper class internally to communicate with the Nessus service.
• Proper permissions on the Nessus server to delete scans are necessary.

Troubleshooting

• Common issues:

  • Specifying an invalid or non-existent scan ID/name will cause the operation to fail.
  • Insufficient permissions on the Nessus account may prevent deletion.
  • Network connectivity issues between n8n and the Nessus server can cause timeouts or errors.

• Error messages:

  • Errors returned from the Nessus API will be passed through, often indicating reasons such as "Scan not found" or "Permission denied".
  • If the node fails to load scans for the dropdown, it will throw an error like "Failed to load scans" which indicates connectivity or authentication problems.

• Resolution tips:

  • Verify the scan ID or name is correct and exists.
  • Ensure the API key used has delete permissions.
  • Check network connectivity and Nessus server availability.
  • Use expressions carefully when specifying scan IDs to avoid syntax errors.

Links and References

• Nessus API Documentation
• n8n Expressions Documentation
• Nessus Official Site