Need to stop the ci's creation from Tenable

Purushotham Ga2 · ‎06-21-2023

Hi Experts,

We were integrated with Tenable.io. Now ci's are getting created into cmdb table in servicenow. Now we Need to stop the ci's creation from Tenable so please assist on this ASAP.

Thanks.

Manmohan K · ‎06-21-2023

@Purushotham Ga2

In the ServiceNow filter search bar, type Tenable. The Tenable applications appear.
In the left-hand menu, click Tenable Connector.
In the sub-menu, click Connectors. Your configured Tenable connectors appear.

Select your Tenable connector.

The selected connector page appears.

At the top of the page, deselect the Active checkbox.

Click Update.

The Tenable Connector deactivates. Repeat this to deactivate all your connectors.

View solution in original post

gml35 · ‎07-28-2023

It would also break the import of vulnerabilities correct? None of the scheduled imports are specifically pointing to the CMDB table They are pointing to the vulnerabilities table. I may be missing something. I've even tried removing the CI mapping from the transform map and the CIs and Assets keep getting created. There has to be something barried in there that is creating the CI. Also thnaks for your quick response @Manmohan K

gml35 · ‎07-28-2023

I'm having the same problems with Tenable and put in a ticket. @Manmohan K , disabling Tenable is not a solution.

gml35 · ‎07-31-2023

Found the answer to the issue. There is a thing called a IRE Data Source Rule. If you create a new rule in the IRE table, you can stop it from creating CIs in the CMDB computers table and any other CMDB table you want. This in turn stops asset creation when you have the two tables sync'd.