Nessus

Overview

This node integrates with the Nessus vulnerability scanner API, allowing users to manage and control scans programmatically within n8n workflows. Specifically, the "Scan" resource's "Resume" operation lets you resume a paused scan by specifying its ID. This is useful in scenarios where a scan was temporarily halted (paused) and needs to be continued without starting over.

Practical examples include:

• Automatically resuming paused vulnerability scans after maintenance windows.
• Integrating scan control into broader security automation workflows.
• Managing scan lifecycle dynamically based on external triggers or conditions.

Properties

Output

The node outputs JSON data representing the response from the Nessus API for the resume scan action. Typically, this includes details about the resumed scan status or confirmation that the scan has been successfully resumed.

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the Nessus API via an API key credential configured in n8n.
• The node depends on the NessusApi helper class to interact with the Nessus REST API.
• Proper permissions on the Nessus server are necessary to resume scans.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent scan ID will cause errors.
  • Attempting to resume a scan that is not currently paused may result in an error or no effect.
  • Network connectivity problems or incorrect API credentials will prevent successful API calls.

• Error messages:

  • Errors thrown by the node typically contain the message from the Nessus API. For example, "Scan not found" or "Invalid scan state".
  • To resolve, verify the scan ID is correct and that the scan is in a paused state before resuming.
  • Ensure the API credentials are valid and have sufficient permissions.

Links and References

• Nessus API Documentation
• n8n Expressions Documentation (for dynamic scan ID input)