ServiceNow
Connector maturity: Beta. See Connector maturity.
Description
The ServiceNow connector uses the ServiceNow Table REST API to discover users, roles, and role assignments within a ServiceNow instance. It authenticates using Basic authentication or OAuth 2.0 and enumerates sys_user, sys_user_role, and sys_user_has_role table records to provide complete visibility into ITSM platform access, including admin and privileged role holders.
System Type Classification
| Field | Value |
|---|---|
| System Type | Application |
| Default Scan Priority | 500 |
Version Support
| OrbisID Edition | Supported |
|---|---|
| Community | No |
| Pro | Yes |
| Enterprise | Yes |
Supported Protocol
| Protocol | Port | Notes |
|---|---|---|
| Table REST API (HTTPS) | 443 TCP | HTTP Basic authentication or OAuth 2.0 |
What OrbisID Discovers
| Data | Source |
|---|---|
| Users | GET /api/now/table/sys_user |
| Roles | GET /api/now/table/sys_user_role |
| Role assignments | GET /api/now/table/sys_user_has_role |
| Groups | GET /api/now/table/sys_user_group |
| Group memberships | GET /api/now/table/sys_user_grmember |
| User enabled state | active field |
Connection Requirements
Required Permissions
Create a dedicated integration user with read access to user and role tables.
Minimum permissions:
- snc_read_only role or equivalent
- Read access to
sys_user,sys_user_role,sys_user_has_role, andsys_user_grouptables
Credential Mapping
| OrbisID Field | Value |
|---|---|
credential.username | ServiceNow integration username |
credential.password | ServiceNow password |
system.ipAddress (the IP Address / Hostname field) | Instance hostname (e.g., myorg.service-now.com) |
Network Requirements
The OrbisID server must have HTTPS access to the ServiceNow instance on port 443.
Configuration Steps
- In ServiceNow, create a service account: User Administration → Users → New
- Assign the
snc_read_onlyrole or grant table-specific read ACLs - Create a Credential in OrbisID:
- Username: ServiceNow integration username
- Password: ServiceNow password
- Navigate to Systems → Add System
- Fill in the fields:
| Field | Value |
|---|---|
| Name | Descriptive name (e.g., ServiceNow – Production) |
| OS Type | ServiceNow |
| System Type | Application |
| IP Address / Hostname | ServiceNow instance hostname |
| Credential | The scanning credential |
- Click Test Connection
- Click Save
Ticketing for findings
Requires Pro or Enterprise edition.
Besides scanning, OrbisID can raise tickets in this ServiceNow instance for findings, assigned to the finding's owner and an assignment group, and keep them in sync. Only one system can have ticketing turned on.
Open Systems, choose Ticketing on the ServiceNow system and set:
| Setting | Description |
|---|---|
| Raise tickets for findings | The switch. Nothing is raised until it is on |
| Credential | A credential that can create and update records in the table. Leave empty to use the system's scan credential |
| Table | incident, or a custom table with short_description, description, correlation_id, state and work_notes fields |
| Raise tickets for | Severities that raise a ticket. Critical and High by default |
| Assignment group | The group (by name) used when none is set for the severity, and one optional group per severity |
| Most tickets per run | Stops a large backlog flooding ServiceNow when you first turn this on. Default 50; the rest follow on later runs, most urgent first |
| Resolved state value | The state meaning resolved: 6 for incidents |
| Close code | Written when OrbisID resolves an incident, which needs one |
The credential's role needs create and write on the table, and read on sys_user and sys_user_group so the owner (found by email address) and the group (found by name) can be looked up. An owner or group that is not found is left blank and the ticket is still raised. Use Test connection to check the saved credential and table, and Sync now to run immediately.
Each ticket carries the finding's KRI, the affected item, system, severity, due date and a link back to the Findings page. Impact and urgency are set from the severity, so an incident's priority follows it.
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|---|---|
401 Unauthorized | Invalid credentials | Verify username and password in ServiceNow |
| No users returned | Missing table read ACL | Grant read access to sys_user table for the service account |
403 Forbidden | IP address restriction | Add OrbisID server IP to the ServiceNow IP allowlist |
| Partial data | Pagination limit | OrbisID uses sysparm_limit and offset pagination automatically |