Local Encryption ... Why Not?
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
nope, but then again I have never used them.
Have you, in that case, seen data loss through servers being stolen?
Nope, and I don't know of any first hand experiences either.
Most burglars will have plenty on their plate stealing all of the desktops/laptops that are just lying around. It's easy to sell off laptops and desktops.. servers not so much.
Plus if your servers are behind other locked doors, it's unlikely they will continue spending time breaking into more doors again with all of the desktops/laptops around.
So don't store data on the laptops directly. If they get stolen no big deal. That's seems to get ride of most of the risk.
-
That's really the thing, when possible. I recently worked for a company that had hundreds of Macbooks (Pro and Air everywhere) and they had people breaking into their offices to steal them. It got really bad. But no one ever threatened the servers or the data, it was all about getting the hardware.
I've never heard of anyone going after full servers. Not in the financial world, not in the political world. Moving to cloud computing effectively eliminates that risk, too, especially public cloud where there is nothing physical to steal ever.
One of the things that is important to remember with medical data, is that no one wants it. There is no large market for stolen medical data. Don't get me wrong, if you can get it with low effort (remote automated hacking attempt) then yes, that data can be sold. But unlike politically or financially motivated thefts you don't have to worry about organized criminal organizations breaking down walls and moving your stuff out with trucks.
-
Remember "Scott's First Rule of Security": The key is to make data more expensive to steal than the data is valuable.
With medical data, especially something like a doctor's office rather than a research facility or big pharma, that is a low threshold and just decently securing a server will cover that.
-
The fact that HIPAA exists is kind of a counter argument to that. Fraud is one of the major reasons for the all of the concern. But I do think you're right, we have little concern that someone will break into clinic offices to steal servers to gain access to that data so they can perform fraud. They have easier ways to fraud the system today.
-
@Dashrender said:
The fact that HIPAA exists is kind of a counter argument to that. Fraud is one of the major reasons for the all of the concern. But I do think you're right, we have little concern that someone will break into clinic offices to steal servers to gain access to that data so they can perform fraud. They have easier ways to fraud the system today.
I don't agree. HIPAA covers casual exposure primarily and is designed around that. I've seen hospitals violate HIPAA because they want to grab data out of their databases to extort money from family members. Kinds of things that encryption won't protect against and big theft isn't the issue. It's getting "simple" access to "things not needed for your job."
-
It's amazing.. that whole limited access thing is something I've seen no health system actually implement.
The comment here is that every staff member who has anything to do with the medical side in one way shape or form (that includes me, the IT guy) needs to have full access to all patient information in order to do our jobs.
Frankly, I'm not sure how you build an easy to use system that limits what nurses and medical assistants can get access to, let along actual providers. Remember that near real time granted access would be a requirement in many cases.
In some health systems I've seen them try to limit who has access by requiring things like a patients SSN as proof they are somehow connected with the patient - but that just doesn't seem right to me.
-
@Dashrender said:
It's amazing.. that whole limited access thing is something I've seen no health system actually implement.
The comment here is that every staff member who has anything to do with the medical side in one way shape or form (that includes me, the IT guy) needs to have full access to all patient information in order to do our jobs.
Frankly, I'm not sure how you build an easy to use system that limits what nurses and medical assistants can get access to, let along actual providers. Remember that near real time granted access would be a requirement in many cases.
In some health systems I've seen them try to limit who has access by requiring things like a patients SSN as proof they are somehow connected with the patient - but that just doesn't seem right to me.
I agree the healthcare system, from small office to large conglomerate is ignoring a lot of this.
Which is exactly why health systems like the one in my article make it simpler by just encrypting the hard drive. Lose a machine, not an issue.
-
@scottalanmiller said:
Um, all the time. You are talking about small businesses like doctors offices. How many have generators or even good UPS? How many accidentally reset gear? This is very common. I've seen it a few times this week already. Maybe you are dealing with much bigger companies that we normally see. Anyone under a few hundred users this is a very common problem.
The ones that I deal with do not have these problems.
The servers do not reboot. (They are all on a UPSes with nice run times.) If they did (for example I had an issue recently with a printer driver rebooting the server in the middle of the day) I got a call immediately. Or I would get an alert the machine was done and call them.
The people I deal with call me, and me exclusively.
Granted, this is not on the scale that some of you deal with, so I can't speak to these other things you talk of.
-
@BRRABill said:
@Dashrender said:
It's amazing.. that whole limited access thing is something I've seen no health system actually implement.
The comment here is that every staff member who has anything to do with the medical side in one way shape or form (that includes me, the IT guy) needs to have full access to all patient information in order to do our jobs.
Frankly, I'm not sure how you build an easy to use system that limits what nurses and medical assistants can get access to, let along actual providers. Remember that near real time granted access would be a requirement in many cases.
In some health systems I've seen them try to limit who has access by requiring things like a patients SSN as proof they are somehow connected with the patient - but that just doesn't seem right to me.
I agree the healthcare system, from small office to large conglomerate is ignoring a lot of this.
Which is exactly why health systems like the one in my article make it simpler by just encrypting the hard drive. Lose a machine, not an issue.
Encrypting data doesn't prevent authorized people from accessing or using data in an unauthorized manor.
-
@Dashrender said:
It's amazing.. that whole limited access thing is something I've seen no health system actually implement.
The comment here is that every staff member who has anything to do with the medical side in one way shape or form (that includes me, the IT guy) needs to have full access to all patient information in order to do our jobs.
Frankly, I'm not sure how you build an easy to use system that limits what nurses and medical assistants can get access to, let along actual providers. Remember that near real time granted access would be a requirement in many cases.
In some health systems I've seen them try to limit who has access by requiring things like a patients SSN as proof they are somehow connected with the patient - but that just doesn't seem right to me.
It's actually insanely easy to build. Views by role is a standard security measure in any modern product. Even Spiceworks does this.
-
@BRRABill said:
@Dashrender said:
It's amazing.. that whole limited access thing is something I've seen no health system actually implement.
The comment here is that every staff member who has anything to do with the medical side in one way shape or form (that includes me, the IT guy) needs to have full access to all patient information in order to do our jobs.
Frankly, I'm not sure how you build an easy to use system that limits what nurses and medical assistants can get access to, let along actual providers. Remember that near real time granted access would be a requirement in many cases.
In some health systems I've seen them try to limit who has access by requiring things like a patients SSN as proof they are somehow connected with the patient - but that just doesn't seem right to me.
I agree the healthcare system, from small office to large conglomerate is ignoring a lot of this.
Which is exactly why health systems like the one in my article make it simpler by just encrypting the hard drive. Lose a machine, not an issue.
But it doesn't address the issues. I've never seen or heard of a HIPAA issue that this would have protected against except in cases of reckless storage of data on end points - often likely because someone was trying to put data into a precarious position.
-
@Jason said:
Encrypting data doesn't prevent authorized people from accessing or using data in an unauthorized manor.
I just looked up the breach report.
https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
It's interesting to note that a majority of the early cases were all from theft. Now they are interspersed with "unauthorized access" which if I had to bet, was due to more healthcare systems encrypting their endpoints. As we discussed, they do not look at an encrypted lost endpoint as a breach.
Are there potential holes in endpoint encryption? Sure. There are holes in anything.
Since we were discussing it, here is an article that states the OCR does not consider the loss of an encrypted endpoint a breach.
http://www.icemiller.com/MediaLibraries/icemiller.com/IceMiller/PDFs/publications/Healthcare-Protect-Confidentiality-Guide.pdf?ext=.pdf -
@scottalanmiller said:
But it doesn't address the issues. I've never seen or heard of a HIPAA issue that this would have protected against except in cases of reckless storage of data on end points - often likely because someone was trying to put data into a precarious position.
They don't need to address the issues.
People can keep working as they are used to, with the tools they need, and are protected by the encryption.
Why reinvent the entire wheel, best practice or not?
-
@BRRABill said:
@scottalanmiller said:
But it doesn't address the issues. I've never seen or heard of a HIPAA issue that this would have protected against except in cases of reckless storage of data on end points - often likely because someone was trying to put data into a precarious position.
They don't need to address the issues.
People can keep working as they are used to, with the tools they need, and are protected by the encryption.
Why reinvent the entire wheel, best practice or not?
Because that is the easiest way to steal data. It's the simplest to protect against also. The current way is about giving an image of security without actual security.
-
@BRRABill said:
@scottalanmiller said:
But it doesn't address the issues. I've never seen or heard of a HIPAA issue that this would have protected against except in cases of reckless storage of data on end points - often likely because someone was trying to put data into a precarious position.
They don't need to address the issues.
People can keep working as they are used to, with the tools they need, and are protected by the encryption.
Why reinvent the entire wheel, best practice or not?
You reinvest the wheel when the existing wheel isn't a good design. Why use the square wheel when the round one could be invested?
-
@BRRABill said:
@scottalanmiller said:
But it doesn't address the issues. I've never seen or heard of a HIPAA issue that this would have protected against except in cases of reckless storage of data on end points - often likely because someone was trying to put data into a precarious position.
They don't need to address the issues.
People can keep working as they are used to, with the tools they need, and are protected by the encryption.
Why reinvent the entire wheel, best practice or not?
Technically, encryption is reinventing the wheel. It only helps when companies are not following standard industry security practices. Not that it is uncommon, but it is the less common. The wheel exists because it is useful.
-
@Jason said:
The current way is about giving an image of security without actual security.
It still hasn't been explained to me how an encrypted hard drive is just an image of security.
-
@scottalanmiller said:
Technically, encryption is reinventing the wheel. It only helps when companies are not following standard industry security practices. Not that it is uncommon, but it is the less common. The wheel exists because it is useful.
So out of the 100% of hospitals in the US ... how many do you think are fully following best practice?
And what percentage would benefit from just encrypting their endpoints?
-
@BRRABill said:
@Jason said:
The current way is about giving an image of security without actual security.
It still hasn't been explained to me how an encrypted hard drive is just an image of security.
We've explained it quite a bit. It's not as secure as the standard "wheel". It encourages lower than normal security and makes it increasingly likely to be insecure.
-
@BRRABill said:
@scottalanmiller said:
Technically, encryption is reinventing the wheel. It only helps when companies are not following standard industry security practices. Not that it is uncommon, but it is the less common. The wheel exists because it is useful.
So out of the 100% of hospitals in the US ... how many do you think are fully following best practice?
And what percentage would benefit from just encrypting their endpoints?
Almost all, Because the majority always do things poorly.
