> 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/snowflake-credentials.md).

# Snowflake: Credentials

### **Overview**

BalkanID supports discovery and governance of credentials within Snowflake 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 (Snowflake) page.

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FL87WMbkfiy5QOlu8j5Qt%2Fimage.png?alt=media&amp;token=9fc1785d-bde1-4cac-bd89-e11ceef4a44c" alt=""><figcaption></figcaption></figure>

### **Required Snowflake Roles for Credential Discovery**

\
To enable full credential discovery, please refer to the [APIs](/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/snowflake-integration-setup.md#h_01hq31cd90m44v2hpsyqg2zn0f) section in the [Snowflake Integration Setup](/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/snowflake-integration-setup.md) page

These APIs allow BalkanID to build a complete view of credential inventory, access, and usage.

### Credential Types Supported

BalkanID tracks the following Snowflake credential types:

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

* RSA Key Pairs
* User Passwords
* OAuth Delegated Authorizations
* External Cloud Integrations

### Common risks associated with Snowflake credentials include:

* Privileged Account Role: Account roles holding high-impact account-level privileges (such as `OWNERSHIP`, `MANAGE GRANTS`, `CREATE USER`, or `CREATE ROLE`) that can modify Snowflake access controls or administrative posture.
* Dormant Privileged User: Privileged users who have not logged in for 90+ days but still retain elevated access, creating stale high-risk paths.
* Public Role Has Elevated Access: The `PUBLIC` role — which applies to every user in the account, has been granted elevated privileges beyond minimal usage rights.
* Account-Wide Wildcard Grant: Roles containing account-wide wildcard grants with non-trivial privileges, giving overly broad access across the entire Snowflake account.
* Unused Credentials: Credentials that are configured on a user but have no observed successful authentication usage, creating unmonitored attack surface.
* Expired OAuth Delegated Authorization: Delegated OAuth authorizations that have passed their expiry date and should be cleaned up to reduce stale credential noise.

This ensures comprehensive visibility and control over credential-based access in Snowflake Accounts.


---

# 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/snowflake-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.