Nessus icon

Nessus

Interact with the Nessus API

Actions17

Overview

This node integrates with the Nessus vulnerability scanner API to manage and control scans. Specifically, the Scan - Launch operation allows users to start a previously configured scan on specified targets. This is useful in automated security workflows where you want to trigger vulnerability assessments on demand or as part of a larger security orchestration process.

Typical use cases include:

  • Automatically launching scheduled vulnerability scans on network assets.
  • Triggering scans dynamically based on changes in infrastructure.
  • Running scans with alternative target lists without modifying the original scan configuration.

For example, you might have a predefined scan template for your internal network and use this node to launch that scan regularly or after deploying new systems.

Properties

Name Meaning
Scan Name or ID Selects the scan to launch by name or ID from existing scans.
Alternative Targets (Optional) Comma-separated list of alternative IP addresses, ranges, or hostnames to scan instead of the default targets configured in the scan.

Output

The output JSON contains the response from the Nessus API related to the launched scan. This typically includes details such as the scan ID, status, and any metadata returned by the API upon starting the scan.

No binary data is produced by this operation.

Example output structure (simplified):

{
  "id": 123,
  "status": "running",
  "scan_name": "My Scan",
  "start_time": "2024-06-01T12:00:00Z"
}

Dependencies

  • Requires an active connection to a Nessus server with appropriate API credentials (an API key or token).
  • The node depends on the Nessus API being accessible and the user having permissions to launch scans.
  • The node uses internal methods to fetch available scans for selection.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Specifying a scan ID that does not exist or is inaccessible will result in errors.
    • Providing malformed alternative targets (e.g., invalid IP format) may cause the launch to fail.
    • Network connectivity issues between n8n and the Nessus server can prevent operations.

  • Error messages:

    • "Failed to load scans: <message>" indicates problems retrieving scan options; check API access and permissions.
    • Errors during launch often include messages about invalid scan IDs or targets; verify inputs carefully.
    • If the node throws an error mentioning item index, it relates to which input item caused the failure.

  • Resolution tips:

    • Ensure the API credentials are valid and have sufficient privileges.
    • Confirm the scan exists and is in a state that allows launching.
    • Validate the format of alternative targets if used.
    • Check network connectivity and firewall rules.

Links and References

Discussion