Skip to main content

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​

FieldValue
System TypeApplication
Default Scan Priority500

Version Support​

OrbisID EditionSupported
CommunityNo
ProYes
EnterpriseYes

Supported Protocol​

ProtocolPortNotes
Table REST API (HTTPS)443 TCPHTTP Basic authentication or OAuth 2.0

What OrbisID Discovers​

DataSource
UsersGET /api/now/table/sys_user
RolesGET /api/now/table/sys_user_role
Role assignmentsGET /api/now/table/sys_user_has_role
GroupsGET /api/now/table/sys_user_group
Group membershipsGET /api/now/table/sys_user_grmember
User enabled stateactive 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, and sys_user_group tables

Credential Mapping​

OrbisID FieldValue
credential.usernameServiceNow integration username
credential.passwordServiceNow 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​

  1. In ServiceNow, create a service account: User Administration → Users → New
  2. Assign the snc_read_only role or grant table-specific read ACLs
  3. Create a Credential in OrbisID:
    • Username: ServiceNow integration username
    • Password: ServiceNow password
  4. Navigate to Systems → Add System
  5. Fill in the fields:
FieldValue
NameDescriptive name (e.g., ServiceNow – Production)
OS TypeServiceNow
System TypeApplication
IP Address / HostnameServiceNow instance hostname
CredentialThe scanning credential
  1. Click Test Connection
  2. 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:

SettingDescription
Raise tickets for findingsThe switch. Nothing is raised until it is on
CredentialA credential that can create and update records in the table. Leave empty to use the system's scan credential
Tableincident, or a custom table with short_description, description, correlation_id, state and work_notes fields
Raise tickets forSeverities that raise a ticket. Critical and High by default
Assignment groupThe group (by name) used when none is set for the severity, and one optional group per severity
Most tickets per runStops a large backlog flooding ServiceNow when you first turn this on. Default 50; the rest follow on later runs, most urgent first
Resolved state valueThe state meaning resolved: 6 for incidents
Close codeWritten 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​

SymptomLikely CauseResolution
401 UnauthorizedInvalid credentialsVerify username and password in ServiceNow
No users returnedMissing table read ACLGrant read access to sys_user table for the service account
403 ForbiddenIP address restrictionAdd OrbisID server IP to the ServiceNow IP allowlist
Partial dataPagination limitOrbisID uses sysparm_limit and offset pagination automatically