Help in migrating from tenable.sc to tenable.io

DavidP609780548
Tera Contributor

3 weeks ago

We are looking to migrate from tenable.sc to tenable.io.

We need to ensure continuity of open VITs that were opened by tenable.sc and still detected by tenable.io.

We need to avoid duplicate assets and VITs.  The VITs opened by tenable.sc should remain open with detections being updated to reflect the new detection from tenable.io.  We have a very large data set.  

I'm looking to hear from someone who has been through this already and hoping to learn from your experience.

We are hearing from support that we will likely have to abandon the continuity from tenable.sc however this leaves a lot of problems with fluctuation in metrics and compliance concerns.

0 Helpfuls
  • 342 Views
1 REPLY 1

Ranjane_Omkar
Kilo Sage

a week ago

@DavidP609780548,

 

Tenable.sc and Tenable.io use completely different detection ID formats, which poses a significant risk for a large-scale migration. Given your dataset, engaging a technical consultant with deep ServiceNow VR experience is strongly advised.

 

I'm not sure how helpful this will be, but you may want to refer to this article -https://www.servicenow.com/community/secops-articles/guidelines-to-migrate-from-tenable-built-vr-tenable-int...

 

Regards,

----
If this response was helpful, please select "Accept as Solution" and "Helpful." This helps both the community and me.

 

0 Helpfuls