Nessus

Overview

This node integrates with the Nessus API to manage security policies, scans, folders, plugins, and sessions. Specifically, for the Policy - Delete operation, it allows users to delete an existing policy from their Nessus environment by specifying the policy's name or ID.

Common scenarios where this node is beneficial include automating vulnerability management workflows, cleaning up outdated or unused policies, and integrating Nessus policy management into broader security orchestration processes.

For example, a security team might use this node in an automated workflow to remove deprecated policies after migrating to new scanning standards, ensuring that only relevant policies remain active.

Properties

Output

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

The output structure is:

{
  "json": {
    // API response data confirming deletion or error information
  }
}

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 endpoints.
• Proper permissions are needed on the Nessus side to delete policies.

Troubleshooting

• Common issues:

  • Attempting to delete a policy that does not exist or has already been deleted.
  • Insufficient permissions or invalid API credentials causing authorization failures.
  • Network connectivity problems preventing communication with the Nessus server.

• Error messages and resolutions:

  • "Failed to load policies": Indicates inability to retrieve the list of policies, possibly due to authentication or network issues. Verify API credentials and network access.
  • Errors returned from the API during deletion (e.g., "Policy not found" or "Access denied") should be checked against the Nessus user permissions and the correctness of the provided policy ID.
  • If the node throws a NodeOperationError, ensure that the input policy ID is valid and that the node is configured correctly.

Links and References

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