One thing I didn't know until recently is Snowflake has a massive fanbase, Apple and Amiga style - if you critique Snowflake in any way people flip tables. The comments on my blog are fun. I mean, the clue is in the product name, really.
IMHO it's fair to call out Snowflake's authentication isn't very good - it's the worst SaaS MFA solution I've seen as it has no top level, easy switch for org wide MFA enforcement.
Combined with putting all customers under *.snowflakecomputing.com sub domain is why their customers are getting owned - infostealers are just full of creds ready to go.
I gather Snowflake are discussing changes to fix, don't tell the fanboys (and yes, they're all dudes).
It’s the subdomain part I didn’t get, and I’m worried we’re doing the same thing. If it’s something bad and preventable, I’d like to get the right eyes on the problem ideally before it blows up.
Kinda interesting - Mandiant notified Snowflake that over 100 customers had data exfil issues, and Snowflake’s share price immediately began to tank in sells offs - before the incident was made public.
@GossiTheDog According to your timeline and the market data my own brokerage gives me access to, I see a nice big selloff the day after Mandiant notified Snowflake and the FBI, which is the day before the data popped up for sale.
Snowflake have told customers "We are also developing a plan to require our customers to implement advanced security controls, like multi-factor authentication (MFA) or network policies, especially for privileged Snowflake customer accounts."
Good! They also say the attack was "not caused by a vulnerability, misconfiguration, or breach of its product". Just happy little bad MFA.
Nice: "In a phone call this week, Jones (Snowflake CISO) told WIRED that Snowflake is working on giving its customers the ability to mandate that users of their accounts employ multifactor authentication going forward, “and then we’ll be looking in the future to [make the] default MFA,” he says."
This will be a great outcome for Snowflake customers and Snowflake itself. I know Snowflake got big mad at me for pointing it out, but that was a prime weakness in their MFA.
@GossiTheDog Do we know why it got removed? Did Snowflake C&D them? And if so, why, is there anything manifestly untrue in it? (Looked to me from the archive that HR was careful to state that this was all 'claimed by the hacker', not proven facts).
I think SaaS providers who provide their own authentication have a responsibility to provide robust, *enforceable* MFA for their customers - so if an org wants all their users to require MFA, they can and it’s just an easy tick box.
Some SaaS providers aren’t doing this - - and it’s the reason infostealer logs are such a problem. Their angle is customer is solely responsible, but as a counterpoint: see how that is working out for Snowflake.
An observation - AT&T, which today announced the biggest data breach of any telco worldwide ever - is down 0.35% on stock market
Snowflake, who own the SaaS platform, are down another 2%, 15% down over 3 months
Each breach has driven Snowflake’s share price down, but not their customer’s share price
In other words: 2024 reality, if you’re a SaaS provider, infostealers and cyber crime groups are a competitor - you have to be shit hot at authentication (even if it inconveniences the customer)
The AT&T Snowflake database wasn’t a law enforcement database, that is false.
They’re a major Snowflake customer, they put CDR in to do data analysis.
They subscribe to Snowflake Telecom Data Cloud and push petabytes of data in, as do other telcos. Snowflake had no way to mandate MFA on local accounts.
The latest Snowflake quarterly results dropped on Wednesday so I looked at their investor presentation, to see what they said about the security incident.
Nothing.
The company's net loss widened to $317 million, from $227 million during the same period a year earlier but this isn’t unusual, they have had accelerated losses for some time.
I should loop this in for more crazy on the Snowflake non-incident incident, where a bunch of teens ran around the poor security at both Snowflake and Snowflake's customers.
Boggles the mind that nation state China managed to get into various US telcos.. and so did a 20 year old kid, who had to be doxxed by @briankrebs to even get arrested.
I'm hoping this one goes to trial so the feds are forced to reveal what happened - as I understand it, various telcos exported CDRs - call record data - and put it into Snowflake Telco Cloud, which didn't have a feature to require MFA for every telco user account, and some users forgot to enable it.