Skip to content
Cloud Security Breaches

Snowflake customer accounts (multiple organizations) (2024): what the sources say about the cloud incident

Snowflake customer accounts (multiple organizations) disclosed the incident on 30 May 2024. What was exposed, as the sources state it: not public. The ledger reads the access path as stolen user credentials and session tokens. The cloud or provider involved: Snowflake.

Open the ledger · Report a correction

Disclosed
30 May 2024
Incident window
from May 2024; the 10-K says further attacks followed
Cloud or provider
Snowflake
What was exposed
not public
How access was gained
Snowflake stated in its annual report that a threat actor accessed a number of customers’ Snowflake accounts because those customers had not met their obligations to implement multi-factor authentication and network access policies, and that it found no breach of its own platform or environment.
Access path
Stolen user credentials and session tokens
Kind of control that addresses it
require phishing-resistant multi-factor authentication and network allow-lists for every identity with access to the data platform, and rotate static credentials

In the words of the source

“we became aware that a cybersecurity threat actor had accessed a number of our customers’ Snowflake accounts as a result of such customers’ failure to fulfill certain of their obligations under our shared responsibility cybersecurity model” (regulator filing, Snowflake Form 10-K for fiscal year ended January 31, 2025)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. Snowflake Form 10-K for fiscal year ended January 31, 2025, read 16 Nov 2026

Last reviewed 16 Nov 2026.