Case 0ADC44 · Famous breaches · L3 Applied
Your data warehouse is being copied
Live alertJune 2024: Snowflake and Mandiant publish UNC5537 IOCs. Your LOGIN_HISTORY shows password-only user SVC_REPORTING logging in from a VPS IP, then CREATE TEMPORARY STAGE, COPY INTO on customer tables, and GET.
- 01 What happened?
- 02 What is the impact?
- 03 What do you do?
What a strong answer covers
Try it out loud first. Then check yourself:
- Snowflake itself was not breached: UNC5537 reused creds stolen by infostealers, some dating back years, on accounts without MFA
- Stage, COPY INTO and GET is bulk exfiltration: treat the customer tables as stolen and expect an extortion demand
- Disable the user, rotate all Snowflake creds, add network policies and MFA, and preserve LOGIN_HISTORY and QUERY_HISTORY
- Scope from ACCOUNT_USAGE: which tables, how many rows, which IPs; then find the infected machine that leaked the password
- Start notification and legal work; victims included AT&T, Ticketmaster and Santander, so regulators and press will move fast
If the interviewer pushes back
- The leaked password came from a contractor's personal laptop. How do you stop third-party infostealer infections exposing your SaaS?