Rebecca_Range_will_and_final_testament.pdf
NadyaNayme - Resume - [Company Name].pdf
divorce_process.pdf
steps-to-take-after-a-car-accident.pdf
personal_injury_michael_perez_west_coast_trial_lawyers.pdf
embarassing_porno_filename.mp4
And this is a smalls subset of filenames that could not only provide PII but also potentially embarrassing or private information that isn't identifying but would be accompanied with files that are personally identifying.
I've also seen similar schemes used by doctor offices/hospitals, where you'll see the patient name and ailment. I once had to troubleshoot a backup problem for what turned out to obviously be an OB-GYN. Imagine my horror as I saw long filenames containing patient names and common STDs scroll by in the thousands.
Names or identifiers are the kinds of things that very often end up in file names.
Sexual Harassment Complaints/Persons Name.doc
...That’s taking it to the extreme, but it’s technically correct.
If you say “Read the law strictly enough” please do...
I'm still wondering, because Backblaze will sign a BAA (their website says so), making them a business associate. I'm not talking about some private person uploading their own documents. My concern is that given that Backblaze will sign a BAA, then some companies must be using Backblaze and potentially storing PHI data there. Yes?
Backblaze then need to follow: "§ 164.312 Technical safeguards. (e)(1) Standard: Transmission security. Implement technical security measures to guard against unauthorized access to electronic protected health information that is being transmitted over an electronic communications network."
Facebook isn't authorized to access this data, but that might be more of a problem for Backblaze, even if Facebook could be required to delete the data.