Tenable Appliance-Tenable Core Migration Guide · 2020-05-18 · Tenable Appliance to Tenable Core...

Tenable Appliance to Tenable Core

Migration Guide

Last Updated: July 02, 2020

Table of Contents

Tenable Appliance to Tenable Core Migration Overview 4

Get Started 5

Version Requirements 7

Considerat ions for Large Deployments 8

Plan Your Tenable.sc Appliance Migrat ion 9

Plan Your Nessus Appliance Migrat ion 10

Plan Your NNM Appliance Migrat ion 12

Perform a Migration 14

Perform a Backup and Restore Migrat ion 15

Perform an Rsync Migrat ion 18

Prepare the Private Key Before an Rsync Migrat ion 23

Downgrade Before an Rsync Migrat ion 24

Deploy a New Instance 26

Post-Migration Actions 27

Appliance Quick Reference 29

Appliance Interface 30

Back Up Appliance 31

Expand Virtual Disk - Hyper-V 33

Expand Virtual Disk - VMware 34

Restore from File 35

Updates 36

Appliance Migrat ion - 3.x to 4.x 38

Copyright © 2020 Tenable, Inc. All rights reserved. Tenable, Tenable.io, Tenable Network Security, Nessus, SecurityCenter, SecurityCenter Cont inuous View and Log Correlat ion Engine are registered trade-

marks of Tenable,Inc. Tenable.sc, Tenable.ot, Lumin, Indegy, Assure, and The Cyber Exposure Company are trademarks of Tenable, Inc. All other products or services are trademarks of their respect ive

Virtual Image Migrat ion 40



Tenable Appliance to Tenable Core Migration Overview

Note: The Tenable Appliance is an end-of- life product. For more information, see the bulletin. Tenablerecommends migrating your Tenable Appliance deployments to Tenable Core.

Tip: If you encounter issues with the migration, contact Tenable Support.

The Tenable Appliance to Tenable Core migration process varies depending on your current Tenable

Appliance deployment and your desired Tenable Core deployment.

You must migrate instances of Tenable Appliance individually to Tenable Core. Tenable does not sup-

port a bulk migration for multiple instances.

Application Migration Order

If you have multiple Tenable Appliance instances supporting different applications, Tenable recom-

mends migrating in the following order:

1. All Tenable Appliance + Tenable.sc instances

2. All Tenable Appliance + Nessus instances

3. All Tenable Appliance + Nessus Network Monitor instances

To plan your migration order and methods and get started with the migration, see Get Started.



https://community.tenable.com/s/feed/0D53a00006SLlukCAD

Get Started

Use the following getting started sequence to migrate your entire Tenable Appliance deployment.

Tip: If you encounter issues with the migration, contact Tenable Support.

To get started with your Tenable Appliance to Tenable Core migration:

1. If your deployment includes multiple instances of Tenable Appliance, plan your migration

sequence.

l You must migrate instances of Tenable Appliance individually to Tenable Core. Tenable

does not support a bulk migration for multiple instances.

l If you have multiple Tenable Appliance instances supporting different applications, Ten-

able recommends migrating in the following order:




Note: You cannot change applications during the migration process. For example, you canonly migrate Nessus on Tenable Appliance to an instance of Tenable Core + Nessus. If youneed to change applications, contact Tenable Support.

If you need to change versions, see Version Requirements.

For more information about migrating multiple instances of Tenable Appliance, see Con-

siderat ions for Large Deployments.

2. Choose the migration method you plan to use for each individual instance of Tenable Appliance:

l Plan Your Tenable.sc Appliance Migrat ion

l Plan Your Nessus Appliance Migrat ion

l Plan Your NNM Appliance Migrat ion

3. If your deployment includes one or more instances of Tenable Appliance + Tenable.sc, migrate

all of your Tenable.sc instances individually:



a. Migrate via the appropriate method: rsync or backup and restore.

b. Perform all necessary post-migrat ion act ion items.

4. If your deployment includes one or more instances of Tenable Appliance + Nessus, migrate all of

your Nessus instances individually:

a. Migrate via the appropriate method: backup and restore or deploying new instances.


5. If your deployment includes one or more instances of Tenable Appliance + NNM, migrate all of

your NNM instances individually:

a. Migrate via the appropriate method: backup and restore or deploying new instances.




Version Requirements

The minimum Tenable Appliance application version supported for migration depends on the method

you use to migrate and your application.

Migration Method Minimum Application Version to Migrate

Backup and restore l Nessus 6.11.1 or later

l Tenable.sc 5.5.1 or later

l Nessus Network Monitor 5.4.0 or laterRemote synchronization

Deploy a new instance No minimum application version requirements.

Note: You cannot change applications during the migration process. For example, you can only migrateNessus on Tenable Appliance to an instance of Tenable Core + Nessus.

The backup and restore and remote synchronization methods include steps to downgrade Tenable

Core to your Tenable Appliance application version in order to complete the migration. For more

information, see Perform a Backup and Restore Migrat ion and Perform an Rsync Migrat ion.

After you migrate to Tenable Core, you can upgrade Tenable Core to other application versions.



Considerations for Large Deployments



Since the migration is performed one instance at a time:

l You can migrate application instances running different versions of the same application.

l You can manage your unmigrated Tenable Appliance instances normally while you begin migrat-

ing other instances.

Application Migration Order






For more information, see Get Started.



Plan Your Tenable.sc Appliance Migration



Tenable recommends different methods depending on the size of your Tenable.sc deployment. To

determine the disk space used on your Tenable Appliance, see the status section described in Appli-

ance Interface.

To confirm you meet the application version requirements, see Version Requirements.

l Tenable.sc Using 250 GB Disk Space or More

l Tenable.sc Using Less Than 250 GB Disk Space

Tenable.sc Using 250 GB Disk Space or More

Large Tenable Appliance + Tenable.sc instances can migrate to Tenable Core via the remote syn-

chronization method. For more information, see Perform an Rsync Migrat ion.

Note: If you change the Tenable.sc hostname during the migration, Tenable must re- issue a Tenable.sclicense.

Tenable.sc Using Less Than 250 GB Disk Space

Small Tenable Appliance + Tenable.sc can migrate to Tenable Core via the backup and restore method.

For more information, see Perform a Backup and Restore Migrat ion.

Note: If you change the Tenable.sc hostname during the migration, Tenable must re- issue a Tenable.sclicense.



Plan Your Nessus Appliance Migration


Appliance deployment and your desired Tenable Core deployment. To confirm you meet the applic-

ation version requirements, see Version Requirements.

l Plan Nessus Professional

l Plan Nessus Manager

l Plan Nessus Scanner Managed by Tenable.sc

l Plan Nessus Scanner Managed by Tenable.io

Plan Nessus Professional

Tenable Appliance + Nessus Professional instances can migrate to Tenable Core via the backup and

restore method. For more information, see Perform a Backup and Restore Migrat ion.

Plan Nessus Manager

Tenable Appliance + Nessus Manager instances can migrate to Tenable Core via the backup and


Note: Tenable recommends retaining the same IP address before and after your migration. If you usethe same IP address for your Appliance and for Tenable Core, Tenable.sc stays connected to theinstance.

If you change the IP address, you must reconfigure the scanner in Tenable.sc. For more information, seeNessus Scanners in the Tenable.sc User Guide .

Plan Nessus Scanner Managed by Tenable.sc

Most Tenable Appliance + Nessus instances managed by Tenable.sc can be migrated by deploying new

instances of Tenable Core. For more information, see Deploy a New Instance.

If you want to preserve an advanced configuration (for example, customized nessusd.rules files or

local scan results), you may prefer to migrate via the backup and restore method. For more inform-

ation, see Perform a Backup and Restore Migrat ion.

Note: Tenable recommends retaining the same IP address before and after your migration. If you use



https://docs.tenable.com/tenablesc/5_12/Content/NessusScanners.htm

the same IP address for your Appliance and for Tenable Core, Tenable.sc stays connected to theinstance.

If you change the IP address, you must reconfigure the scanner in Tenable.sc. For more information, seeNessus Scanners in the Tenable.sc User Guide .

Plan Nessus Scanner Managed by Tenable.io

Tenable Appliance + Nessus instances managed by Tenable.io can be migrated by the backup and

restore method or by deploying new instances of Tenable Core, depending on the needs of your organ-

ization.

l If you do not know the appliance's Tenable.io scanner group or your Tenable.io linking key, you

must migrate via the backup and restore method.

If you want to preserve an advanced configuration (for example, customized nessusd.rulesfiles or local scan results), you may choose to migrate via the backup and restore method.

For more information, see Perform a Backup and Restore Migrat ion.

l If you know the appliance's Tenable.io scanner group and your Tenable.io linking key, you may

prefer to deploy new instances of Tenable Core instead of migrating. For more information, see

Deploy a New Instance.



https://docs.tenable.com/tenablesc/5_12/Content/NessusScanners.htm

Plan Your NNM Appliance Migration


Appliance deployment and your desired Tenable Core deployment. To confirm you meet the applic-

ation version requirements, see Version Requirements.

l NNM Standalone Instance

l NNM Instance Linked to Industrial Security

l NNM Instance Linked to Tenable.sc

l NNM Instance Linked to Tenable.io

NNM Standalone Instance

Tenable Appliance + NNM standalone instances can migrate to Tenable Core via the backup and


NNM Instance Linked to Industrial Security

Tenable Appliance + NNM instances linked to Industrial Security can migrate to Tenable Core via the

backup and restore method. For more information, see Perform a Backup and Restore Migrat ion.

NNM Instance Linked to Tenable.sc

Tenable Appliance + NNM instances managed by Tenable.sc can be migrated by the backup and

restore method or by deploying new instances of Tenable Core, depending on the needs of your organ-

ization.

l If your highest priority is to retain your NNM instance configurations, you must migrate via the

backup and restore method. For more information, see Perform a Backup and Restore Migra-

t ion.

l If you prefer a faster migration and you are willing to reconfigure your NNM instance con-

figurations after migration, you may prefer to deploy new instances of Tenable Core instead of

migrating. For more information, see Deploy a New Instance.

Note: Tenable recommends retaining the same IP address before and after your migration. If youuse the same IP address for your appliance and for Tenable Core, Tenable.sc stays connected to



the instance.

If you change the IP address, you must reconfigure the NNM in Tenable.sc.

NNM Instance Linked to Tenable.io

Tenable Appliance + NNM instances managed by Tenable.io can be migrated by the backup and restore

method or by deploying new instances of Tenable Core, depending on the needs of your organization.

l If you do not know the appliance's Tenable.io scanner group or your Tenable.io linking key, you

must migrate via the backup and restore method. For more information, see Perform a Backup

and Restore Migrat ion.

l If you know the appliance's Tenable.io scanner group and your Tenable.io linking key, you may

prefer to deploy new instances of Tenable Core instead of migrating. For more information, see

Deploy a New Instance.



Perform a Migration



l Perform a Backup and Restore Migrat ion

l Perform an Rsync Migrat ion

l Deploy a New Instance








To plan your overall migration strategy and decide which methods suit your individual instances, see

Get Started.



Perform a Backup and Restore Migration

Required Tenable Core User Role: Administrator with reuse my password for privileged tasks selec-ted during login


Appliance deployment and your desired Tenable Core deployment. To plan your overall migration

strategy and confirm the backup and restore method suits your Tenable Appliance instance, see Get

Started.

Before you begin:

l Confirm your environment meets the requirements to handle backup and restore.

Tip: To determine the disk space used on your Tenable Appliance, see the status sectiondescribed in Appliance Interface.

To determine your available disk space on Tenable Core, see Manage System Storage in TenableCore + Nessus, Manage System Storage in Tenable Core + Tenable.sc, or Manage System Stor-age in Tenable Core + NNM in the Tenable Core User Guide.

Tip: To increase your available disk space on Tenable Core, see Add or Expand Disk Space inTenable Core + Nessus, Add or Expand Disk Space in Tenable Core + Tenable.sc, or Add orExpand Disk Space in Tenable Core + NNM in the Tenable Core User Guide.

l Confirm your current Tenable Appliance application disk space usage does not use more

than 50% of the total disk space on Tenable Appliance.

l Confirm that your Tenable Core instance has free disk space on the volume containing

/opt that is at least the size of your current Tenable Appliance application disk space

usage.

l Confirm your Tenable Appliance meets the version requirements, as described in Version

Requirements.

l If your migration includes a Tenable.sc deployment, enable touch debugging for DB Locks:

l Tenable.sc version 5.10.x or later —See Enable Touch Debugging in the Tenable.sc User

Guide.

l Tenable.sc version 5.9.x or earlier —Contact Tenable Support.



https://docs.tenable.com/tenablecore/Nessus/Content/TenableCore/Storage.htm

https://docs.tenable.com/tenablecore/Nessus/Content/TenableCore/Storage.htm

https://docs.tenable.com/tenablecore/SecurityCenter/Content/TenableCore/Storage.htm

https://docs.tenable.com/tenablecore/NNM/Content/TenableCore/Storage.htm

https://docs.tenable.com/tenablecore/NNM/Content/TenableCore/Storage.htm

https://docs.tenable.com/tenablecore/Nessus/Content/TenableCore/AddExpandDiskSpace.htm

https://docs.tenable.com/tenablecore/Nessus/Content/TenableCore/AddExpandDiskSpace.htm

https://docs.tenable.com/tenablecore/SecurityCenter/Content/TenableCore/AddExpandDiskSpace.htm

https://docs.tenable.com/tenablecore/NNM/Content/TenableCore/AddExpandDiskSpace.htm

https://docs.tenable.com/tenablecore/NNM/Content/TenableCore/AddExpandDiskSpace.htm

https://docs.tenable.com/tenablesc/Content/EnableTouchDebugging.htm

If you encounter issues with the migration, Tenable Support may ask you to share this file for

troubleshooting.

l If you are migrating in an air-gapped environment, on the Tenable downloads page, download

the application RPM for your current Tenable Appliance application version.

To migrate to Tenable Core via the backup and restore method:

1. Log in to your Tenable Appliance.

2. In Tenable Appliance, perform a backup as described in Back Up Appliance.

Note: You cannot use Whole Appliance for this backup. You must back up all applications indi-vidually.

3. In Tenable Core, deploy and get started.

Caution: You must migrate your Tenable Appliance application data to a new Tenable Coreinstance. Tenable does not recommend migrating to an existing Tenable Core instance; the migra-tion overwrites all existing application data.

l To configure Tenable Core + Nessus, see Get Started with Tenable Core + Nessus.

l To configure Tenable Core + Nessus Network Monitor, see Get Started with Tenable

Core + NNM.

l To configure Tenable Core + Tenable.sc, see Get Started with Tenable Core + Ten-

able.sc.

4. In Tenable Core, restore your Tenable Appliance backup file.

l To restore your Nessus application, see Restore a Nessus Backup.

l To restore your Nessus Network Monitor application, see Restore a NNM Backup.

l To restore your Tenable.sc application, see Restore a Tenable.sc Backup.

The system restores your Tenable Appliance backup to Tenable Core.

5. If prompted, confirm that you want to upgrade or downgrade your Tenable Core application ver-

sion to match your Tenable Appliance application version. For more information, see Version

Requirements.



https://www.tenable.com/downloads

https://docs.tenable.com/tenablecore/Nessus/Content/TenableCore/GetStartedTenableCore.htm

https://docs.tenable.com/tenablecore/NNM/Content/TenableCore/GetStartedTenableCore.htm


https://docs.tenable.com/tenablecore/SecurityCenter/Content/TenableCore/GetStartedTenableCore.htm


https://docs.tenable.com/tenablecore/Nessus/Content/TenableCore/Backup_Restore.htm

https://docs.tenable.com/tenablecore/NNM/Content/TenableCore/Backup_Restore.htm

https://docs.tenable.com/tenablecore/SecurityCenter/Content/TenableCore/Backup_Restore.htm

a. Click Install Correct Version.

A confirmation window appears.

b. Click Replace.

Tenable Core installs the correct version of your application.

The restore window appears.

c. Click Restore.

The system restores your Tenable Appliance backup to Tenable Core.

6. Review your application data.

Note: You may need to update your license. If you see Error: Invalid/ Expired Activation Code,reupload your application license to Tenable Core.

What to do next:

l Perform the post-migration actions for your deployment type, as described in Post-Migrat ion

Act ions.



Perform an Rsync Migration

Video: Migrate to Tenable Core Using Remote Sync

Required Tenable Core User Role: Administrator with reuse my password for privileged tasksenabled



strategy and confirm the remote synchronization (rsync) method suits your Tenable Appliance

instance, see Get Started.

Note: This process is only for migrating Tenable.sc data on Tenable Appliance to Tenable Core+ Tenable.sc.

Before you begin:

l Confirm that your Tenable Core instance has free disk space on the volume containing /opt that

is at least the size of your current Tenable Appliance application disk space usage.

Tip: To determine the disk space used on your Tenable Appliance, see the status sectiondescribed in Appliance Interface.

To determine your available disk space on Tenable Core, see Manage System Storage in the Ten-able Core User Guide. To increase your available disk space on Tenable Core, see Add or ExpandDisk Space in the Tenable Core User Guide.

l Confirm that your Tenable Appliance instance and Tenable Core instance can communicate via

SSH over port 22.

l Confirm your Tenable Appliance meets the version requirements, as described in Version

Requirements.

l Deploy and get started as described in Get Started in the Tenable Core User Guide.

l Prepare your Tenable Appliance tns user's private key for use during the migration, as

described in Prepare the Private Key Before an Rsync Migrat ion.

l If you are migrating in an offline (air-gapped) environment, manually download the RPM for the

version of the application being migrated from the Tenable downloads page. If you cannot find



https://youtu.be/181b-ep6v8U

https://docs.tenable.com/tenablecore/SecurityCenter/Content/TenableCore/Storage.htm





the version you need, contact Tenable Support.

l If your Tenable.sc version on Tenable Core is later than your version on Tenable Appliance,

downgrade as described in Downgrade Before an Rsync Migrat ion.

l Enable touch debugging for DB Locks:

l Tenable.sc version 5.10.x or later —See Enable Touch Debugging in the Tenable.sc User

Guide.

l Tenable.sc version 5.9.x or earlier —Contact Tenable Support.

If you encounter issues with the migration, Tenable Support may ask you to share this file for

troubleshooting.

To migrate to Tenable Core via the rsync method:

1. In Tenable Core, log in to the shell via SSH, the Terminal page, or the system console.

Tip: If you run the migration via the Terminal page, you cannot enable progress output later inthe migration.

2. Run the following command to stop Tenable.sc.

pkexec systemctl stop SecurityCenter

3. Run the following command to stop all running Tenable.sc processes.

pkexec pkill -9 -u tns

4. Run the following command to remove any existing Tenable.sc data.

pkexec sh -c 'rm -rf /opt/sc/* /opt/sc/.*'

5. Run the following command:

pkexec rsync -e "ssh -x -T -i <SSH key path> " -a --hard-links --human-readable --acls --sparse --exclude /support/logs/*tns@<appliance IP address>:/opt/sc/ /opt/sc/



https://docs.tenable.com/tenablesc/Content/EnableTouchDebugging.htm

Tip: If you are running rsync via the via the Terminal page, do not enable progress output. If youare running rsync via SSH or the system console, you can enable progress output by adding oneof the following to the command:

--info=progress2

or

--progress

The synchronization begins.

Tip: If the synchronization fails or is disrupted, run the command again to resume the syn-chronization.

The synchronization finishes.

6. Connect to the Tenable Appliance interface.

7. In the menu, click SecurityCenter.

The SecurityCenter page appears.

8. Click Stop SecurityCenter.

Tenable.sc stops.

9. In Tenable Appliance, log in to the shell via SSH.

10. Run the following command to confirm your SSH and shell are only jobs listed.

ps U tns

11. In Tenable Core, log back into the shell via SSH, the Terminal page, or the system console.

12. Run the following synchronization command again to synchronize files changed since you star-

ted the migration:

pkexec rsync -e "ssh -x -T -i <SSH key path> " -a --hard-links --human-readable --acls --sparse --exclude /support/logs/*tns@<appliance IP address>:/opt/sc/ /opt/sc/



Tip: If you are running rsync via the via the Terminal page, do not enable progress output. If youare running rsync via SSH or the system console, you can enable progress output by adding oneof the following to the command:

--info=progress2

or

--progress

The synchronization begins.

Tip: If the synchronization fails or is disrupted, run the command again to resume the syn-chronization.

The synchronization finishes.

13. Run one of the following commands to reinstall your current version of Tenable.sc:

Online installation:

pkexec yum reinstall SecurityCenter

Offline installation:

pkexec yum reinstall /<RPM path>

14. Run the following command to restore SELinux context on Tenable Core:

pkexec restorecon -RF /opt/sc

Your SELinux context is restored.

15. Log in to the Tenable Core UI.

16. Click Tenable.sc.

17. In Tenable.sc Installation Info, click Start.

The system starts the Tenable.sc service.

What to do next:



l Perform the post-migration actions for your deployment type, as described in Post-Migrat ion

Act ions.

l Upgrade Tenable.sc to the latest version, as described in Upgrade in the Tenable.sc User Guide.



https://docs.tenable.com/tenablesc/Content/Upgrade.htm

Prepare the Private Key Before an Rsync Migration

You must prepare the Tenable Appliance tns user's private key before using it during rsync migra-

tions.

Before you begin:

l Enable SSH access for your Tenable Appliance tns user, as described in the knowledge base art-

icle.

Note: Tenable recommends generating RSA keys 2048 bits or greater.

To prepare your tns user's private key for use during the migration:

1. Confirm your private key is in OpenSSH .key format.

2. Confirm the .key file begins with Begin RSA Private Key.

3. Copy the the .key file to a directory on Tenable Core.

4. Run the following command to change the permissions of the .key file:

chmod 400 <private_key>.key

Tenable Core updates the file permissions.

What to do next:

l Perform your rsync migration, as described in Perform an Rsync Migrat ion.



https://community.tenable.com/s/article/Enable-SSH-access-for-SecurityCenter-on-a-Tenable-Virtual-Appliance

Downgrade Before an Rsync Migration


If your Tenable.sc version on Tenable Core is later than your version on Tenable Appliance, you must

downgrade Tenable Core to your Tenable Appliance application version before performing an rsync

migration.

The downgrade process is different for online and offline Tenable Core migration environments.

Before you begin:

l If you are migrating in an offline (air-gapped) environment, manually download the RPM for the

version of the application being migrated from the Tenable downloads page. If you cannot find

the version you need, contact Tenable Support.

To perform a downgrade in an online migration environment:

1. In Tenable Core, log in to the shell via the Terminal page or the console.

2. Run the following command to begin the downgrade:

pkexec /usr/libexec/tenablecore/backup/applicationDowngrade.sh Secur-ityCenter

A version prompt appears.

3. Press the number next to your Tenable Appliance application version.

4. Press Enter.

A confirmation prompt appears.

5. Press y to confirm the downgrade details.

The downgrade begins. When the downgrade finishes, the system displays a Complete! mes-

sage.

To perform a downgrade in an offline migration environment:




1. In Tenable Core, log in to the shell via the Terminal page or the console.

2. Run the following command to begin the downgrade:

pkexec /usr/libexec/tenablecore/backup/applicationDowngrade.sh -r<path to the .rpm file you downloaded>

The downgrade begins. When the downgrade finishes, the system displays a Complete! mes-

sage.

What to do next:

l Perform your rsync migration, as described in Perform an Rsync Migrat ion.



Deploy a New Instance




strategy and confirm that deploying a new instance of Tenable Core suits your Tenable Appliance

instance, see Get Started.

To deploy a new instance of Tenable Core:

1. In Tenable Core, deploy and get started.

l To configure Tenable Core + Nessus, see Get Started with Tenable Core + Nessus.

l To configure Tenable Core + Nessus Network Monitor, see Get Started with Tenable

Core + NNM.

l To configure Tenable Core + Tenable.sc, see Get Started with Tenable Core + Ten-

able.sc.

What to do next:

l Reconfigure custom configurations from Tenable Appliance in Tenable Core.



https://docs.tenable.com/tenablecore/Nessus/Content/TenableCore/GetStartedTenableCore.htm





Post-Migration Actions

After you perform the migration to Tenable Core, perform the post-migration action items for all new

instances of Tenable Core:

l Instances of Tenable.sc

l Instances of Nessus Professional

l Instances of Nessus Manager

l Instances of Nessus Managed by Tenable.sc

l Instances of Nessus Managed by Tenable.io

l Instances of NNM

Instances of Tenable.sc

l If you changed the Tenable.sc hostname during the migration, contact your Tenable rep-

resentative and ask them to re-issue your Tenable.sc license.

l To continue learning about Tenable Core, see the Tenable Core + Tenable.sc User Guide.

Instances of Nessus Professional

l Reset your Nessus activation code. For more information, see Reset Act ivat ion Code in the Nes-

sus User Guide.

l To continue learning about Tenable Core, see the Tenable Core + Nessus User Guide.

Instances of Nessus Manager

l Reset your Nessus activation code. For more information, see Reset Act ivat ion Code in the Nes-

sus User Guide.

l If you changed the Nessus Manager IP address during migration, you must reconfigure Nessus

Manager in Tenable.sc. For more information, see Nessus Scanners in the Tenable.sc User

Guide.




https://docs.tenable.com/tenablecore/SecurityCenter/Content/TenableCore/Introduction_SC.htm

https://docs.tenable.com/nessus/Content/ResetActivationCode.htm

https://docs.tenable.com/tenablecore/Nessus/Content/TenableCore/Introduction_Nessus.htm

https://docs.tenable.com/nessus/Content/ResetActivationCode.htm

https://docs.tenable.com/tenablesc/Content/NessusScanners.htm


Instances of Nessus Managed by Tenable.sc

l If you changed the Nessus IP address during migration, you must reconfigure Nessus in Ten-

able.sc. For more information, see Nessus Scanners in the Tenable.sc User Guide.

l If you deployed a new instance of Tenable Core, reconfigure any advanced configurations (for

example, customized nessusd.rules files or local scan results) in Tenable Core.


Instances of Nessus Managed by Tenable.io

l If you deployed a new instance of Tenable Core, reconfigure any advanced configurations (for

example, customized nessusd.rules files or local scan results) in Tenable Core.


Instances of NNM

l Update your Monitored Network Interfaces in NNM to reflect your updated NICs. For more

information, see NNM Sett ings in the Nessus Network Monitor User Guide.

l If your NNM instance is linked to Tenable.sc, and you changed the NNM IP address during migra-

tion, you must reconfigure NNM in Tenable.sc. For more information, see NNM Instance Set-

t ings in the Tenable.sc User Guide.

l To continue learning about Tenable Core, see the Tenable Core + NNM User Guide.



https://docs.tenable.com/tenablesc/Content/NessusScanners.htm



https://docs.tenable.com/nnm/Content/ConfigurationNNMSettingsSection.htm

https://docs.tenable.com/tenablesc/Content/NNMInstanceSettings.htm

https://docs.tenable.com/tenablesc/Content/NNMInstanceSettings.htm

https://docs.tenable.com/tenablecore/NNM/Content/TenableCore/Introduction_NNM.htm

Appliance Quick Reference

This documentation is end-of- life (EOL) due to the Tenable Appliance product EOL.

Appliance Interface

Back Up Appliance

Expand Virtual Disk - Hyper-V

Expand Virtual Disk - VMware

Restore from File

Updates

Appliance Migrat ion - 3.x to 4.x

Virtual Image Migrat ion



Appliance Interface


The Appliance interface is comprised of a top navigation bar containing several options with expanded

drop down lists and a main information/ work section.

Click on the top navigation bar options (Appliance, Administration, Backup, Networking, Applications,

Logs, and Support) in the image below to go to the corresponding Appliance sections.



Back Up Appliance


Regular backups of Tenable Appliance data help to ensure redundancy and data recovery in the event

of system failure.

l A Whole Appliance backup backs up appliance configurations and all application data.

l A System Configuration backup backs up the Tenable Virtual Appliance configuration. No applic-

ation data is backed up.

l An application backup backs up all application data and configuration.

To back up application data on the Tenable Appliance:

1. Log in to the Tenable Appliance.

2. In the top navigation bar, click Backup.

The Backup Appliance page appears.

3. In the Take Backup of drop-down box, select the application you want to back up.

4. Click Take Backup.

The Proceed with generating backup page appears.

5. Click Take Backup.

The backup completes and the Backup Appliance page reappears. The completed backup

appears in the Available Backupssection.

6. In the Available Backupssection, select the completed backup you want to download.

7. Click Download Backup to download a backup.

The backup downloads.

Automated Backups

You can set up Automated Backups by selecting the Enabled option in the Automated Backups sec-

tion.



1. Click the edit icon ( ) to set the time month, day of the week, hour and minute for the auto-

matic backups.

2. Click Store Automated Backupsdrop down list option to select the location to store the

backups.

3. Click Save Schedule button to confirm your selections.

A green bar will display at the top of the screen indicating the system successfully saved your

automated backup.

Note: The automatic backup feature deletes the backup from the Appliance local disk after the transfersucceeds.

Remote Backup Locat ion

The Automated Backups section provides an option to store backups at a remote location. To use this

feature, the Remote Backup Location must be configured. The table below provides descriptions for

the items that need to be entered. After the information has been entered, click Save Remote Config.

Option Description

Remote Backup Location This is the location where the backup is sent. (supports SCP)

Destination Path This is the location on the machine (file path location).

SSH Known Host File This is the SSH public (host) key of the server the Appliance con-

nects to. Enter an SSH Private Key.

Note: The SSH Key must be passphrase protected.

Port This is the port that is connecting to the Appliance.

Authentication This information is required to access the system. Enter the

Username and either a Passphrase or SSH Private Key. (The

SSH Private Key is preferred.)

Note: Backups must be scheduled when no jobs are running and the system is in an idle state.



Expand Virtual Disk - Hyper-V

The Tenable Appliance supports expanding the virtual hard disk to increase the storage capacity of the

Appliance.

Note: The instructions provided here are to be used as guidelines. The specifics may be slightly dif-ferent for your environment. Please refer to the appropriate Hyper-V manual for your environment.

Locate Disk to be Expanded

Power off your VM and navigate to the settings of your VM host. Two hard drives will be configured.

The first disk is named OS.vhd and should not be altered unless instructed to by Tenable Support.

The second drive, named Data.vhd, is the disk to choose for expansion.

Note: Once you increase the size of the virtual drive, it cannot be reduced later. Additionally, do notexpand it to a size larger than your physical storage can accommodate.

Click on the Edit button for the properties of the disk. Select Expand from the Choose Action option,

and select Next to display the screen to select the new size. Enter the new size value and click Finish to

close the window and expand the drive to the new size.

Ignore Repartit ion Notice

Once the process completes you may be presented with a dialog box indicating that you must repar-

tition and expand the file system on the guest operating system.

Note: Disregard this notice as the Tenable Appliance will apply the required changes on its next boot.

Boot Appliance

Once the process is complete you can boot your Tenable Appliance VM and make use of the additional

space on the newly expanded disk.



Expand Virtual Disk - VMware

The Tenable Appliance supports expanding the virtual hard disk to increase the storage capacity of the

Appliance. Follow the steps described in this appendix to expand your virtual disk.

Note: The instructions provided here are to be used as guidelines. Two VMware products are describedhere: VMware Player and the vSphere Client. Due to differing VMware platforms, products, and versions,the specifics may be slightly different for your environment. Please reference the appropriate VMwaremanual for your environment.

Locate Disk to be Expanded

Power off your VM and navigate to the properties of your VM host. There you will find two hard disks.

The first one, labeled Hard Disk (SCSI), is 20 GB in size. The second drive, labeled Hard Disk 2 (SCSI),is 30/ 180 GB in size by default and is the disk to choose for expansion.

Note: Once you increase the size of the virtual drive, you cannot reduce it later. Additionally, do notexpand it to a larger size than your physical hard disk can store.



Restore from File


If you have previously saved the Appliance configuration to a file, you can restore the configuration by

selecting the file from the Choose File button and selecting the Whole Appliance or individual applic-

ation to be restored from the drop-down box. If the application is not contained in the backup file

selected, no restore operation will be completed. Supported versions of the backups that may be

restored are listed on the screen.

To restore a backup to an Appliance that has enabled applications contained in the backup:

1. From the Backup tab, scroll to the Restore from File section, and select Only Nessus from the

drop-down box.

2. Navigate to the Nessus Only backup file, and click Upload Backup File.

3. Click the Backup Existing or Restore Backup button.

4. Click the Discard Existing and Backup button.

Note: When restoring a backup file from a previous version of Tenable software, it will be upgraded tothe currently installed version on the Appliance.



Updates


Update Appliance

You can download updates from the Tenable Virtual Appliance 4.8 section of the Tenable Down-

loads page. The update(s) should be stored locally before performing the installation. Update pack-

ages can be applied to either the hardware or VM version of the Appliance unless otherwise noted.

To apply the update, click Choose File, then browse to the location that the update file was saved. A

green banner will display if the update is successful. A red banner will display if the update is



https://www.tenable.com/downloads/tenable-appliance

https://www.tenable.com/downloads/tenable-appliance

unsuccessful stating the problem that caused the error. After applying the update, the license will be

shown again.

The update can be confirmed by viewing the version information in the Appliance tab.

Note: The best practice is to store locally. Storing locally prevents issues with browser upload.

Update Availabil ity Detection

The Appliance has the ability to check for updates. When an update has been detected, a banner will

appear at the top of the interface until it is installed.

Click the Configure Automatic Update Detection button to set up automatic checks. The system is

set to Apply Updates Automatically by default. Selecting the Check for Updates Automaticallyoption alerts the user to updates in the interface, but does not apply them without user intervention.

This feature cannot be disabled.

In addition, an HTTP proxy may be configured. This proxy setting only applies to the Update Availability

Detection option.



Appliance Migration - 3.x to 4.x

This document provides instructions on how to upgrade from Tenable Appliance 3.10.1 to the latest

version.

Note: Click the link to view the Supported Upgrade Paths.

The migration steps will require:

l Upgrade to Tenable Appliance version 3.10.1.

l Disk migration to 4.2 and upgrade to the most recent version (3.X> upgrade to 3.10.1 > migrate

to 4.2 > upgrade to latest).

Migration Steps

1. Upgrade to Tenable Appliance 3.10.1 using the TenableAppliance -3.10.1-5-update.tar via the

Administration > Updatespage.

Note: All upgrade files are located here. (You may have to log in before being directed to theupgrade files page.)

2. Install and configure another virtual image running Tenable Appliance v 4.2.

3. Attach the drives from Appliance 3.10.1 to Appliance 4.2 and complete the import process, as

described in Virtual Image Migrat ion.

l Click here for steps on attaching drives in VMware.

l Click here for steps on attaching drives in Hyper-V.

4. Upgrade 4.2 to the latest 4.Xversion.

5. Click the Check for Updatesbutton to install any patches.

When importing data in step 3, you may receive an import error due to version mismatch on Ten-

able.sc. Please note that Version 3.10.1 can update OTA to include a version of Tenable.sc that is more

recent than the version that ships on version 4.2. To remedy this, update Tenable.sc via the Appliance

GUI, or manually update the Appliance to version 4.3 or 4.4, then run the import again.

Note: For instructions on updating the OTA, see Updates.



https://docs.tenable.com/releasenotes/Content/appliance/appliance38.htm


https://www.vmware.com/support/ws45/doc/disks_add_ws.html

https://technet.microsoft.com/en-us/library/cc956004.aspx

l Prior to performing the migration, it is recommended to make a backup of the current virtual

image. This provides a recovery option if there is an issue during the migration process.

l Depending on the amount of data currently on the virtual image, the migration process may take

several hours to complete while the data is being copied between the old and new disks.

l This process only migrates data for the Tenable applications that were previously installed. Sys-

tem configuration settings from the previous Appliance are not migrated. The password you set

on the new virtual image won’t be replaced with data from the attached disks. You can restore a

System Configuration backup (by uploading or using one on the attached disks) if you want to

restore those settings.

Note: For instructions on restoring a System Configuration backup, see Restore from File.

l Due to differences in products, platforms, and versions, the steps described here are written for

general use. The specific wording of options varies depending on the software being used.

l A migration option is available on the wizard if the drives are attached for import before launch-

ing the Appliance image.



Virtual Image Migration


The virtual Appliance supports direct import of application data from older Tenable Appliance virtual

disks. The process for importation involves adding the previous Appliance's disk files to the new Appli-

ance as a third and fourth drive.

l Prior to performing the migration it is recommended to make a backup of the current virtual

image. This provides a recovery option if there is an issue during the migration process.

l Depending on the amount of data currently on the virtual image, the migration process may take

several hours to complete while the data is being copied between the old and new disks.

l This process only migrates data for the Tenable applications that were previously installed. Sys-

tem configuration settings from the previous Appliance are not migrated. The password you set

on the new VM won’t be replaced with data from the attached disks. You can restore a System

Configuration backup (by uploading or using one on the attached disks) if you wish to restore

those settings.

l Due to differences in products, platforms, and versions, the steps described here are written for

general use. The specific wording of options varies depending on the software being used.

l A migration option is available on the wizard if the drives are attached for import before launch-

ing the Appliance image.

Steps in Wizard

Use the following steps to perform virtual image migration before the Appliance has been installed.

1. The screen shot below reflects what displays in the wizard during the initial setup if the old Appli-

ance's disks are attached before accessing the UI. This provides the ability to import an applic-



ation prior to setting the password and accepting the license agreement.

l If the import is not done at this time, it can be done later in the Appliance UI by going to Admin-

istration tab (see Steps in Appliance UI below). A yellow circle if displays if disks are recognized.



2. The system will then display the VM Import page.

3. Click on the Import Application Data button to complete the process.

Steps in Appliance UI

Use the following steps to perform the virtual image migration after Appliance has been installed.

1. Shut down your newly deployed Tenable Appliance VM.

2. Edit the settings for the newly deployed Tenable Appliance VM within your VM software. Under

the Hardware section, begin the process to add another hard disk. Choose to use an existing vir-

tual disk and select the *-disk1/OS.vhd then *-disk2/Data.vhd files in that order from

your existing Appliance. If asked, choose to keep the existing format of your .vmdk files.

Note: When selecting the second .vmdk f ile, note that you must again browse to the directorycontaining your previous disk files. The VMware software does not open for browsing in the pre-viously used directory.

3. Once the disk addition is complete, start your Tenable Appliance image.



Some versions may display a message warning against using a duplicate UUID. Select the Yesbut-

ton and continue to start.

Use your web browser to navigate to your Tenable Appliance web interface.

4. At the top of the Admin page a Tenable Application Data Import section will be displayed.

5. When the Import Application Data button is clicked, it will perform the import of data in the

background.

6. Once the page reloads, the Import Application Data button will be replaced with text indicating

that the import process is in progress. The System Log contains progress messages and includes

a final Application Data Migration Finished message.

7. Once the migration is complete, shut down the Tenable Appliance. Edit your virtual image and go

to the Hardware section to remove the Appliance .vmdk disks added in step 2.

8. After removing the hard disks, boot the updated version of Tenable Appliance. You may log into

your applications and find your previous data is now available.

Note: To prevent disks from attaching in inverse order, disks will import a prior VM.



Tenable Appliance-Tenable Core Migration Guide · 2020-05-18 · Tenable Appliance to Tenable Core...

Documents

Transcript of Tenable Appliance-Tenable Core Migration Guide · 2020-05-18 · Tenable Appliance to Tenable Core...