Your Tenable Core + Tenable Nessus Network Monitor deployment must meet the following requirements.
You must have internet access to download Tenable Core files.
After you transfer a file to your machine, internet access requirements to deploy or update Tenable Core vary depending on your environment.
|Environment||Tenable Core Format||Internet Requirement|
|Virtual Machine||VMware||.ova file||You do not need internet access to deploy or update Tenable Core.|
|Microsoft Hyper-V||.zip file|
|Hardware||.iso image||Requires internet access to install or update Tenable Core.|
Tip: You do not need access to the internet when you install updates to Tenable Core + Tenable Nessus Network Monitor via an offline .iso file. For more information, see Update Tenable Core Offline.
Your Tenable Core deployment requires access to specific ports for inbound and outbound traffic.
Allow inbound traffic to the following ports listed.
Note: Inbound traffic refers to traffic from users configuring Tenable Core, etc.
|TCP 22||Inbound SSH connections.|
Inbound HTTPS communications to the Tenable Core interface.
Inbound HTTPS communications for restoring backups.
Inbound communications with the file upload server.
|TCP 8834||Inbound communications to the Tenable Core + Tenable Nessus interface.|
|TCP 8835||Inbound communications to the Tenable Core + Tenable Nessus Network Monitor interface.|
Allow outbound traffic to the following ports listed.
|TCP 22||Outbound SSH connections, including remote storage connections.|
|TCP 443||Outbound communications to the
|UDP 53||Outbound DNS communications for Tenable Nessus Network Monitor and Tenable Core.|