Sovereignty and compliance

Lessons from the 2024 Snowflake customer breaches: shared responsibility on any data platform

In 2024 attackers accessed more than 100 Snowflake customer environments using stolen credentials on accounts without multi-factor authentication. Investigators found Snowflake’s own platform was not breached. The lesson applies to every data platform: enforce single sign-on and MFA, restrict network access, rotate service credentials, monitor logs, and know exactly which controls are yours.

Published . Last updated

On this page

What happened?

From April 2024, a financially motivated group tracked as UNC5537 used credentials stolen by infostealer malware, some dating back to 2020, to log in to Snowflake customer accounts that did not require multi-factor authentication. Victims included Ticketmaster, Santander and AT&T. Mandiant and Snowflake found the incidents traced to compromised customer credentials, not a breach of Snowflake's own environment.

Why does it matter for every platform?

Because it is a shared responsibility failure, and every cloud data platform has the same split. The vendor secures the service. The customer configures identity, network access and credentials. When each side assumes the other has it covered, attackers walk through the gap.

What controls would have stopped it?

  1. Single sign-on with enforced MFA for every human user, with no password-only logins.
  2. Network policies that allow access only from known networks.
  3. Service account hygiene: key-based authentication, rotation and least privilege for non-human identities.
  4. Credential rotation after any malware infection or third-party breach.
  5. Monitoring of login sources, large exports and unusual queries.

What changed afterwards?

Snowflake introduced stronger MFA requirements and controls for customers. Across the industry, MFA moved from "recommended" to "required".

How does this relate to sovereignty?

Sovereignty is about who can compel access. Security is about who can break in. You need both. A sovereign platform with weak identity controls is still exposed.

How does DataNature handle these controls?

Atlas connects to your identity provider for single sign-on, so MFA and conditional access are enforced where your security team already manages them. Role-based access, row and column rules, network restrictions and audit logs of every login and query come standard, and the logs stay in your jurisdiction. Dlytica is ISO/IEC 27001 certified. See security.

Sources

How does DataNature Atlas keep this secure and compliant?

Every rule in this article is enforced in one place, inside your jurisdiction. DataNature Atlas is the platform's governance module:

  • Knows your data: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
  • Controls access: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
  • Governs AI: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
  • Proves it: lineage from source to metric to decision, and an audit log of who or what accessed which data.
  • Stays local: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.

These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read DataNature Atlas in depth or see security and compliance.

See it on your own data.

Book a demo

Demos and quotes are handled by Dlytica, the company behind DataNature.