3 ms·
> They provide enough information (unfortunately) to identify the employee whose credentials were stolen, and she's a Sales Engineer. I'm not previously famili
by hn_throwaway_99 2y ago
> They provide enough information (unfortunately) to identify the employee whose credentials were stolen, and she's a Sales Engineer.
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.
- foobiekr 2y agoExactly, 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.
- p_l 2y agoBy customer giving their account permission to access customer's dataset.
- KingOfCoders 2y agoThe prospective customer copies their data to Snowflake so Snowflake can demonstrate their awesomeness with the customer data.
- lesuorac 2y agoBut 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.
- NotEvil 2y agoThe problem isn't the employee or the hiring process. It's the security infrastructure! One compromised account, supposedly from sales, shouldn't bring down the whole company.