ServiceNow
Visualize ServiceNow resources and monitor them through queries and alerts.
- Installation
- Authorization
- Data Model
- Types
- Release Notes
Installation
Before configuring this integration in JupiterOne, create a dedicated service account with read access in ServiceNow:
Required in ServiceNow:
- A dedicated service account user (for example,
JupiterOne) - A custom read-only role (for example,
jupiterone_reader) - Access Control Lists (ACLs) that grant that role read access to the required tables
- Your ServiceNow instance hostname (for example,
yourcompany.service-now.com)
Authentication: This integration uses HTTP Basic authentication with a username and password.
Required table access: The service account must have read access to these base tables:
sys_user- user datasys_user_group- group datasys_user_grmember- group membership dataincident- incident datasys_db_object- table metadata used to resolve CMDB classescore_company- company data
Additional roles for optional data:
- CMDB: to ingest CMDB items, views and relationships, add the
cmdb_readrole, which grants read access to thecmdb_citables as well ascmdb_rel_typeandcmdb_rel_ci. - Incidents: incidents are read from the
incidenttable. Theitilrole grants this access; alternatively, grant read onincidentthrough the custom role's ACLs. - Vulnerable Items: requires the licensed Vulnerability Response application and the
sn_vul.read_allrole. - Configuration Compliance: requires the licensed Configuration Compliance application and the
sn_vulc.readrole.
Optional write access: If you want JupiterOne to create ServiceNow incidents from alert rules, create an additional role (for example, jupiterone_incident_creator) with Create access to the incident table.
Detailed setup instructions are provided in the Configuration in ServiceNow section below.
To allow JupiterOne to fetch data from your ServiceNow account, create a ServiceNow role with read-only access, grant it the tables above through ACLs, and assign it to a dedicated ServiceNow user.
ServiceNow enforces MFA on interactive (human) user accounts, which blocks Basic-auth API sign-in. Make the service account API-only by enabling Web service access only on the user record, and set a local password so Basic authentication can use it.
Configuration in ServiceNow
-
Create a read-only role. Go to All > User Administration > Roles > New and create a role named
jupiterone_reader. -
Create an access control rule (ACL) for each required table. Go to All > System Security > Access Control (ACL) > New and create a rule with Type
record, Operationread, Requires role set tojupiterone_reader, and Name set to each table and its fields (<table>and<table>.*). Creating ACLs requires elevating to thesecurity_adminrole. Create rules for the following tables:sys_usersys_user_groupsys_user_grmemberincidentsys_db_objectcore_company
-
Create the service account user. Go to All > User Administration > Users > New and create a user named
JupiterOne. Set a local password, enable Web service access only, and record the username and password; you need them when configuring the integration in JupiterOne. -
Assign the role. Open the
JupiterOneuser, go to Roles > Edit, and addjupiterone_reader. Add any of the following roles for the data you plan to ingest:cmdb_readfor CMDB items, database views and relationships. This base system role grants read access to the CMDB tables and is contained in theassetrole. See the base system roles reference for details.itilto read theincidenttable, unless yourjupiterone_readerACLs already grant read onincident.sn_vul.read_allfor Vulnerable Items. This requires the licensed Vulnerability Response application.sn_vulc.readfor Configuration Compliance test results. This requires the licensed Configuration Compliance application.
-
(Optional) To let JupiterOne create ServiceNow incidents from JupiterOne alert rules, create an additional role (for example,
jupiterone_incident_creator), add an ACL with Typerecord, Operationcreate, Nameincidentandincident.*, and Requires role set to that role, then assign it to theJupiterOneuser.
Configuration in JupiterOne
To install the ServiceNow integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select ServiceNow. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the ServiceNow account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle is enabled. -
Description to assist in identifying the integration instance, if desired.
-
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
Your ServiceNow Hostname (for example,
j1.service-now.com), Username, and Password. -
Your ServiceNow CMDB Classes to ingest, as a comma-separated list of classes (up to 20).
Click Create once all values are provided to finalize the integration.
Advanced Options
Additional configuration can be set to customize the ingested data.
User Configuration
- Custom fields to include in User entities adds the named custom fields (by field key) to each user entity. Separate fields with commas.
- Excluded User Classes excludes users whose system class name (
sysClassName) matches one you list, so they are not created as User entities.
Host Configuration
- Host Classes lists the system class names that are treated as hosts and mapped to the JupiterOne Device data model.
- Custom fields to include in Host entities adds the named custom fields to each host entity.
- Custom fields to include in CMDB entities adds extra fields to generic CMDB entities, which are otherwise dropped on scoped or custom tables. Use a dot-path for reference fields (for example,
primary_owner.value). - Fallback name fields for CMDB entities is an ordered list of fields used to name a CMDB entity when its
namecolumn is empty. The first field with a value is used, and entities that already have a name are unaffected. Prefix an entry with<sys_class_name>:to apply it to one class only. - CMDB owner reference fields lists reference fields whose referenced user owns the CMDB item. Each one produces a user OWNS CMDB relationship in addition to the standard
owned_bycolumn. - CMDB group reference fields lists reference fields whose referenced group uses the CMDB item. Each one produces a group USES CMDB relationship. This requires the Groups ingestion source.
- CMDB host names field relates CMDB items to the hosts named in one of their text fields. See Relating CMDB items to hosts by name.
- CMDB custom field handlers maps a CMDB field key to the handler used to read its value, for columns whose shape the standard mapping does not understand. The only supported handler is
commaSeparatedToArray.
CMDB Database Views
- Database views to ingest lists the ServiceNow database views to ingest, each mapped to the alias of the view's primary joined table. List views here rather than under CMDB Classes, because a view is a join of several tables and is ingested separately, one record per row. This requires CMDB Classes to be set as well.
- Database view row key columns maps a database view name to the columns whose values identify each row. Leave this unset in almost all cases; set it only to deliberately group rows more coarsely.
Relating CMDB items to hosts by name
Some ServiceNow instances record which servers an application owns or uses in a text field on the CMDB item, such as a custom Owns or Uses Servers column on cmdb_ci_business_app, rather than (or as well as) in CI relationships. Set CMDB host names field to that field's key (for example u_owns_or_uses_servers) to turn those names into relationships.
- The field must hold host names separated by commas. Spaces around the names are ignored.
- Each name is matched case-insensitively against the
nameof the ingestedservice_now_cmdb_hostentities, so the host classes must be listed in Host Classes and included in the CMDB classes. - Each match creates a
service_now_cmdb_objectUSESservice_now_cmdb_hostrelationship. These are added alongside the relationships from the CI relationship table (cmdb_rel_ci) and do not replace them. - A name that matches more than one host is skipped, because there is no way to tell which host is meant. Names that match no host are also skipped.
- Leave the field empty to turn this off.
After a run, this query lists the applications and the hosts they were related to:
FIND service_now_cmdb_object THAT USES service_now_cmdb_host RETURN service_now_cmdb_object.name, service_now_cmdb_host.name
Excluded User Classes configuration option:
This J1QL Query can be executed to determine which system class names (sysClassName) of users exist within ServiceNow, after a successful job run without any User Class Exclusions:
FIND service_now_user RETURN count(service_now_user), service_now_user.sysClassName
Data Volume Configuration
Control how much CMDB, vulnerability and configuration compliance data is ingested from ServiceNow to manage storage and processing volume.
Ingestion Windows
| Field | Description | Default | Options |
|---|---|---|---|
| Vulnerability Timeframe (days) | Only ingest vulnerable items found within the last N days, based on each item's last-found date. Leave empty to ingest all. | All ages | Enter a number of days (for example, 30) |
Data Filtering Options
| Field | Description | Default | Options |
|---|---|---|---|
| Install Status Filter | Limit CMDB items to the listed install statuses, as a comma-separated list of install status values (for example, 1,2,6). | All statuses | 1 In Use, 2 Planned, 6 In Stock, and other values configured in your instance |
| Vulnerability Severities | Limit ingestion to vulnerable items with the selected source severities. | Critical, High, Medium | Critical, High, Medium, Low, None/Info |
| Vulnerability States | Limit ingestion to vulnerable items in the selected states. | Open, Under Investigation | Open, Under Investigation, Closed, In Review, Awaiting Implementation, Resolved, Deferred |
| Configuration Compliance Filter | A raw ServiceNow encoded query applied to the test result table. When set, it replaces the default rather than adding to it. Avoid queries that include passing results on large instances, as they are usually the overwhelming majority of the table. | sourceLIKEqualys^resultINFailed,Fail,Error (failing Qualys results) | Any ServiceNow encoded query |
Advanced Configuration
| Field | Description | Default |
|---|---|---|
| Custom fields to include in Company entities | Adds the named custom fields (by field key) to each company entity. Use a dot-path for reference fields (for example, u_duns.value). | None |
| Vulnerability Table | The ServiceNow vulnerability table to ingest. | sn_vul_vulnerable_item |
| Configuration Compliance Table | The ServiceNow Configuration Compliance test result table to ingest. | sn_vulc_result |
| Scanner Result ID Column | The column on the test result table that holds the scanner-assigned result id (the Qualys Posture ID for Qualys Policy Compliance). Leave empty to auto-detect it from source_id, id and external_id. | Auto-detect |
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Roles
RBAC roles that must be assigned to the integration principal.
Show Roles (4)
cmdb_readitilsn_vul.read_allsn_vulc.read
Endpoints
API endpoints that the integration makes requests to.
Show Endpoints (13)
GET https://{hostname}/api/now/table/cmdb_rel_ciGET https://{hostname}/api/now/table/cmdb_rel_typeGET https://{hostname}/api/now/table/core_companyGET https://{hostname}/api/now/table/incidentGET https://{hostname}/api/now/table/sys_choiceGET https://{hostname}/api/now/table/sys_db_objectGET https://{hostname}/api/now/table/sys_userGET https://{hostname}/api/now/table/sys_user_grmemberGET https://{hostname}/api/now/table/sys_user_groupGET https://{hostname}/api/now/table/{cmdb_class}GET https://{hostname}/api/now/table/{config_compliance_table}GET https://{hostname}/api/now/table/{view_name}GET https://{hostname}/api/now/table/{vuln_table}
Licenses
Product licenses or SKUs required in the target environment.
Show Licenses (2)
Configuration ComplianceVulnerability Response
Documentation Links
Links to provider documentation relevant to setup and configuration.
Show Documentation Links (5)
- https://www.servicenow.com/community/developer-forum/cmdb/m-p/2964768
- https://www.servicenow.com/docs/r/australia/api-reference/rest-apis/c_TableAPI.html
- https://www.servicenow.com/docs/r/australia/platform-administration/user-administration/r_BaseSystemRoles.html
- https://www.servicenow.com/docs/r/australia/security-management/configuration-compliance/view-vuln-config-compl-test-results.html
- https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/vulnerable-item-fields.html
Per-Data-Source Breakdown
Authorization required by the steps that make up each data source. Steps that depend on a data source are listed in the Per-Step Breakdown; the complete lists are in the sections above.
Show all data sources (9)
| Data Source | Roles | Endpoints | Licenses |
|---|---|---|---|
| CMBD Items | cmdb_read | GET https://{hostname}/api/now/table/sys_choice, GET https://{hostname}/api/now/table/sys_db_object, GET https://{hostname}/api/now/table/{cmdb_class} | - |
| CMDB Database Views | - | GET https://{hostname}/api/now/table/{view_name} | - |
| CMDB Relationships | cmdb_read | GET https://{hostname}/api/now/table/cmdb_rel_ci, GET https://{hostname}/api/now/table/cmdb_rel_type | - |
| Companies | - | GET https://{hostname}/api/now/table/core_company | - |
| Configuration Compliance Test Results | sn_vulc.read | GET https://{hostname}/api/now/table/{config_compliance_table} | Configuration Compliance |
| Groups | - | GET https://{hostname}/api/now/table/sys_user_grmember, GET https://{hostname}/api/now/table/sys_user_group | - |
| Incidents | itil | GET https://{hostname}/api/now/table/incident | - |
| Users | - | GET https://{hostname}/api/now/table/sys_user | - |
| Vulnerable Items | sn_vul.read_all | GET https://{hostname}/api/now/table/{vuln_table} | Vulnerability Response |
Per-Step Breakdown
Detailed authorization requirements for each ingestion step.
Show all steps (4)
| Step | Roles | Endpoints |
|---|---|---|
| CMDB Database Views | - | GET https://{hostname}/api/now/table/{view_name} |
| CMDB Relationships | cmdb_read | GET https://{hostname}/api/now/table/cmdb_rel_type, GET https://{hostname}/api/now/table/cmdb_rel_ci |
| Group Members | - | GET https://{hostname}/api/now/table/sys_user_grmember |
| Incidents | itil | GET https://{hostname}/api/now/table/incident |
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Account | service_now_account | Account |
| CMDB Host Object | service_now_cmdb_host | Host |
| CMDB Object | service_now_cmdb_object | Configuration |
| Company | service_now_company | Vendor |
| Configuration Compliance Test Result | service_now_config_test_result | Finding |
| Database View Record | service_now_view_record | Record |
| Incident | service_now_incident | Incident |
| User | service_now_user | User |
| User Group | service_now_group | UserGroup |
| Vulnerable Item | service_now_vulnerable_item | Finding |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
service_now_account | HAS | service_now_user |
service_now_account | HAS | service_now_group |
service_now_cmdb_object | ASSIGNED | service_now_user |
service_now_cmdb_object | ASSIGNED | service_now_group |
service_now_cmdb_object | HAS | service_now_view_record |
service_now_cmdb_object | USES | service_now_cmdb_host |
service_now_cmdb_object | CONNECTS | service_now_cmdb_object |
service_now_company | HAS | service_now_company |
service_now_group | HAS | service_now_group |
service_now_group | HAS | service_now_user |
service_now_group | MANAGES | service_now_cmdb_object |
service_now_group | USES | service_now_cmdb_object |
service_now_group | ASSIGNED | service_now_vulnerable_item |
service_now_group | ASSIGNED | service_now_config_test_result |
service_now_incident | ASSIGNED | service_now_user |
service_now_user | MANAGES | service_now_group |
service_now_user | MANAGES | service_now_user |
service_now_user | MANAGES | service_now_cmdb_object |
service_now_user | OWNS | service_now_cmdb_object |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
|---|---|---|---|
service_now_cmdb_object | CONNECTS | service_now_cmdb_object | FORWARD |
service_now_cmdb_object | HAS | service_now_vulnerable_item | FORWARD |
service_now_cmdb_object | HAS | service_now_config_test_result | FORWARD |
service_now_config_test_result | IS | qualys_compliance_finding | FORWARD |
service_now_vulnerable_item | IS | qualys_issue | FORWARD |
Service Now Cmdb Host
service_now_cmdb_host inherits from Host
| Property | Type | Description | Specifications |
|---|---|---|---|
assetFunction | string | Derived from the property named: "asset_function" | |
assetTag | string | Derived from the property named: "asset_tag" | |
assignedTo | string | Derived from the property named: "assigned_to.value" | |
attributes | string | Derived from the property named: "attributes" | |
businessUnit | string | Derived from the property named: "business_unit.value" | |
comments | string | Derived from the property named: "comments" | |
correlationId | string | Derived from the property named: "correlation_id" | |
department | string | Derived from the property named: "department.value" | |
discoverySource | string | Derived from the property named: "discovery_source" | |
dnsDomain | string | Derived from the property named: "dns_domain" | |
environment | string | Derived from the property named: "environment" | |
hardwareStatus | string | Derived from the property named: "hardware_status" | |
hardwareSubStatus | string | Derived from the property named: "hardware_substatus" | |
installDate | number | Derived from the property named: "install_date" | |
installStatus | string | Derived from the property named: "install_status". This property shows the recovered label. | |
location | string | Derived from the property named: "location.value" | |
managedBy | string | Derived from the property named: "managed_by.value" | |
managedByGroup | string | Derived from the property named: "managed_by_group.value" | |
mode | string | Derived from the property named: "mode" | |
numericInstallStatus | string | Derived from the property named: "install_status". This property shows the raw value. | |
numericOperationalStatus | string | Derived from the property named: "operational_status". This property shows the raw value. | |
operationalStatus | string | Derived from the property named: "operational_status". This property shows the recovered label. | |
orderDate | number | Derived from the property named: "order_date" | |
ownedBy | string | Derived from the property named: "owned_by.value" | |
subcategory | string | Derived from the property named: "subcategory" | |
substatus | string | Derived from the property named: "substatus" | |
sysClassNames * | array of strings | ||
terminated | boolean | Derived from the property named: "install_status". True when the CI is Retired, Stolen or Created in Error. | |
warrantyExpiration | number | Derived from the property named: "warranty_expiration" |
Service Now Company
service_now_company inherits from Vendor
| Property | Type | Description | Specifications |
|---|---|---|---|
city | string | null | Mailing address city. Derived from the property named: "city". | |
contactId | string | sys_id of the primary contact (sys_user). Derived from the property named: "contact.value". | |
country | string | null | Mailing address country. Derived from the property named: "country". | |
discount | number | Negotiated discount. Derived from the property named: "discount". | |
isCustomer | boolean | Whether this company is a customer. Derived from the property named: "customer". | |
isManufacturer | boolean | Whether this company is a manufacturer. Derived from the property named: "manufacturer". | |
isPrimary | boolean | Whether this is the instance's own/primary company. Derived from the property named: "primary". | |
isVendor | boolean | Whether this company is a vendor. Derived from the property named: "vendor". | |
marketCap | number | Market capitalization. Derived from the property named: "market_cap". | |
numEmployees | number | Number of employees. Derived from the property named: "num_employees". | |
state | string | null | Mailing address state. Derived from the property named: "state". | |
stockSymbol | string | null | Ticker symbol. Derived from the property named: "stock_symbol". | |
vendorType | string | null | Vendor classification. Derived from the property named: "vendor_type". | |
zip | string | null | Mailing address postal code. Derived from the property named: "zip". |
Service Now Config Test Result
service_now_config_test_result inherits from Finding
| Property | Type | Description | Specifications |
|---|---|---|---|
actualValues | string | null | The values the scanner actually observed on the configuration item. Derived from the property named: "actual_values". | |
assignedToId | string | null | sys_id of the individual working on this test result. Derived from the property named: "assigned_to.value". | |
assignmentGroupName | string | null | Name of the ServiceNow assignment group that owns remediation of this test result. Derived from the property named: "assignment_group.name". | |
closedOn | number | Timestamp at which the test result transitioned to closed. Derived from the property named: "closed". | |
controlId | string | null | The identifier assigned to the configuration test by the SCA scanner. For Qualys Policy Compliance this is the Qualys Control ID. Derived from the property named: "test.source_id". | |
expectedValues | string | null | The values the scanner expected the configuration item to report for a passing result. Derived from the property named: "expected_values". | |
firstSeenOn | number | Timestamp of the first import of this test result into Configuration Compliance. Derived from the property named: "first_seen". | |
isActive | boolean | Whether the test result is still active, i.e. has not been closed. Derived from the property named: "active". | |
lastPassedOn | number | Timestamp of the most recent date on which this test result passed. Derived from the property named: "last_pass". | |
lastSeenOn | number | Timestamp of the most recent import of this test result. Derived from the property named: "last_seen". | |
number | string | null | The number assigned to the test result during the import process (e.g. "CTR19994689"). Derived from the property named: "number". | |
resolution | string | null | Resolution calculated from the associated remediation task groups (e.g. "Stale"). Derived from the property named: "resolution". | |
result | string | null | Outcome of the configuration test as reported by the scanner: Passed, Failed, Error or Unknown. Derived from the property named: "result". | |
riskRating | string | null | Raw numeric risk rating (1-5) reported by ServiceNow, where 1 is the most severe. Derived from the property named: "risk_rating". | |
riskScore | number | Score derived from the criticality of the configuration test. Derived from the property named: "risk_score". | |
source | string | null | System name of the third-party SCA integration that produced the result (e.g. "Qualys"). Derived from the property named: "source". | |
sourceId | string | null | The identifier assigned to this test result by the third-party SCA scanner. For Qualys Policy Compliance this is the Qualys Posture ID, which is what joins the result to a qualys_compliance_finding. | |
state | string | null | Raw state value, calculated by ServiceNow from the remediation tasks the test result belongs to. Derived from the property named: "state". | |
stateLabel | string | null | Human-readable label for the numeric state value, when ServiceNow reports state numerically (e.g. "1" resolves to "Open"). | |
technology | string | null | The technology the test was evaluated against (e.g. "Windows 2019 Server"). Derived from the property named: "technology". | |
testId | string | null | sys_id of the configuration test (sn_vulc_test) this result evaluates. Derived from the property named: "test.value". | |
testName | string | null | Name of the configuration test, i.e. the control statement. Derived from the property named: "test.name". |
Service Now User
service_now_user inherits from User
| Property | Type | Description | Specifications |
|---|---|---|---|
employeeNumber | string | ||
sysClassName | string | ||
title | string |
Service Now View Record
service_now_view_record inherits from Record
| Property | Type | Description | Specifications |
|---|---|---|---|
rowKeyValues * | array of strings | ||
sysClassNames * | array of strings | ||
viewName * | string | Name of the ServiceNow database view this row was read from, e.g. "u_app_portfolio" |
Release Notes
-
2026-11-09 — ServiceNow configuration compliance test results now include the assignment group name, enabling table-based filtering and queries by remediation owner group.
-
2026-11-05 — ServiceNow CMDB host entities now include a terminated flag derived from the configuration item install status, enabling queries that distinguish active from retired configuration items.
-
2026-11-04 — ServiceNow CMDB host entities now read OS information from custom operating system columns when the standard OS field is empty, improving OS accuracy for deployments that store guest OS data in custom host fields.
-
2026-10-26 — ServiceNow CMDB configuration items now include normalized OS name, type, version, detail, and kernel version properties, enabling consistent OS-based queries across CMDB data.
-
2026-10-23 — CMDB entity names configured with reference columns now resolve to the referenced record's display name, improving the readability of configuration item names.
-
2026-10-22 — CMDB objects can now be linked to hosts named in a configurable text column, creating usage relationships between configuration items and their associated hosts.
-
2026-10-19 — Added support for linking user groups to CMDB objects via configurable reference fields, creating group-to-CI usage relationships.
-
2026-10-19 — ServiceNow CMDB database view records now include human-readable display names alongside system IDs for reference columns.
-
2026-10-15 — The ServiceNow Configuration Compliance ingestion default query now limits results to failing tests, reducing ingested data volume and focusing on actionable findings.
-
2026-09-25 — ServiceNow database view rows are now ingested as individual entities, linked to the CMDB objects each row joins, enabling SQL-view-level queries.
-
2026-09-04 — ServiceNow CMDB objects can now be linked to their owners via configurable reference field paths, creating user-to-CI ownership relationships.
-
2026-09-04 — CMDB entities without a primary name field can now be identified using a configurable set of fallback name fields.
-
2026-08-31 — Added ingestion of ServiceNow Configuration Compliance test results, linked to assigned groups, CMDB objects, and Qualys compliance findings.
-
2026-08-04 — ServiceNow incidents now include a direct web link property for quick navigation to the record in the ServiceNow portal.
-
2026-08-03 — ServiceNow incident entities now include a direct web link for quick navigation to the incident in ServiceNow.
-
2026-07-30 — Added ingestion of ServiceNow company records as vendor entities, including parent-company hierarchy relationships.
-
2026-07-13 — Added support for ingesting custom CMDB fields via a new configuration option, and linked Wiz integration assets to CMDB records via mapped relationships.
-
2026-03-31 — Added additional vulnerability states to ServiceNow vulnerable item ingestion, supporting Awaiting Implementation, Resolved, and Deferred states.
-
2026-03-24 — Added configurable default filtering for ServiceNow vulnerability ingestion, defaulting to open and under-investigation states and critical, high, and medium severities.
-
2026-03-23 — Added Vulnerable Items ingestion step, bringing in ServiceNow vulnerable item entities from the vulnerable items table with host and vulnerability relationships.
-
2026-02-24 — Added configuration field to specify custom fields for special handling during CMDB object ingestion.
-
2026-02-18 — Added user to group manager relationships for ServiceNow, linking the manager of each user group to the groups they manage.
-
2025-11-14 — Added ServiceNow user manages user relationship for assignment group managers.
-
2025-10-22 — Added strict filtering on sys class names configuration, improving CMDB object ingestion accuracy.
-
2025-10-02 — Added ServiceNow user manages user relationship derived from manager field.
-
2025-10-01 — Added integration filters for ServiceNow CMDB object entities, enabling subset ingestion by sys class name.
-
2025-08-27 — Added host custom fields configuration option for promoting custom CMDB host fields (mirrors existing user custom fields behavior).
-
2025-06-09 — Added ingestion of CMDB configuration item relationships as graph relationships between CMDB objects.