> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/entitlement-data-discovery/credentials-discovery/servicenow-credentials.md).

# ServiceNow: Credentials

### Overview

BalkanID supports discovery and governance of credentials within ServiceNow as part of **IGA for Non-Human Identities (NHI)**.

All credentials are normalized into the BalkanID data model and surfaced in the Credentials tab, along with their associated identities, access relationships, and risk insights.

The associated credentials can also be seen under the specific application integration (ServiceNow) page.

### Required ServiceNow configuration for Credential Discovery

To enable full credential discovery, please refer to the [OAuth credential read permissions](/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/service-now-integration-setup.md#oauth-credential-read-permissions) section in the [Service Now Integration Setup](/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/service-now-integration-setup.md) page.

The OAuth application registry entry must have an **OAuth Application User** set. Without it, ServiceNow rejects the client-credentials token request and BalkanID cannot connect.

These Table API reads allow BalkanID to build a complete view of OAuth client and token inventory, access relationships, and derived role blast radius across the ServiceNow instance.

BalkanID retrieves **metadata only** — client secrets, token values, and password fields are never stored.

{% hint style="info" %}
**Early Access:** Credential discovery requires **IGA for Non-Human Identities (NHI)** to be enabled for your tenant.
{% endhint %}

### Credential Types Supported

BalkanID tracks the following ServiceNow credential types:

{% hint style="info" %}
Note: The credential types listed below are examples and do not represent the full set of supported ServiceNow credentials.
{% endhint %}

* OAuth Clients
* OAuth Tokens

### Common risks associated with ServiceNow Credentials include:

* Overentitled OAuth Clients: OAuth applications with token restrictions disabled, allowing broader token use than intended.
* Expired OAuth Tokens Retained in Inventory: Tokens past expiration still associated with users, reducing visibility into active programmatic access.
* Unscoped Application Users: OAuth clients whose application user carries excessive roles (for example, `admin`), expanding blast radius for client-credentials grants.
* Stale Token Holders: OAuth tokens still issued to inactive or locked-out users.

This ensures visibility and governance of programmatic access in ServiceNow, forming a critical part of IGA for Non-Human Identities.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.balkan.id/getting-started/entitlement-data-discovery/credentials-discovery/servicenow-credentials.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.