Tanium logs reporting error: ServiceNow instance is missing the "Tanium" discovery sourceIssue When trying to connect Tanium with a ServiceNow instance, the Test Connection fails and Tanium logs report:Could not connect to ServiceNow instance: ServiceNow instance is missing the "Tanium" discovery source; caused by Error: ServiceNow instance is missing the "Tanium" discovery source.ReleaseAllCauseThere must be a Choice with Label Tanium and Value Tanium for the cmdb_ci.sys_choice column in accordance with Tanium's documentation: https://docs.tanium.com/asset/asset/exportasset.htmlPrepare ServiceNow to receive Tanium data1. In ServiceNow, add an entry for Tanium as a choice in the discovery_source column of the cmdb_ci table. Use Tanium as the value in both the Label and Value fields. The Tanium service account user must also be able to read the Choice [sys_choice] Label column. Out of box, all internal users can read this column, but if any Required Roles were added to this ACL, this could prevent the Tanium service account user from reading it.ResolutionIf not present, add a Choice record on the cmdb_ci.discovery_source column in the Choices relates list where the label is Tanium and the value is Tanium. https://instanceName.service-now.com/nav_to.do?uri=sys_dictionary.do?sys_id=2a5e0483db312200757eff9aae961948 Verify that no required roles have been added to this out-of-box sys_choice.label ACL: https://instanceName.service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=9bc03a0c1b021000aebbfbcd2c0713c8If there are required roles, you can remove them since all internal users should be able to read the Choice Labels. There are no required roles on this ACL out of box.