ServiceNow Classification Details

This article summarizes what types of asset attributes can be enriched from our connector with ServiceNow CMDB, and the benefits of using that enriched data in policy.

 

ServiceNow Integration with Elisity

Our Integration is designed to provide two major benefits: 

  • Provide contextual data from CMDB into CCC to help our SecOps user persona to understand operational context about a device 
  • Enable customers to distinguish rogue devices from enterprise-managed and apply differentiated policies to them. By rogue devices, we mean devices of types that we have accurately identified – but which may not be owned or managed by our enterprise customer. 

Elisity looks the device up by MAC address (first in the CMDB network adapter table, then in cmdb_ci), then by IP address when IP Only Based Lookup is enabled, then by hostname when Hostname-Based Lookup is enabled.

When several CMDB records match, Elisity uses the best match, in this order:

  1. MAC + IP Address
  2. MAC Address
  3. IP Alone, when IP Only Based Lookup is enabled
  4. CMDB Name contains the hostname (case-insensitive)

Engage Elisity support to modify the behavior of the above query order.

The IP Only Based Lookup and Hostname-Based Lookup options under Advanced Settings on the ServiceNow connector control the last two steps of this query order. Hostname-Based Lookup is on by default; turn it off where hostnames are not reliably unique. See Connect ServiceNow CMDB for the configuration steps. 

 

Attribute Mapping

Below is a map of how attributes map from ServiceNow to Elisity's Cloud Control Center.

ServiceNow API Attribute Elisity Attribute Core Effective Attribute Policy Group Match Criteria
manufacturer Vendor Yes Yes
asset_tag Asset Tag No Yes
sys_class_name CMDB Class Name No Yes
name CMDB Name No Yes
department Department No Yes
short_description Description No Yes
fqdn FQDN Yes No
fqdn (part before the first ".") Hostname Yes No
location + location.country Location No Yes
managed_by Managed By No Yes
operational_status Operational Status No Yes
owned_by.name Owner No Yes
owned_by.user_name Owner Username No Yes
serial_number Serial Number No Yes
managed_by_group Managed By Group No Yes
support_group Support Group No Yes
u_business_org * Business Org No Yes
u_tech_org * Tech Org No Yes
u_ci_id * CI ID No Yes
subcategory Type Yes Yes
model_number Model Yes Yes
install_status Install Status No Yes
environment Environment No Yes
u_ci_ownership * CI Ownership No Yes
sys_created_by Created By ** No Yes
sys_updated_by Updated By ** No Yes
(derived by Elisity) Category Yes Yes

* Custom fields defined in your ServiceNow instance. If a field does not exist in your CMDB, the attribute is left empty and enrichment of the other attributes continues.

** Created By and Updated By support flexible matching (equals, not equals, contains) in Policy Group match criteria.

If a CI has no asset tag, Asset Tag shows SID-<sys_id>, or SLNO-<serial_number> when no sys_id is available.

Install Status and Environment contain the label shown in ServiceNow (for example, Installed or Retired), not the stored value. ServiceNow attributes appear on the device details page and can be added as columns in the Device Table. Attributes marked Yes in the Policy Group Match Criteria column are listed under ServiceNow Attributes when you build Policy Group match criteria. Known in ServiceNow is a value of the Trust Attributes criterion instead.

Category is an attribute derived from Elisity Intelligence and does not directly map to attributes in ServiceNow.

Additional Considerations

Refresh interval

By default, Cloud Control Center re-queries ServiceNow for each device every 24 hours. Change this with Global Timer (1 to 168 hours) under Advanced Settings. Devices Elisity already knows are queued for lookup as soon as the connector is created.

Device attributes can also be refreshed on demand: select Refresh Attributes from the ... menu on the ServiceNow tile in the Trust Attributes section of the device's IdentityGraph view.

Deployment Order: 

If ServiceNow functions are deployed after Elisity, admin-initiated refresh(es) will need to be triggered from CCC when the CMDB has been populated. 

If ServiceNow is used prior to an Elisity deployment and the CMDB is populated, admin intervention should not be necessary.  

 

Was this article helpful?
0 out of 0 found this helpful