Re:Snowflake, Cloud Storage Giant, Suffers Breach
by foobiekr on Friday May 31, 2024 @02:14PM
(#40538535)
Exactly, how is an SE privileged enough to cause a problem? Or for the activities to go unnoticed?
Like I would be very humiliated to have a system under my care that had this problem.
Re:Snowflake, Cloud Storage Giant, Suffers Breach
by p_l on Friday May 31, 2024 @05:24PM
(#40540422)
By customer giving their account permission to access customer's dataset.
Re:Snowflake, Cloud Storage Giant, Suffers Breach
by KingOfCoders on Saturday June 01, 2024 @01:50AM
(#40543221)
The prospective customer copies their data to Snowflake so Snowflake can demonstrate their awesomeness with the customer data.
Re:Snowflake, Cloud Storage Giant, Suffers Breach
by lesuorac on Friday May 31, 2024 @02:15PM
(#40538546)
But don't you see, we fired the problem so no more worries!
Oh, what's that. How did we change our hiring process to avoid hiring a problem again?
Sorry, my phones buzzing and I need to go.
--
Although obviously yes the problem isn't with hiring, it's with the system where a what should be fairly untrusted device shouldn't be able to exfiltrate a ton of data without setting a flag off somewhere.
I'm not previously familiar with Hudson Rock, nor how "standard" disclosures around this work, but identifying the breached employee felt like an extremely shitty move to me. If a single infected laptop of a sales engineer (i.e. not even an admin with extensive access rights) resulted in a breach this large, the root cause problem is not the sales engineer - and I'd note that Hudson Rock says as much in their article.