Skip to content

Commit b8b3857

Browse files
amee-sumojpipkin1
andauthored
Snowflake authentication update (#5912)
* Snowflake authentication update * Update blog-service/2025-10-13-collection.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update blog-service/2025-10-13-collection.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update blog-service/2025-10-13-collection.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-sql-api.md Co-authored-by: John Pipkin (Sumo Logic) <[email protected]> * changed release date --------- Co-authored-by: John Pipkin (Sumo Logic) <[email protected]>
1 parent c7f66dc commit b8b3857

File tree

3 files changed

+42
-0
lines changed

3 files changed

+42
-0
lines changed
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
title: Snowflake Authentication Update (Collection)
3+
image: https://assets-www.sumologic.com/company-logos/_800x418_crop_center-center_82_none/SumoLogic_Preview_600x600.jpg?mtime=1617040082
4+
keywords:
5+
- c2c
6+
- snowflake
7+
hide_table_of_contents: true
8+
---
9+
10+
import useBaseUrl from '@docusaurus/useBaseUrl';
11+
12+
### What's changing?
13+
14+
Starting November 2025, Snowflake will block single-factor authentication (password-only sign-ins) as part of their enhanced security protocols.
15+
16+
Snowflake has signed the CISA *Secure by Design* pledge and is committed to adopting security best practices, including:
17+
- Eliminating high-risk authentication methods (for example, password-only access)
18+
- Enforcing multi-factor authentication (MFA)
19+
- Reducing the risk of credential theft and unauthorized access
20+
21+
These changes are designed to strengthen Snowflake’s overall security posture and better protect your data.
22+
23+
### Next steps
24+
25+
As an interim measure, Sumo Logic recommends you to use the Programmatic Access Tokens (PATs) to authenticate your Sumo Logic integration with Snowflake before 1st November 2025. This ensures continued access and seamless data collection from the Snowflake platform.
26+
27+
Refer to [Using programmatic access tokens for authentication](https://docs.snowflake.com/en/user-guide/programmatic-access-tokens) for step-by-step instructions to authenticate the integration with Snowflake.
28+
29+
:::note
30+
- Programmatic Access Tokens (PATs) provide a short-term authentication solution, with each token expiring after approximately one year. So, you must generate a new token annually until a long-term multifactor authentication solution becomes available.
31+
- Sumo Logic is actively developing a long-term authentication solution using OAuth 2.0, which will provide enhanced security and ease of use. More information and rollout timelines for OAuth 2.0 support will be shared in the upcoming release.
32+
:::
33+
34+
[Learn more](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source/#vendor-configuration).
35+
36+
For more information, contact your Technical Account Engineer (TAE) or reach out to Sumo Logic Support.

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-logs-source.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,9 @@ The Snowflake Logs source requires you to provide the following data to setup th
3737
- **Account Identifier**. An account identifier uniquely identifies a Snowflake account within your organization, as well as throughout the global network of Snowflake-supported cloud platforms and cloud regions. For more information, see [Account identifiers](https://docs.snowflake.com/en/user-guide/admin-account-identifier).
3838
- **Username**. Snowflake account's login username. For example, `SUMOLOGIC`.
3939
- **Password**. Snowflake account's login password. For example, `yufncixxxxxxxxxp55hbdy7`.
40+
:::note
41+
Starting November 2025, Snowflake will block single-factor authentication (password-only sign-ins) as part of their enhanced security protocols. Sumo Logic recommends that you update your integration to [Programmatic Access Tokens (PATs)](https://docs.snowflake.com/en/user-guide/programmatic-access-tokens) before 1st November 2025 to ensure continued access.
42+
:::
4043

4144
Once you have all the required values, set up the source configuration to collect your desired log types available in the configuration section.
4245

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/snowflake-sql-api.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,9 @@ To collect metric data from the Snowflake SQL API, you must have an authorized S
2727
1. Collect your admin account identifier following the instructions in the [Snowflake documentation](https://docs.snowflake.com/en/user-guide/admin-account-identifier). The identifier should look something like this: `wp00000.us-east-2.aws`.
2828
1. Take note of the database name you plan to query.
2929
1. Collect your Snowflake Programmatic Access Token following the instructions in the [Snowflake documentation](https://docs.snowflake.com/en/user-guide/programmatic-access-tokens).
30+
:::note
31+
Starting November 2025, Snowflake will block single-factor authentication (password-only sign-ins) as part of their enhanced security protocols. Sumo Logic recommends that you update your integration to [Programmatic Access Tokens (PATs)](https://docs.snowflake.com/en/user-guide/programmatic-access-tokens) before 1st November 2025 to ensure continued access.
32+
:::
3033
1. Optional additional information such as a role, warehouse, or schema name can also be configured with the source.
3134

3235
### Source configuration

0 commit comments

Comments
 (0)