Tenable connector s.o for assets

[CandyDee]

Morning all

I have just configured the tenable connector app and tenable for assets. wondering if anyone has had any user experience with the app as the documentation is alittle wooly and not very helpful.

Successfully configured the app and have configured a small export of assets from servicenow to be sent to tenable but im getting the below error in job when i run it. Anyone seen this issue before? i have reached out to tenable team to see if they can see any activity there side. 

when you create the job to export it has 2 fields "group type" and "group name" which im not sure what its refering to

error - No Data to Sync at this time. Although there may be matching records in the CMDB, those records did not contain values in the DNS Domain field

[CandyDee]

thanks frank, the test export which had 15 assets I configured do have the dns_domain filled in on each asset.

Also on the test export instead of "group type = dns", it can be changed to "group type = Static IP" and it gives the same error but the assets all have an ip address in their field-

No Data to Sync at this time. Although there may be matching records in the CMDB, those records did not contain values in the IP Address field

really dont know! 

[Frank Tate]

OK. I found the documentation from Tenable, and I agree with you - it doesn't have just a whole lot of detail, and no help with troubleshooting problems.

From the docs (step 11 on this page), it looks like there's an option in the Connector to set the Asset Logging Level to something more detailed than the default, which is "Errors Only". Is there a "debug" or "trace" level you can set that might produce some more useful data?

And when I mentioned Discovery before, that is in reference to the ServiceNow CIs. Normally, CIs get into the ServiceNow CMDB via discovery, though it's also possible to manually import or create them. Were these CIs created via discovery or a manual process?

Another path to possibly take is to try to export a single CI from ServiceNow, and then you can possibly change values in that CIs fields to see if they affect the error message seen.

Frank

[Ken Lesick]

Hi CandyDee, Were you able to get this problem resolved? 
I too am getting the message "No Data to Sync at this time.  Although there may be matching records in the CMDB, those records did not contain values in the DNS Domain field" but not able to sync the data despite filtering on records that contain values in the DNS Domain field. Please let me know how you may have resolved this issue. 

Thanks.

[CandyDee]

Evening Ken

Yes I did get it to work.

So there is a script include that runs on the import/export of assets. (dont have that name to hand sorry but its very easy to find) , i think its called tenableexport. 

In that script include, basically to successfully export servicenow assets out and over to tenable the script goes to the cmdb_rel_ip table and will only export assets that have a relationship in place with 'owned by' as 'owned by'.

So if your asset records dont have a 'related IP' address and 'owned by' in place they are ignored so your export comes up blank.

This didnt make sense to me but when i mentioned it to the asset team they knew exactly what I was on about regarding the 2 things needed.

In my case i was focusing on server assets and mine were never being found with the same error you are getting because our assets had been changed from OOB to customized for my environment. Tenable connector is configured to run on a OOB set up.

We had to then go through a very long excerise which is still on going regards to updating the assets with related ip in place with owned by 'owned by' in order to use the connector.

Hope this helps. It was a while now since I last picked it up.