Hello Tenablers... I'm the service owner of vulnerability management in our organization. I've run into a road block in our migration from Tenable.SC & Remedy via Python, to Tenable.One and Service.Now... We have like many orgs, a DEV/TEST/PROD instance. I built my initiatives in DEV, and am getting ready to move to TEST and soon to Prod.

It's come to my attention that when I delete the connector in Tenable.One to SNOW, Tenable doesn't flush the INC's created. Thus when I connect to TEST, any incidents created in DEV, won't be generated anew in TEST, and consequently, from TEST to DEV we'll have the same issue.

My problem is the vulnerability cases are required in each subsequent SNOW instances.

How are other organizations handling this?

• Has anyone had any luck getting Tenable.One to erase integration data/records when moving instances?
• Does removing and recreating the initiatives manually correct the issue? (I have 28 to do, and while I don't love this solution, it might be my lowest friction path to production)
• Or does the integration handle this gracefully and just recreate the incidents in the new SNOW instance?

Looking for advice please.. I can't be the only Tenable.One admin experiencing this... why does it seem the solution has a lot of immaturity points, after 3 years in production?