None of your systems store patient data encrypted at rest.
Inadvertent data breaches are inevitable.
The very best you could possibly do is access logs and auditing. Which of your customers do any kind of auditing?
Inadvertent data breaches are inevitable.
The very best you could possibly do is access logs and auditing. Which of your customers do any kind of auditing?
I'm advocating Translucent Database techniques, where patient data is encrypted at the field and row (document) level. Much like a salted password file.
System level encryption still means the admins can still see the data. Therefore, breaches remain inevitable.
Translucent Databases http://a.co/d/5855TYO http://wayner.org/node/46
Think of how password databases don't actually store passwords. Instead they (should) be storing salted and hashed passwords.
---
Please see my other comment about plaintext demographic data vs using unique identifiers.