Post-Migration Actions
After you perform the migration to Tenable Core, perform the post-migration action items for all new instances of Tenable Core:
- Instances of Tenable Security Center
- Instances of Tenable Nessus Professional
- Instances of Tenable Nessus Manager
- Instances of Tenable Nessus Managed by Tenable Security Center
- Instances of Tenable Nessus Managed by Tenable Vulnerability Management
- Instances of Tenable Nessus Network Monitor
Instances of Tenable Security Center
- If you changed the Tenable Security Center hostname during the migration, update the hostname on your license. For more information, see the Tenable Community Guide.
- To continue learning about Tenable Core, see the Tenable Core + Tenable Security Center User Guide.
Instances of Tenable Nessus Professional
-
Update your Tenable Nessus activation code. For more information, see Update Activation Code in the Tenable Nessus User Guide.
- To continue learning about Tenable Core, see the Tenable Core + Nessus User Guide.
Instances of Tenable Nessus Manager
-
Update your Tenable Nessus activation code. For more information, see Update Activation Code in the Tenable Nessus User Guide.
- If you changed the Tenable Nessus Manager IP address during migration, you must reconfigure Tenable Nessus Manager in Tenable Security Center. For more information, see Nessus Scanners in the Tenable Security Center User Guide.
- To continue learning about Tenable Core, see the Tenable Core + Nessus User Guide.
Instances of Tenable Nessus Managed by Tenable Security Center
- If you changed the Tenable Nessus IP address during migration, you must reconfigure Tenable Nessus in Tenable Security Center. For more information, see Nessus Scanners in the Tenable Security Center User Guide.
-
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.
- To continue learning about Tenable Core, see the Tenable Core + Nessus User Guide.
Instances of Tenable Nessus Managed by Tenable Vulnerability Management
-
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.
- To continue learning about Tenable Core, see the Tenable Core + Nessus User Guide.
Instances of Tenable Nessus Network Monitor
-
Update your Monitored Network Interfaces in Tenable Nessus Network Monitor to reflect your updated NICs. For more information, see NNM Settings in the Tenable Nessus Network Monitor User Guide.
- If your Tenable Nessus Network Monitor instance is linked to Tenable Security Center, and you changed the Tenable Nessus Network Monitor IP address during migration, you must reconfigure Tenable Nessus Network Monitor in Tenable Security Center. For more information, see Tenable Nessus Network Monitor Instance Settings in the Tenable Security Center User Guide.
- To continue learning about Tenable Core, see the Tenable Core + NNM User Guide.