Earlier quoted context omitted.
No. And hence this will keep happening.
Even if there are, it’ll be minuscule compared to what is necessary to drive effective change. The fine for one person’s information from this site should be equivalent to their entire revenue for the year; should not be permitted to be resolved by bankruptcy, and should be required to transfer to any company purchasing their assets. Their entire executive team should be jailed for a minimum of 3 years per individual…
'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
11–20 of 193 posts
Re: 'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
#12Worth mentioning, because the authority level of medical practitioners throws people off. Don't ever give a doctor or practice your Social Security Number. They don't need it. Similarly if they want to check an ID that doesn't mean scan or photograph. Doctors, practices, etc are the worst at infosec. They have no training, basically no penalties if they do something wrong and all of that info is only to follow up in…
Re: 'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
#13Re: 'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
#14Move fast and violate HIPAA.
Does HIPAA apply to HR into, or just patient health data?
source: i run Wyndly (YC W21 https://www.wyndly.com), which is most easily understood as a telehealth allergist online.
Re: 'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
#15Re: 'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
#16Which means it's either old, or they recklessly opened it up because they couldn't get files uploaded/downloaded to the bucket from their mobile app/services.
Re: 'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
#17Earlier quoted context omitted.
Even if there are, it’ll be minuscule compared to what is necessary to drive effective change. The fine for one person’s information from this site should be equivalent to their entire revenue for the year; should not be permitted to be resolved by bankruptcy, and should be required to transfer to any company purchasing their assets. Their entire executive team should be jailed for a minimum of 3 years per individual…
Your proposal is so bizarrely out of proportion with the harm caused that I can’t tell if it’s parody or not. Why not execute them while you’re at it?
Re: 'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
#18Here we are. I guess we can blame the users and not any shitty security architecture slapped on AWS.
Clearly what matters most is that legal culpability be avoided, not that users will be secure. The former is 'shite security' while the latter is good security
Re: 'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
#19Worth mentioning, because the authority level of medical practitioners throws people off. Don't ever give a doctor or practice your Social Security Number. They don't need it. Similarly if they want to check an ID that doesn't mean scan or photograph. Doctors, practices, etc are the worst at infosec. They have no training, basically no penalties if they do something wrong and all of that info is only to follow up in…
In the US, HIPAA is pretty much the strongest privacy legislation there is. There's probably no group that would have a more severe penalty for leaking your info than your healthcare provider.
Re: 'Uber for nurses' exposes 86K+ medical records, PII via open S3 bucket
#20I'll need to dig up a source but I recently heard about this company and, apparently, before offering gigs they do a credit report to determine how much debt the person is carrying (i.e. how desperate they are) and they use that information to _round down_ the hourly rate they offer them. In the unlikely event that there are any negative consequences for this breach, they deserve every bit of them and more.