Slashdot Mirror


Study Finds Password Misuse In Hospitals Is 'Endemic' (securityledger.com)

chicksdaddy writes from a report via The Security Ledger: Hospitals are pretty hygienic places -- except when it comes to passwords, it seems. That's the conclusion of a recent study by researchers at Dartmouth College, the University of Pennsylvania and USC, which found that efforts to circumvent password protections are "endemic" in healthcare environments and mostly go unnoticed by hospital IT staff. The report describes what can only be described as wholesale abandonment of security best practices at hospitals and other clinical environments -- with the bad behavior being driven by necessity rather than malice. "In hospital after hospital and clinic after clinic, we find users write down passwords everywhere," the report reads. "Sticky notes form sticky stalagmites on medical devices and in medication preparation rooms. We've observed entire hospital units share a password to a medical device, where the password is taped onto the device. We found emergency room supply rooms with locked doors where the lock code was written on the door -- no one wanted to prevent a clinician from obtaining emergency supplies because they didn't remember the code." Competing priorities of clinical staff and information technology staff bear much of the blame. Specifically: IT staff and management are often focused on regulatory compliance and securing healthcare environments. They are excoriated for lapses in security that result in the theft or loss of data. Clinical staff, on the other hand, are focused on patient care and ensuring good health outcomes, said Ross Koppel, one of the authors of the report, who told The Security Ledger. Those two competing goals often clash. "IT want to be good guys. They're not out to make life miserable for the clinical staff, but they often do," he said.

198 comments

  1. Just amazing by Overzeetop · · Score: 5, Insightful

    If you forget a password, someone may die right in front of you. You can choose to write that password down and reduce security, or you can take a chance that you'll forget what this month's 12 character combination of at least two upper case, two lower case, 2 numbers, and 2 non-alphanumeric characters is in a pressure situation and the result will be death or injury to a human in your care and, likely, a lawsuit and dismissal.

    Until this is fixed, people are going to write down passwords.

    --
    Is it just my observation, or are there way too many stupid people in the world?
    1. Re:Just amazing by Anonymous Coward · · Score: 1

      There is no way to fix it. Even moving to biometric scanning will not fix it because when the scanning device breaks people will die. The right question is why these devices need security in the first place. Why are they routable from the Internet? If they aren't, why is physical security so lax that bad guys can gain access? Without physical or network access to a medical machine it's going to be fairly difficult for hackers.

    2. Re:Just amazing by Overzeetop · · Score: 3, Insightful

      Yup. These are things that, by their use, need to be fail safe rather than fail secure. And, yes, they really need to be air-gapped from the internet. But that would be inconvenient to the administrators and developers, so they prefer instead to make it inconvenient to the practitioners.

      --
      Is it just my observation, or are there way too many stupid people in the world?
    3. Re:Just amazing by Anonymous Coward · · Score: 0

      what we know about the human body and how it can fail has probably increased tens of times since the 50's, the human brain hasn't changed, so doctors need in vitro information storage. Plus more convenient and complete acces to medical records.

      I use a computer for my calendar, postal system, sketchbook etc etc, why shouldn't doctors, wherever they come from?

    4. Re:Just amazing by Anonymous Coward · · Score: 0

      How about a keyring with little keytags that have each password written on them? Then give the keyrings to the people who are supposed to be able to get into those doors.

      Hey wait, didn't there used to be an invention just like this, but completely mechanical?

    5. Re:Just amazing by Bill,+Shooter+of+Bul · · Score: 1

      Ok, we someone here who's never paid attention in a hospital. There are life saving computerized machines that doctors and nurses use to keep people alive. Since they are critical, they are pass worded. which creates this delema. Some of those have manual backups that will work, but not as well reducing good outcomes. Some just don't because computers are better at stuff than humans. And don't believe the bs on tv where doctors "Improvise" when machines fail and create their own solutions that no one has ever thought of. That never happens and would be a horrible lawsuit waiting to happen.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    6. Re:Just amazing by Anonymous Coward · · Score: 0

      We don't even ask for all that. Here I've reduced AD's password policy to two characters, no timeout. It's still a bother for the medical staff.

      Also, no, someone won't die right in front of you because of a forgotten password, except maybe in a movie. Real-life healthcare doesn't work like that. And in the case of lock codes on critical locks to be used by people unfamiliar with that lock, well, you may want to rethink that lock in the first place.

      Passwords are written down because IT is seen by users not as a tool, but as an hindrance. They resent the need for traceability and time spent in front of a screen; neither, in their opinion, is helpful for the patient nor for the staff.

      Also, they don't like, don't understand, and don't want to use IT as a whole. Most are even proud and eager to tell me that they don't understand "all that computer stuff, so it's not my fault I have to call you to open my session/print that report/find that file".

      Oh, there will be lawsuits and dismissals, but it won't be because of mistakes in pressure situations. It will be because a poor sob gave his/her password away to fifty people "so we can actually work", and someone somewhere at some point used it and mistyped a diagnosis, or a drug concentration, or accessed a file they shouldn't have access to. And then there'll be cries of "It's not my fault! Everyone knew my password, anyone could have done it!" Yeah dude, it was your fault. That's what medical responsibility is.

    7. Re: Just amazing by Anonymous Coward · · Score: 1

      What the fuck are you talking about clearly you've never worked in a hospital, it's not IT competence that is the issue the drug machine is digitally locked with biometric and password backup, I know know what to do but you physically need access the medications. Secondly the hipaa and aca mandates EMR that isn't something that was optional it was forced so all clinical data is in the computer is hard to diagnose without labs and imaging in cases.

      Source: I'm a doctor

    8. Re:Just amazing by Anonymous Coward · · Score: 0

      Yeah bullshit. I would much rather have a doctor who's willing to think and research instead of the arrogant fuck who knows it all.

    9. Re:Just amazing by MitchDev · · Score: 1

      Keycard and 4-digit pin combo.
      The "security" is getting ridiculous. Especially since when you hear about these data breaches, it all seems to be from the big companies servers, not from a regular joe 6-pack user

    10. Re:Just amazing by Anonymous Coward · · Score: 3, Insightful

      Yup. These are things that, by their use, need to be fail safe rather than fail secure. And, yes, they really need to be air-gapped from the internet. But that would be inconvenient to the administrators and developers, so they prefer instead to make it inconvenient to the practitioners.

      Wrong. I would love nothing more than to completely airgap my systems and establish secondary internet-accessible systems. That would be a huge relief to me as a clinical IT sysadmin. But *THAT* would inconvenience our clinical staff who need to check their personal webmail and google information we should be paying for, so I can't do that. Not to mention, thanks to HIPAA and the need to be able to send electronic billing and receive electronic remittance notices and be ordered to be able to check insurance eligibility, our systems MUST face the Internet.

      Next time, have a clue before you open your mouth.

    11. Re:Just amazing by Anonymous Coward · · Score: 2, Insightful

      need to be able to send electronic ..., our systems MUST face the Internet.

      Firewall whitelist

    12. Re:Just amazing by Anonymous Coward · · Score: 0

      No, you shouldn't need webmail and google information on the life safety equipment. Air gap the life safety stuff and secure the personal info systems.

    13. Re: Just amazing by Anonymous Coward · · Score: 0

      Sir, that was barely readable. I guess it's not only the scrawl. You guys need more sleep, desperately.

    14. Re:Just amazing by Anonymous Coward · · Score: 5, Interesting

      General Electrics: "Oh, we didn't tell you but we'll need a 24/7 IPSec VPN to this 500,000€ piece of equipment (and all its consoles) you just bought from us."
      Me: "What."
      General Electrics: "I know your medical imagery dept. is currently airgapped but hey, easy enough to correct, right?"
      Me: "Yeah, no, it's not that easy."
      General Electrics: "Then I'm afraid you've got a 500,000€ paperweight until you comply with our demands."

      That was last year.

    15. Re:Just amazing by Anonymous Coward · · Score: 1

      Jeebus people. Just provide some open access wifi enabled terminals for internet access.

      Keep the medical IT either stand alone (no network access at all) or wired into it's own secure network (wired access only, glue the cables in if need be, NO internet access) and provide some other free access machines for people to do personal stuff on.

      This is not rocket science and what's the cost of a small internet kiosk type machine these days ? Hell you could probably use raspberry pis running rapbian for basic, slightly slow, internet kiosk machnes.

    16. Re:Just amazing by MobyDisk · · Score: 5, Funny

      This is great, because I am on the other side of that, possibly building that 500,000€ paperweight right now!

      Security: You must provide a way to remotely update your medical devices so they aren't vulnerable to zero-day exploits!
      Me: Okay, I will turn on automatic updates.
      Regulatory: Wait! Software changes must be tested and approved first. That takes a few months.
      Customer: Our regulatory group says the lab must be air gapped.
      Everyone: *Head explodes*

    17. Re:Just amazing by EvilSS · · Score: 4, Interesting

      Heh, yea it's pretty obvious when people comment on these articles that they never tried to work with doctors (or lawyers for that matter). I've seen a department chair storm into the CEO's office of a large health care org and literally scream at him because he couldn't get to a sports website due to a new content filter. Was he fired? Reprimanded? Asked nicely to call the fuck down? Hell no. The content filter was changed after a huge shitball rolled down that hill onto the IT staff's heads.

      --
      I browse on +1 so AC's need not respond, I won't see it.
    18. Re:Just amazing by Anonymous Coward · · Score: 2, Interesting

      You don't even have to have the entire device itself air gaped from the internet, just its primary functions. Put a separate board in each device that has a NIC in it with a one way interface (only receiving data) to the actual health device (heart monitor, IV, etc). ID/Admin can secure the networked part of it to their hearts content and manufactures/bean counters/developers/monitors can still have access to the logs but the actual device functions via simple keys, with maybe a simple hospital wide password that is changed on a yearly/as needed basis just to keep some random nut from messing with the settings.

    19. Re:Just amazing by famebait · · Score: 2

      The right question is why these devices need security in the first place. Why are they routable from the Internet?

      Because they consume and produce medical information about the patient, which in turn need to be transferred to wherever the patient receives medical attention next, sometimes in a hurry.

      The clearest case of this dilemma are the boring terminals used for handling patient records: Full and unhindered access is critical to proper treatment, but they also provide just about the most hefty lump of sensitive personal data you can find.

      --
      sudo ergo sum
    20. Re:Just amazing by The-Ixian · · Score: 1

      You do realize how these breaches happen right?

      Almost every major hack you have heard about has the same vector into the network: users.

      --
      My eyes reflect the stars and a smile lights up my face.
    21. Re:Just amazing by Anonymous Coward · · Score: 0

      The local hospital has solved this to some extent. Each employee has an ID card, and all computers have a device that reads these cards. The cards are worn on a lanyard around the neck, and have a photo of the employee. I do not know the details of how the system works, but I have seen it in use.

    22. Re:Just amazing by l0n3s0m3phr34k · · Score: 4, Insightful

      This comment should be +5, not 0. A close friend of mine works in ITSEC at a major research hospital. GE is one of his major headaches; their patch cycle doesn't come close to keeping the equipment secure. You can't just install any OS you want on them; nor can you just patch them at will. All of this is FDA regulated. Change anything outside of the manufacturer's allowance and you break the certification...which breaks the "warranty", support contract, and the whole insurance liability chain. A partial solution is vlans/separate physical networks...but only hospitals with $$$ can afford this. He's lucky that his workplace is very well funded (they even paid for his CISSP certs) and he has a whole team dedicated to security. Many hospitals just do the bare "Required" parts of HIPAA, which is aimed at an office manager's simple checklist.

    23. Re:Just amazing by l0n3s0m3phr34k · · Score: 1

      Yes, the eighth layer of the OSI model: end users. The most insecure layer of them all LOL

    24. Re:Just amazing by colinrichardday · · Score: 1

      Would a data breach on a regular Joe 6-pack user's machine be newsworthy enough for us to hear about it?

    25. Re:Just amazing by tchdab1 · · Score: 3, Informative

      Add to this the great volume of doctors, interns, nurses, technicians, assistants, etc. that need access to these understaffed and overly busy places, and that come and go frequently. You arrive at a unit in the hospital and everything is password protected, all the passwords are different, and you need to get into many of them to do your job and help people in various stages of critical need. Nobody has taken the time to tell you what the common passwords are (for getting into locked rooms) or even given you your personal authorization to get at med dispensing machines, because they don't have the 15 minutes needed to do that (they'll get to this a little later when the breathing is stabilized or the pain is addressed). Don't be surprised that security is squarely in the way of getting things done, but make it easier for people to survive and be productive in this kind of environment.

    26. Re:Just amazing by MitchDev · · Score: 1

      Requiring complicated passwords they need to write down is a failure of security design.

      Network security that allows average user access to things they don't need access to is the bigger problem.

      If Joe SixPack doesn't have access to the credit card database, his account can;t be used to hack it.

    27. Re: Just amazing by Anonymous Coward · · Score: 0

      This just in - news is news - new at 10 PM

    28. Re:Just amazing by geekmux · · Score: 1

      If you forget a password, someone may die right in front of you. You can choose to write that password down and reduce security, or you can take a chance that you'll forget what this month's 12 character combination of at least two upper case, two lower case, 2 numbers, and 2 non-alphanumeric characters is in a pressure situation and the result will be death or injury to a human in your care and, likely, a lawsuit and dismissal.

      Until this is fixed, people are going to write down passwords.

      So instead of liability reform, I vote in favor of removing all door locks and all security from any medical device or hospital. In fact, that whole HIPAA security model has probably cost lives by now, so let's just get rid of that shit too.

      That way, all you have to worry about at the end of the day is when the device itself fails, or when the human operator working back-to-back 18-hour shifts makes a mistake.

      If you goal is to remove liability from the medical industry, good fucking luck.

    29. Re:Just amazing by Anonymous Coward · · Score: 0

      Yeah bullshit. I would much rather have a doctor who's willing to think and research instead of the arrogant fuck who knows it all.

      I would much rather have a doctor who's willing to think and research instead of the arrogant fuck on /. that can only specutlate as if they know it all.

    30. Re:Just amazing by Applehu+Akbar · · Score: 1

      Any hospital gear that is not airgapped should be painted some warning color, with a distinctive logo for the colorblind.

    31. Re:Just amazing by Ol+Olsoc · · Score: 1

      If you forget a password, someone may die right in front of you.

      If we didn't connect the damn things to the intertoobz, perhaps a password might not be needed at all.

      But the hospital as the proving grounds of the Internet of Things, just shows that if you need an easy password to save lives, bad guys can use that easy passwork to kill people.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    32. Re:Just amazing by EndlessNameless · · Score: 1

      If Joe SixPack doesn't have access to the credit card database, his account can;t be used to hack it.

      It's never that simple.

      An attacker will hack Joe's account because Joe was dumb enough to click a phishing email or download a trojan.

      The attacker will own Joe's machine and wait for an account with admin privileges to log on. It could be the Help Desk guys installing patches, or it could be the application account for the enterprise configuration management application. It doesn't matter, as long as it has the privileges.

      Since that admin account probably has access to all the workstations on the domain, the attacker now has admin rights to all workstations. Now he just needs to wait for a server or database admin to login somewhere so he can steal those credentials.

      It is pretty trivial to escalate from standard user to sensitive administrator accounts as long as the intrusion is not detected immediately. The only way to make it even slightly difficult is to prohibit server admins from logging into workstations across the board.

      All it takes is one lazy admin to leave it open. If one server admin account is compromised, the attacker can get onto his server(s). Since most organizations have at least one IT group or application account with access to all the servers, the attacker will be able to steal those credentials the next time they login.

      So yes, Joe SixPack can easily lead to compromised web and database servers even though he has no access himself. It is mind-boggling easy to harvest credentials from compromised machines, and most APTs employ these techniques as a standard method.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    33. Re:Just amazing by Ol+Olsoc · · Score: 1

      Not to mention, thanks to HIPAA and the need to be able to send electronic billing and receive electronic remittance notices and be ordered to be able to check insurance eligibility, our systems MUST face the Internet.

      Next time, have a clue before you open your mouth.

      Well then, y'all simply accept that you will be compromised. If doctors hace to have password1 as their password because people will die, and if there is absolutely no way that a system can be constructed without the equipment having no choice but to be on the toobz, and at the same time allow passowrd1, then you just sit back and wait for the inevitable.

      Sucks to be you, because the fickle finger of damnation is gonna point right at ya. Have you considered a job somewhere else?

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    34. Re:Just amazing by Anonymous Coward · · Score: 0

      If you forget a password, someone may die right in front of you. You can choose to write that password down and reduce security, or you can take a chance that you'll forget what this month's 12 character combination of at least two upper case, two lower case, 2 numbers, and 2 non-alphanumeric characters is in a pressure situation and the result will be death or injury to a human in your care and, likely, a lawsuit and dismissal.

      Until this is fixed, people are going to write down passwords.

      I've worked in a hospital IT department. The issue really isn't with the IT department or its rules. The issue is that the medical staff aren't trying. For an example, one of the passwords might be something as simple as the hospital initials and 4 numbers after it. You'll tell the hospital staff this password due to their forgetting their previous password, which was the exact same thing.
      After working there for a month, you start to realize it's the same staff forgetting the same password every single day.

    35. Re:Just amazing by Ol+Olsoc · · Score: 1

      The right question is why these devices need security in the first place. Why are they routable from the Internet?

      Because they consume and produce medical information about the patient, which in turn need to be transferred to wherever the patient receives medical attention next, sometimes in a hurry.

      The clearest case of this dilemma are the boring terminals used for handling patient records: Full and unhindered access is critical to proper treatment, but they also provide just about the most hefty lump of sensitive personal data you can find.

      The thing that is strange is that I've built nicely functioning systems with networking that are miles from internet access. I handle the updates via USB, and while it's possible of course to compromise an air gapped network, all of the activity is logged to let me know if anything odd is happening. Then when I need to gather the data, I sneakernet it to the computers that are on the toobz.

      And yes, I do realize that if someone really really really wanted to, they could probably get past it. But that is allowing perfect to be the enemy of really really really good.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    36. Re:Just amazing by EndlessNameless · · Score: 1

      It's called Smart Card authentication, and it is vulnerable to most of the same attacks as password-based accounts on Windows domains because the underlying security protocol is the same.

      If some random guy walks into the office, he won't be able to use passwords on stick-it notes to get into the systems. So yes, this is a small step in the right direction.

      If we're talking about a network compromise, however, the value of Smart Cards is very low. Most attackers will still steal password hashes and Kerberos credentials from compromised systems, and even SmartCard-enabled accounts have password hashes under the hood in Active Directory.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    37. Re:Just amazing by MitchDev · · Score: 1

      It is pretty trivial to escalate from standard user to sensitive administrator accounts

      And THAT is the fault of the programmers making the software and OSs....

    38. Re:Just amazing by sjames · · Score: 3, Informative

      No, the devices need to be connected to a private LAN where they can, in-turn, talk to machines that may also need to talk to the internet.

    39. Re:Just amazing by tlhIngan · · Score: 1

      If you forget a password, someone may die right in front of you. You can choose to write that password down and reduce security, or you can take a chance that you'll forget what this month's 12 character combination of at least two upper case, two lower case, 2 numbers, and 2 non-alphanumeric characters is in a pressure situation and the result will be death or injury to a human in your care and, likely, a lawsuit and dismissal.

      Until this is fixed, people are going to write down passwords.

      Then it's time to change it up.

      Authentication consists of 3 different factors - something you are, something you know, or something you have. In general, we authenticate ourselves using one of those factors - typically a password (something you know).

      "two factor" is called that because you're supposed to integrate two of those three things - typically something you know (password) and something you have (a key, token, phone with mobile authenticator, etc).

      But no one has said if you're using single-factor authentication that you must use "something you know".

      Switch it up - use "something you have" as the authentication mechanism - all hospital workers, including doctors, nurses, etc., have ID cards on them all the time, so use them for authentication. They don't just have to beep people through doors, they can unlock cabinets and computers.

      And log everything - who used their card, etc.

    40. Re:Just amazing by Chelloveck · · Score: 2

      So if there's an actual air gap between the device and the network, what zero-day exploits need to be patched? What did they do in Ye Olden Dayes before everyone and their toaster had to be connected to the net?

      --
      Chelloveck
      I give up on debugging. From now on, SIGSEGV is a feature.
    41. Re:Just amazing by I'm+New+Around+Here · · Score: 1

      Pencils are very resistant to virus attacks.

      --
      If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
    42. Re:Just amazing by clodney · · Score: 4, Informative

      Yup. These are things that, by their use, need to be fail safe rather than fail secure. And, yes, they really need to be air-gapped from the internet. But that would be inconvenient to the administrators and developers, so they prefer instead to make it inconvenient to the practitioners.

      Air gapped systems have their own problems. Embedded and dedicated systems already have a completely dismal record when it comes to getting updated, and disconnecting them from the internet only makes that problem worse. And not just security updates, but functional bugs that actually put patients at (greater) risk. And more and more complex systems have phone home capabilities for remote monitoring and proactive support, capabilities that stop working when you air gap the systems.

    43. Re: Just amazing by Anonymous Coward · · Score: 0

      Hi Khyber.

    44. Re:Just amazing by toadlife · · Score: 1

      It is pretty trivial to escalate from standard user to sensitive administrator accounts as long as the intrusion is not detected immediately.

      Please elaborate. We're talking about Windows right?

      You need admin rights to monitor keystrokes in Windows and you can't set programs to automatically run for other users without admin rights.

      In 16 years in IT, I've seen a piece of malware successfully escalate privileges once an this was a long time ago when privilege escalation exploits in Windows were much more common.

      I'm not saying it's not possible, but I think we have different definitions of "trivial."

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    45. Re:Just amazing by Anonymous Coward · · Score: 0

      As if passwords are the biggest security concern for hospitals. YAWN...

    46. Re:Just amazing by nmr_andrew · · Score: 1

      My work password rules are set/enforced by hospital IT (I don't work in the hospital, but we unfortunately share IT). The rules are basically 10 characters minimum with 2 upper, 2 lower, 1 or 2 numbers, 1 non-alpha, no embedded dictionary words, some minimum level of difference compared to your last 10 passwords, and changed every 6 months. This is why you see things written down on sticky notes.

    47. Re: Just amazing by Anonymous Coward · · Score: 0

      The network being air gapped does not mean that there are no compromised machines on the network,and infact, I'm sure I could sneak a $30 WAP into any air gapped hospital network.

    48. Re: Just amazing by Anonymous Coward · · Score: 0

      That is a lazy excuse.

      If you can not remember your passwords, write them on a card you keep in your wallet. Not a post it on the device.

    49. Re:Just amazing by Anonymous Coward · · Score: 0

      I think one issue in a hospital is that people are moving around all over the place, and remembering all the PIN's and passwords for everything in the whole place can probably be quite hard.

      There are a few way to "fix" it..

      For each door there should be:
          - a old-type key (stored somewhere safe)
          - key-pad for pin-entry (known to the administrator or similar)
          - RFID keyless system for everyone else with a personal 4 digit pin.
          - Emergency-open button next to the door. When pressed security gets a video-feed of the person and should open the door remotely if it's hospital staff + send out personnel to check what's going on.

      For computers:
        - RFID/smartcard + personal PIN to log in. No need for idiotic security-policies about changing passwords all the time.
        - If someone lost their smartcard, or if it's broken, have a "emegency" button next to the computer.. When pressed security gets a video-feed of the person and can compare the video with the photo on the person's hospital ID and could unlock it remotely. Or possibly just use another person's login.

      There are so many ways this could be handled in a good way, but it will cost a bit of money... If they lose patient-data they just blame hackers, not the security issues they do have, and they get a free pass since they follow the "industry standard security-policies regarding passwords" etc...
      Unless a kid uses one of those entry-codes and goes into some supply room and eats loads of candy-looking pills nothing will happen.

    50. Re: Just amazing by Anonymous Coward · · Score: 0

      Bullshit... the billing dept needs access to the internet... admitting needs access to the internet... the nurse in the room with the patient does NOT need access to the internet. Put a machine in the nurses station that has internet access but cannot access the patient records.

    51. Re:Just amazing by Anonymous Coward · · Score: 0

      In the old days before the PCs got Internet connections, it was sneaker net with floppy disks. Everything was more secure because there was no network, and everyone shared data on floppy disks. Just that viruses hid on floppy disks and infected PCs infected floppy disks.

    52. Re:Just amazing by torkus · · Score: 1

      You also have to take into account physical access, not just the interwebz. Drug carts, supply rooms, medical pumps, etc. all need to be protected from the patients that are in the same room/area as they are.

      Yeah, someone might remote in and hack the drug cart to open up and dispnse lots of morphine to their friend who stealths in on a fake sickness...or the junkie who goes to the ER every other week for a hot meal and a shower figures out how trivial it is to get into the cart with a a fixed punch-code or when the nurses forget to fully close it and steals 10 amules of morphine.

      --
      You can get rich if you own a politician, but you have to be rich to buy one in the first place.
    53. Re:Just amazing by slashdotwannabe · · Score: 1

      That is not an air gap, and it is no better than using a router for network segregation.

      --
      This comment is my opinion and does not represent an official position of Donald Trump or others I do not work for
    54. Re:Just amazing by Anonymous Coward · · Score: 0

      the arrogant fuck on /. that can only specutlate as if they know it all.

      You must be new here. Pretty much everyone on /. is an arrogant fuck.

      Except me, of course!

  2. what happens if someone dies by known_coward_69 · · Score: 2

    because people can't remember the password or code for that exact door or device? at some point you accept some lapse in security for the greater good

    1. Re:what happens if someone dies by beelsebob · · Score: 3, Insightful

      It's also a great example of something I've been saying for a while.

      IT needs to take much more account of what their users actually need and want. In a hospital, it reaches a really obvious head, because what the users need and want is for their patients not to die, but the same applies across pretty much every company I've worked at bar one. The IT department universally will try to bias things towards security (because thats their mandate) and will want excessive justification for anything at all that a user needs/wants to do.

      The result almost always is that users will end up going "fuck IT" and trying to find work arounds (*cough* like putting top secret emails on their own personal mail server *cough*). Seriously, I would bet big money that the only reason that Hillary had emails on her own server was because IT refused to accommodate her needing to access work somewhere other than where they deemed the correct place was.

    2. Re:what happens if someone dies by Anonymous Coward · · Score: 0

      A quick and painful lawsuit will rectify the problem. They have their uses.

    3. Re:what happens if someone dies by jon3k · · Score: 3, Insightful

      This isn't an IT problem it's a federal regulation problem. Take it up with congress. HIPAA mandates unique user IDs and passwords so that access to ePHI can tied back to a human being. Sharing passwords makes it next to impossible to guarantee you know who accessed a medical record.

    4. Re:what happens if someone dies by The-Ixian · · Score: 1

      Meh. It's a trade off issue like everything else.

      Clearly there should be no critical, time sensitive, live saving system or device with heavy security. At the same time, make sure that these systems are physically separated from the administrative network.

      On the other hand, stuff like research terminals or administrative computer systems can be locked down and require more security. I believe that these are the systems the article is talking about.

      This isn't brain surgery here.

      --
      My eyes reflect the stars and a smile lights up my face.
    5. Re:what happens if someone dies by Calydor · · Score: 2

      Please explain to the uninitiated how a lawsuit against a hospital makes the nurses magically never forget a password in a stressful situation after days of double shifts with little to no sleep.

      Perhaps we can find a way to use this magical solution without the lawsuit unless it's the lawsuit itself that is magical?

      --
      -=This sig has nothing to do with my comment. Move along now=-
    6. Re:what happens if someone dies by geekmux · · Score: 2

      It's also a great example of something I've been saying for a while.

      IT needs to take much more account of what their users actually need and want. In a hospital, it reaches a really obvious head, because what the users need and want is for their patients not to die, but the same applies across pretty much every company I've worked at bar one. The IT department universally will try to bias things towards security (because thats their mandate) and will want excessive justification for anything at all that a user needs/wants to do.

      The result almost always is that users will end up going "fuck IT" and trying to find work arounds (*cough* like putting top secret emails on their own personal mail server *cough*). Seriously, I would bet big money that the only reason that Hillary had emails on her own server was because IT refused to accommodate her needing to access work somewhere other than where they deemed the correct place was.

      Anyone doing IT Security long enough knows damn well it's a double-edged sword.

      Too much, or not enough, will hurt you. This cuts right to the bottom line these days, and speaks directly to the bean-counters, in the only language they understand.

    7. Re:what happens if someone dies by Anonymous Coward · · Score: 2, Insightful

      No. Hillary did it to avoid FOIA.

    8. Re:what happens if someone dies by EndlessNameless · · Score: 1

      IT refused to accommodate her needing to access work somewhere other than where they deemed the correct place was

      Those refusals were based on following the law.

      Federal laws dictate what constitutes a public record and how they must be retained. Virtually all outbound communications would qualify as public records, and many internal office emails will qualify as well.

      Federal laws also dictate how sensitive information is handled. This includes not only classified information, but also any electronic storage of personal information or information designated for official use only.

      Sometimes IT may slack off and deny a request when they could meet the requirement with a bit of work.

      In my experience, however, most requests are denied because there is a significant cost associated with delivering the service in a manner that complies with legal requirements. Occasionally, a request cannot be fulfilled legally at all. But mostly it is possible, just very expensive---and upper management decides not to allow it.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    9. Re: what happens if someone dies by Anonymous Coward · · Score: 0

      Well, paying enough to have sufficient staff that double shifts and sleep deprivation are not assumed as necessary solves it. So if the hospital funds things properly it doesnt require magic.

      Good, fast, cheap. Pick two. They certainly didn't pick cheap when I see biils, so I expect good and fast, or they should expect to be held liable.

    10. Re:what happens if someone dies by torkus · · Score: 1

      Part of it is the fact that there are so many independent data points to remember. In theory SSO-type mechanisms would work but in reality there's a different code, password, PIN, and combination for any number of things.

      I work outside of the medical field and we've implemented SSO for quite a few things...and there's still a dozen accounts the typical user needs to know and remember. It basically falls under "yeah SSO for everything...but hey here's this new tool/site/app that you need for some other critical function and it doesn't integrate with our SSO" Oops...

      --
      You can get rich if you own a politician, but you have to be rich to buy one in the first place.
  3. I would have thought by Anonymous Coward · · Score: 0

    In a hospital, misuse would be epidemic.

  4. Friday Friday by Anonymous Coward · · Score: 0

    Gotta get down on Friday

  5. Recent = 2014 by Anonymous Coward · · Score: 0

    Click to the actual article.
    Click to the link to the actual study.
    Check out the properties on the PDF. It was created in 2014.

    Time for a new study.

    1. Re:Recent = 2014 by geekmux · · Score: 1

      Click to the actual article. Click to the link to the actual study. Check out the properties on the PDF. It was created in 2014.

      Time for a new study.

      To tell us what? That users in 2016 still tape their fucking passwords everywhere in plain sight?

      Pull a study from 20 years ago and tell me if it's any fucking different than the one you're complaining about from 2 years ago. Humans have not changed regardless of the threat landscape. Anyone doing this long enough knows this has been a systemic problem since passwords were invented.

  6. Yep by Anonymous Coward · · Score: 0

    At my doctor's office they have the passwords taped to the computers.

    1. Re:Yep by Anonymous Coward · · Score: 0

      In my home office I have a password taped to my monitor. If you can break into my house, you now have access to my computer.

  7. It's not just in Healthcare by Dust038 · · Score: 3, Informative

    Having been in the trenches for a number of years, it isn't just heathcare where password misuse is 'Endemic' I am not sure how paywalled this article is but this here: ~~ "Those two, competing goals often clash. “IT want to be good guys. They’re not out to make life miserable for the clinical staff, but they often do,” he said." ~~ I've been in their shoes, and at the next HIPAA Compliance check they are doomed with IT taking most of the blame. We can only advise them in the end to follow best practice. Anyone have an article about a doctor being fired for password misuse and not IT? Just my 2 cents.

  8. "Patient Care" trumps all by Anonymous Coward · · Score: 0

    In healthcare, "impact on patient care" trumps essentially everything else. Do you really want to be the CIO who has to explain that a patient died because providers couldn't quickly access medication or supplies?

    It's a constant battle to find the right balance between security best practices, regulatory compliance, and providers revolting...

    1. Re:"Patient Care" trumps all by Anonymous Coward · · Score: 0

      "In healthcare, "impact on patient care" SHOULD TRUMP essentially everything else"

      Fixed that for you, in reality I think regulations play an uncomfortably significant role in patient care (well, that and understandably cost). I think some studies have shown that due to HIPAA requirements some administrative tasks have tripled in the amount of time that needs to be spent to stay in compliance. Where necessary for patient care it is understandable, but something tells me that a majority of it is just record keeping bureaucratic nonsense. If you google images "healthcare industry administrative percentage" its pretty telling that the administrator to physician ratio has skyrocketed since the 90s.

  9. Two failure modes by Geoffrey.landis · · Score: 4, Insightful

    Let me remind everyone here that there are always two failure modes of a simple component, type 1 and type 2. A switch can fail open-circuit or short-circuit; a lock can fail locked or open, and a password failure can be either "will let people in who shouldn't be allowed to get in" or "won't let people in who need to get in".

    You can alway take one failure rate to zero by making the other failure rate 100%. Reducing the rate of type 1 errors tends to increase the rate of type 2 errors, and vice versa.

    Basically, the hospital workers are voting "there are too many errors of the type "can't get in when we need to", and we need a work-around to prevent this."

    --
    http://www.geoffreylandis.com
  10. It's not un-noticed by IT, it's rejected. by Anonymous Coward · · Score: 0

    I worked for a multiple-doctor location, and ALL use the same password, and the doctors tell the nurses they can't change their password. The nurses have the doctor's passwords in the EMR system and prescribe things to patients and fill out the doctor's paperwork. You push for change, stating it's against HIPAA policy and will get them in trouble, they act as if you're a fool for even suggesting it. 26 doctors I answered to, and they all felt entitled to have the nurses do everything for them except talk to or cut on the patient...

    It's all asinine. I have a whole new perspective of the medical industry; I find it both laughable and horrifying.

    -Systems Admin

    1. Re:It's not un-noticed by IT, it's rejected. by silas_moeckel · · Score: 1

      Sounds more like a broken system. Why shouldn't a doctor be able to verbally tell a nurse something and have them enter the data? An RN is required to know a lot about meds they are supposed to be the last line of defence to catch screwups. The system would be better if they use their own credentials and select what doc they are doing it for. Do you realy think a doctor is getting out a prescription pad in the ER no they tell a nurse they do it and chart it.

      Oh yea idiocy around the drug war.

      --
      No sir I dont like it.
    2. Re:It's not un-noticed by IT, it's rejected. by Anonymous Coward · · Score: 0

      Why shouldn't a doctor be able to verbally tell a nurse something and have them enter the data? An RN

      An RN? LOL.

      I've got doctors who give their cellphones to their MAs so they can do the 2FA thing because the doctor can't be bothered with typing in (or clicking on a picklist) the Vicodin prescription in the patient's chart themselves. I've got another one that flipped their shit because they're failing the CPOE (computerized PROVIDER order entry) rules because they can't be bothered to check a box to order a lab on a patient. The medical assistant "knows" what labs he wants done, he doesn't need to be bothered with documenting them and the government shouldn't penalize him for that.

    3. Re:It's not un-noticed by IT, it's rejected. by Anonymous Coward · · Score: 0

      I find the best thing in those situations is to find another job, wait 6 months, file a HIPAA Violation complaint with health and human services and let them get the fined to hell and back. I'm getting ready to do this to a doctor over a 6month billing dispute that is still uncorrected.

  11. Researchers Ignore Real World Concerns Yet Again by Anonymous Coward · · Score: 0

    As usual, security people always think that security is the only thing that matters. And they also like to blame these 'bad practices' on the users instead of bad security policies. Patient care and ensuring good health outcome absolutely SHOULD be a higher priority considering that they are the entire point of a hospital. Biometrics or maybe smartcards are probably a far better solution for hospitals anyway, especially if the current situation requires everyone to remember a large number of passwords (written down passwords everywhere are an obvious outcome of this approach).

  12. What this means is... by Anonymous Coward · · Score: 0

    ... that "security" is still mostly a mindfap for "tech"* and not at all even close to the needs of the users.

    Then again, much of end user computing in general is this. Even "GUI" falls under this, as a matter of fact. Reasons why cruelly left as an exercise.

    * Driven by a mixture of the usual tech neophily and "clever" sales and marketeering.

  13. Just a thought.... by Squatting_Dog · · Score: 1

    Security is important - that we all know. But, there must be a compromise between asset protection/control and unhindered availability. In a crisis, I wouldn't want my nurse/doctor getting the code to the drug cabinet confused with how many cc's/mg's or whatever is supposed to go into the shot that I'm about to get! Maybe biometrics would be a better alternative?

    1. Re:Just a thought.... by Anonymous Coward · · Score: 0

      Biometrics would be a foolish choice for a hospital (blood, glasses, gloves, disease, etc). Some kind of contactless (bar code, RFID) watch, badge, etc should provide enough security while maintaining sterile conditions. However these security considerations should always take a back seat to patient care necessitating some kind of override of the whole system where necessary. A nurse doesn't need to be hunting down a specific doctor after a bus crash turns the hospital into a zoo to get rights to administer some low level medication.

  14. feels familiar here. you can easily fix it. by nimbius · · Score: 4, Informative

    I work in an analytical simulation lab, and as a sysadmin these guys are notorious for sharing their passwords either out of an inability to understand unix file permissions or out of callous disregard. I was told when I joined that "this is just how it is" and that kind of management level complacency is what i think drove it all.

    my solution was 3 fold. First, I expired everyones password. Next, departments are restricted to their specific laptops and workstations. Analytics should not be logging into design workstations, or vice versa. And finally, yubikey for anyone who needs access to finite elements or VPN, or simulator hardware that runs in a test chamber. The whole thing required serious management buy-in, which was easily the hardest part. It also required me to train users on posix permissions and how to properly collaborate in a unix-like environment, which for most newer college grads was completely foreign. greybeards in the labs were a huge help here.

    --
    Good people go to bed earlier.
  15. Security that gets in the way doesn't work by Opportunist · · Score: 5, Insightful

    Security that gets into the way of the worker to the point where it hinders him in his actual work will be circumvented without remorse. Actually, it will be done with the justification of increasing productivity. An example:

    Take a security door that MUST be closed all the time for security reasons because something valuable is stored behind that door. Now take a worker that has to haul heavy items through that door. The prescribed flow of operation would be that he unlocks the door, goes through it, locks the door behind him, picks up whatever heavy item he has to haul, puts it down at the door, unlocks the door, opens the door, carries the heavy item through, puts it back down, closes the door, locks the door and then carries the heavy item to its destination.

    How many times do you think he'll do this before that door is wedged open?

    To him, that door is a nuisance and, worse, it is something that lowers his productivity and, in his opinion because he does not know the other implications, hurts his company. It isn't something he does for personal gain where he'd hurt his company, like checking his Facebook page on company time or watching YouTube videos, something he would at least feel guilty for, it is something he does FOR the company because it means he can work faster.

    That is by some margin the worst kind of security infraction because it is done without remorse and with a good justification.

    How much more likely is something in a health related area where the justification can well be saving someone's life?

    This is why you have to plan your security in such a way that it does not impede the workflow of your workers more than absolutely necessary. Yes, that means you have to actually do your fucking job as a CISO and not just spout some insane and harebrained password requirements that force everyone to write it down 'cause they cannot remember them. You have to find out how to automatize away security from your workers. Perfect security isn't one where your workers stumble upon it every single time they want to do it, perfect security is achieved if the worker doesn't even interact with it anymore and hence CANNOT fuck it up, neither deliberately nor accidentally.

    The aforementioned door could be made secure without causing your worker additional stress simply by giving him a RFID token and the door opening if it is being scanned. If you want to make theft of the token unlikely, activate it when the worker signs in in the morning (using the RFID token and a pin key, so someone stealing the RFID token would not know the pin) and deactivate it when he leaves. This is trivially possible and if whatever you have to secure is so important, the cost for implementing this are negligible as well.

    But you have to do it. Instead of just offloading the burden of security onto your workers.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    1. Re:Security that gets in the way doesn't work by Anonymous Coward · · Score: 0

      My belief is there's three factors to encouraging employees to follow security practices. Education. Sometimes the circumvention is due to misunderstanding the capabilities of an application and how it works. Enfranchisement. The users don't fully understand what could happen if other people are using their credentials and how they could be blamed for what happens. Ease of Use. If the method isn't easy enough to use that's going to prompt circumvention.

    2. Re:Security that gets in the way doesn't work by Opportunist · · Score: 1

      Well, I can talk from over 10 years of experience in IT security and in the end, ease of use trumps all.

      People are first and foremost concerned with getting their job done (let's assume for a moment that they actually care about their job and don't just want to make the time go by so they can go home). And they will actually try to streamline and improve the way their job is done if they're good. Security will eventually get into their way.

      Yes, education does help, as does raising awareness of the implications of security infractions and why those security guards are in place. But in the end, what matters to people is getting the job done. If security can be upheld, fine, if security gets in the way, it's out the window.

      People don't do that to make your life as a security officer difficult or to spite you, far from it. They may even be very security conscious. But getting the job done comes first. All the time.

      Your job as a security officer is to take that burden off them, to keep them secure and build security so around them that they can do their job with the least possible obstacles, preferably without any. This is what a good CISO will do. And yes, that is possible.

      The reason why it's so rarely done is simply that the CISO will have to duke it out with the CFO because such measures are usually not free. And few CISOs have the in-company muscle to stand up against the CFO unless security is a big deal.

      But we're getting there. Give it time.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  16. That assumes the IT staff has time. . . by Salgak1 · · Score: 3, Informative

    . . . .to worry about passwords. Both my daughters work at the local hospital, a regional medical center. ~450 beds. 5000+ employees.

    IT Shop ? 3 people. They're too busy putting out brush-fires to even THINK about more than out-of-the-box configs. It's to the point that both daughters (one is a ward admin, the other a radiology trainee ) spend about a third of the time as de-facto frontline IT Techs.

    I rather suspect it's not an isolated case. . .

    1. Re:That assumes the IT staff has time. . . by Anonymous Coward · · Score: 0

      This. I was thinking the same thing. Does the hospital have the IT staff necessary to reset passwords for x% of the office each day? Are these password such that the request can linger or must it be done ASAP? How are off hours handled?

      I'm imagining strecthes of time where if a user doesn't remember their password they are SOL for a few hours at least. Of course people are going to use stickies.

  17. Working with DHS components by wiredog · · Score: 2

    DHS being the Defense Health Service of the DoD. Someone had the brilliant idea of requiring the use of CACs (ID cards) to log in to terminals used by military medical personnel worldwide. This would satisfy the HIPAA requirements, keep Security happy, make it easy to log who was seeing what, and generally be a Good Thing.

    Then it was pointed out that using a CAC for login required a connection to validation servers. And field hospitals in Afghanistan, Iraq, and other places generating lots of patients might not have good connections... Oh, and Navy ships at (and especially under) sea can also lack good connectivity.

    Amazingly, the Powers That Be agreed that the Idea, while Good, was not practical, so using the CAC is now recommended rather than required.

    1. Re: Working with DHS components by Anonymous Coward · · Score: 0

      You want a good VA story with how stupid chip cards with built-in keyboards are. Well at the VA they disable new USB devices on the computers as a security measure, they also have keyboard with built in readers, however the cards can only hold 1 set of cards and if the card is removed the computer locks but what happens if you need admin rights week they don't put those on the card the IT people have a separate admin card however they can't login with it but if you remove your login card the computer locks so they bought a second card reader for EVERY computer at the VA so that the admin card can used when needed.. that's some fucked up waste. Don't get me started on the 1 month account lock if your away and that no one can unlock your account until 830 am only on weekdays since they don't work at night.

    2. Re:Working with DHS components by Anonymous Coward · · Score: 0

      Wouldn't using passwords encounter the same issue? They still need to be validated. But I think that is unrelated to this article because they are standalone devices with unique passwords.

    3. Re:Working with DHS components by Anonymous Coward · · Score: 0

      Each naval vessel could have a local copy of the CAC DB updated when it docks or surfaces as conditions warrant.

    4. Re:Working with DHS components by EndlessNameless · · Score: 1

      Then it was pointed out that using a CAC for login required a connection to validation servers.

      Not continuously.

      They could download the CRLs from each certificate authority once a day and distribute them to the authentication servers (Windows domain controllers, most likely).

      There are tools to automate this process, and they can be scheduled for off hours and to retry in the event of a network outage.

      Obviously, there are grounds for an exception where internet connectivity goes down for days at time, but even then you could configure the system to skip validation. (Skipping validation still means the user has a legitimate certificate---it just does not check to see if has been revoked since the time it was created.)

      The domain admin should be capable of disabling validation in under five minutes. Users could also unplug the network cable and log in with cached credentials.

      The only permanent exception might be submarines, where they are routinely expected to go without network connectivity for days at a time. Even then, they could just disable validation. It's not like the Chinese Unit 61398 guys are going to steal a sailor's CAC while his sub is underway.

      So, basically, they could require smart card authentication in those places---if they have the forethought to provide proper training and permissions in advance.

      Even without validation, smart cards are probably more secure than passwords. Especially if people write down or share passwords.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    5. Re: Working with DHS components by EndlessNameless · · Score: 1

      at the VA they disable new USB devices on the computers as a security measure

      Disabling USB ports is stupid.

      A lot of crap gets spread on USB drives, so I'm not surprised if those are locked down.

      if you remove your login card the computer locks

      This prevents unauthorized people from accessing unattended computers. This is the same reason that the computer locks if you don't use it for 10-15 minutes.

      Locking user sessions is basic security, and if you don't understand that then I'm not surprised if no one listens to your complaints.

      so they bought a second card reader for EVERY computer at the VA so that the admin card can used when needed.. that's some fucked up waste

      Smart card readers are around $20, so it's trivial compared to the cost of the computer (or even compared to the cost of other security measures).

      One of the companies I worked for had smart card authentication, and they supplied multiple readers to support alternate credentials.

      Yes, they could provide extra readers only to IT staffers. But they're more likely to get broken if people are carrying them around all day while they work. It is simpler and possibly cheaper in the long run to just have one sitting at each workstation, where it will generally be left alone until it is used. Smart card readers are cheap, but they are not particularly durable.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    6. Re:Working with DHS components by MercTech · · Score: 1

      Local cache of commonly used login profiles would solve the problem of needing validation servers. Log in once with net access on the computer then your card will get you in thereafter. This is an often used technique for company issue laptop computers. Log in once while connected to the corp. network then you can access that laptop while traveling until the password expires. (Last time I drew one for a field job; the password authentication was good for 90 days. The expiry date could be whatever I suppose.)

      --
      NRRPT/RCT
    7. Re:Working with DHS components by EndlessNameless · · Score: 1

      Cached logons ignore password expiration. They should be able to login indefinitely.

      Domain accounts rely on the password expiration date stored in Active Directory, but the LSA subsystem enforces the policy locally when it authenticates via a domain controller. If the LSA falls backs to cached credentials, there is no expiration data and thus no enforcement.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
  18. It's not just emergencies by Anonymous Coward · · Score: 2, Informative

    My wife is a practitioner and she constantly complains how when she's with a patient, the system locks her out and demands a password change - which can take several minutes because they have this cloud EMR shit that's hosted across the country and is slower than shit.

    Or just having the system time out fast. She's with a patient listening to their health complaints and examining them and then the system times-out and she has to log in again - and go through the obscene obstacle course of a UI to get back where she needs to be.

    Of the jobs she's had and my experience in that environment, I have yet to see a medical system that has the practitioner in mind. As my doctor says, "These things are written for the insurance companies and many times make no sense to us."

    1. Re:It's not just emergencies by The-Ixian · · Score: 1

      [...] is slower than shit.

      Try eating fiber. No more slow shit.

      It is fun to hear people complain about technology.

      If there is one thing I have learned, it is that people like to complain and they LOVE to complain about technology.

      You could address all of these concerns and the next thing out of the user's mouth will be "the text is hard to read" or "the color scheme hurts my eyes" or any number of other asinine things.

      --
      My eyes reflect the stars and a smile lights up my face.
    2. Re:It's not just emergencies by sabri · · Score: 2

      Try eating fiber. No more slow shit.

      It's not about fiber. If you have Netflix, go find "Code Black". It's a documentary about a group of ER doctors, and of of the things that stand out is their move to a "HIPAA compliant" hospital. One of the doctors can be quoted saying something like "if I use the restroom, I want to login. Login Login Login everywhere". Sure, HIPAA keeps patient records safe. But what use is that to the patient if he's dead? I'd rather be alive and have my records slightly less safe than being dead but knowing for sure that nobody knows I had a heart attack.

      Also, your fiber is not going to fix it. Yes, fiber will lower the latency on the physical transmission. However, you fail to take into account that you still need a datacenter with computing power (since "the cloud" is nothing more than a computer elsewhere). And that's where you'll see most of the latency coming from.

      But seriously, watch "Code Black" if you're bored. It's an excellent documentary.

      --
      I'm not a complete idiot... Some parts are missing.
    3. Re:It's not just emergencies by Anonymous Coward · · Score: 0

      That's because HIPAA was not designed to keep patient records and privacy safe. It was very explicitly designed so that consumers and practitioners would eventually go "Fine! Fuck it! do what you want with our data, just let us actually do our jobs!" and we're back to being bought and sold like pigs in the marketplace.

  19. Re:Researchers Ignore Real World Concerns Yet Agai by silas_moeckel · · Score: 1

    Biometrics in a hospital setting are hard lots of gloves lots of issue with sterilization. Contactless is pretty easy the problem is you have upteen vendors that do not work with it. It's a case where you need something like HIPPA or similar to require it vs a nebulous you should follow good standards to get all the suppliers to get working with a standard.

    --
    No sir I dont like it.
  20. Govt is just as bad by coolmoe2 · · Score: 1

    If you could go into any govt office and look around its just as bad with post it notes with all kinds of login information everywhere. What I don't get is when looking at these they look like they have been put there since the beginning of time. Now I don't know about most of you but if I typed the same login information in for decades the last thing I need is a post it note. So no im not buying this "we cant have passwords and save lives" bullshit because it happens in office settings were no lives are at risk and still see the same lazy ass attitudes towards security. Call me an IT nazi but I would tear them all down and the first person that put up a post it note with login information on it would be immediately fired. Im sure if you fire a few of the worst offenders that others would catch on that this is no longer acceptable.

    1. Re:Govt is just as bad by jratcliffe · · Score: 1

      Fine, but if there are half a dozen systems that someone needs to use, each with a different login, and each with different password requirements, and each requires changing the password every month, that becomes a non-trivial problem.

      "OK, this is the one where I have to use a password with at least ten characters, including two numbers, a capital letter, a symbol, and no actual words - is it W34@wqaszn? No? Maybe that was last month?"

    2. Re:Govt is just as bad by Anonymous Coward · · Score: 0

      Except security is not considered part of their job and not what their paid for. Everyone now tries to maximize the money they make and specialize, but no one gets any benefit of how well they follow the rules and how well they fit into an organization. The expectations of the healtcare professionals are to be great at saving lives - they will generally be punished by following the rules because they will have to spend a bunch of time learning the rules, memorizing passwords, conforming to procedures, all these things take their time and they are already max'ed out doing important work (because we stretch everyone so far and understaff everything).

  21. there's a reason military humvee don't have keys. by Anonymous Coward · · Score: 0

    most hospital devices should NEVER require a password for physical access and use.

  22. No time... by Anonymous Coward · · Score: 0

    To remember passwords, I have lives to save!

    Captcha: Predict

  23. Missing component not being discussed by Anonymous Coward · · Score: 0

    Shouldn't the expectation of privacy / security also be discussed?
    Everyone should have an expectation of privacy, however, is such a potentially chaotic setting, should we still have such strict restrictions? Shouldn't the individual have to accept some risk to his privacy in such a setting when taking advantage of it?

    Perhaps the restrictions themselves should have some language that would only punish those that are negligent with the patient's privacy - allowing IT to relax their restrictions somewhat and explore other mechanisms to increase privacy but allow for action to be taken when needed. (ex. general staff awareness of privacy / security requirements)

    Thoughts?

  24. This Weeks Weak Password for the Hospital is.... by Anonymous Coward · · Score: 0

    The Password is...

    AntiBioticResistant.

  25. Wrong way to write down passwords by gurps_npc · · Score: 3, Interesting

    There is a right way and a wrong way to do this. In my experience, all the hospitals do it the wrong way - which is to write down the actual password.

    The correct way to do it is simple, right down a password that is systematically wrong.

    If the password is 845, write down 734.
    If the password is EmerC@rE, write down eMERc2Re, or perhaps R,rV#tR (check your keyboard).

    simple cryptography works fine.

    --
    excitingthingstodo.blogspot.com
    1. Re:Wrong way to write down passwords by Anonymous Coward · · Score: 0

      I do the same - needing to Add one - but I think SUBTRACTING ONE is better

      0123456789 -> 9012345678

    2. Re:Wrong way to write down passwords by Registered+Coward+v2 · · Score: 1

      There is a right way and a wrong way to do this. In my experience, all the hospitals do it the wrong way - which is to write down the actual password.

      The correct way to do it is simple, right down a password that is systematically wrong.

      If the password is 845, write down 734. If the password is EmerC@rE, write down eMERc2Re, or perhaps R,rV#tR (check your keyboard).

      simple cryptography works fine.

      A corrollary would be to have two passwords stored in the system, the real one and the memory jogger. If someone enters the memory jogger you know an intrusion may have be attempted and can lock the system and warn the ser the next time they log on.

      --
      I'm a consultant - I convert gibberish into cash-flow.
    3. Re:Wrong way to write down passwords by geekmux · · Score: 3, Insightful

      There is a right way and a wrong way to do this. In my experience, all the hospitals do it the wrong way - which is to write down the actual password.

      The correct way to do it is simple, right down a password that is systematically wrong.

      If the password is 845, write down 734. If the password is EmerC@rE, write down eMERc2Re, or perhaps R,rV#tR (check your keyboard).

      simple cryptography works fine.

      Holy SHIT do you overestimate the average human's ability to understand even simple obscurity models.

      Feel free to provide examples of where this has actually worked for people outside of IT.

    4. Re:Wrong way to write down passwords by ljw1004 · · Score: 1

      In my experience, all the hospitals do it the wrong way - which is to write down the actual password. The correct way to do it is simple, right down a password that is systematically wrong. If the password is 845, write down 734.
      If the password is EmerC@rE, write down eMERc2Re, or perhaps R,rV#tR (check your keyboard). simple cryptography works fine.

      Sure, great idea. That way you'll have two post-it notes stuck on the monitor:
      * "password is 734
      * "add 1 to each digit to get real password"

      What actual threat model do you imagine anyway? Which danger model is more likely? (1) That a clinician forgets a password or the password sticky note convention and so care is delayed by several hours while it gets restored? (2) Or a new clinician comes to the shift and doesn't know the convention and care is delayed? (3) Or an electronic attacker tries to get into the medical systems via remote access? (4) Or an electronic attacker tries to get into the system via local access?

      Your solution would guard against (4) at the cost of (1,2) and without impacting (3).

      Read the article. It says "the health IT itself can undermine the central mission of the clinician: serving patients". Your idea

    5. Re:Wrong way to write down passwords by painandgreed · · Score: 1

      There is a right way and a wrong way to do this. In my experience, all the hospitals do it the wrong way - which is to write down the actual password.

      The correct way to do it is simple, right down a password that is systematically wrong.

      If the password is 845, write down 734. If the password is EmerC@rE, write down eMERc2Re, or perhaps R,rV#tR (check your keyboard).

      simple cryptography works fine.

      Except that the many of the people who are writing it down are the people who have issues getting it correct even when written down correctly, mostly older doctors and staff. The rest are people who have so many passwords for som many systems that are used so seldomly, that they can't remember them. This would include what their system of cryptography is too. Add in that many of these systems are vendor controlled and they all have different constraints on how passwords can be created so that any such system would be about as complicated as just remembering the things in the first place.

    6. Re:Wrong way to write down passwords by antdude · · Score: 1

      They won't remember that method.

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
  26. use hardware !!! by Anonymous Coward · · Score: 0

    Sounds like the perfect place to implement biometric security measures,a simple self cleaning finger print scanner seems ideal for this situation..

    1. Re:use hardware !!! by famebait · · Score: 1

      See, hospitals are full of squishy biology stuff, some of it really bad, some of it really vital, so when there is a real crisis and you need that information more urgently than ever, your hands may well be covered in any combination of gloves, bodily fluids, and medicinal gunk.

      --
      sudo ergo sum
  27. Passwords are the biggest failure in technology by zerofoo · · Score: 4, Insightful

    The fact that we IT professionals have not come up with a universal replacement for passwords is the IT industry's biggest failure in my lifetime.

    Security professionals cannot simply demand that business stops when security policies are not met. IT security and policies should support the mission of the organization - not the other way around.

    1. Re:Passwords are the biggest failure in technology by Anonymous Coward · · Score: 0

      IT security and policies should support the mission of the organization - not the other way around.

      Mission of the organization should include not having all your customer data stolen from you.

    2. Re:Passwords are the biggest failure in technology by Moof123 · · Score: 1

      +1, Wish I had mod points.

      Passwords in general have been obsolete for years, but not replaced. Password policies have made this worse. I have 4 different passwords and a chip card at work alone (WTF?). Dozens of websites want passwords, many of which I only need to access monthly or yearly. Many have policies that get in the way of good password practices (many have very short character limits, which is stupid beyond belief). So I readily admit I reuse the same burner password and login for many low importance sites rather than having to reset my accounts every month or three when I need access. We need better, but usually just resort to vilifying the beleaguered users who get compromised.

    3. Re:Passwords are the biggest failure in technology by EndlessNameless · · Score: 1

      IT security and policies should support the mission of the organization - not the other way around.

      This is a useless generalization.

      Since most businesses do not want their trade secrets or contract information stolen, they need IT security.

      Since most businesses are obliged to protect personal information or other sensitive information, they need IT security.

      The value of various protections should determine how much they spend to implement security, and the potential for lost productivity should determine how much is spent on streamlining procedures and deploying enterprise tools. Most of those assessments come from upper management.

      I've worked at some mid-sized and larger enterprises, and very rarely are the security measures stupid or wasteful in the larger organizations. They usually hire good people or pay for good consultants.

      There is more room for stupidity to take root at smaller offices where IT is not subject to the cost analysis or external auditing.

      The fact that we IT professionals have not come up with a universal replacement for passwords is the IT industry's biggest failure in my lifetime.

      There are a variety of alternatives because the security needs of organizations vary. Passwords have always been the lowest common denominator in terms of security.

      Some places still use passwords. Others use smart cards, and yet others use RSA tokens as multi-factor supplements to passwords.

      Passwords were a universal security measure because they were fast and cheap to implement. They failed when computational capacity inevitably exceeded basic human memory capacity.

      The alternatives are not universal because they are more expensive, and they involve different trade-offs in terms of upfront investment, infrastructure requirements, overhead, and operational costs.

      You are basically saying there is a failure because there is no one-size-fits-all solution. You need to move beyond that and realize that everything more secure than a password is also more expensive and complicated. There is no way to avoid that, so every organization will need to assess the alternatives and make an intelligent decision.

      Security professionals cannot simply demand that business stops when security policies are not met.

      A lot of times, the outcry to "stop doing X" does not mean the business should stop performing one of its functions entirely. It usually means we need to figure out how to replace insecure procedure X with secure procedure Y.

      While I'm sure some places have moronic IT staff, practically no one expects essential operations to halt. You can't get more than the basic security certifications without being reminded that business needs and continuity of operations are essential considerations in forming IT policies.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
  28. Go ahead by Sir_Eptishous · · Score: 1

    For starters, go ahead with your weak rationalizations about why any of these critical devices need to be on a network that is also connected to the Internet.
    Go ahead...

    --
    We play the game with the bravery of being out of range
    1. Re:Go ahead by LordWabbit2 · · Score: 1
      From an AC post further up

      General Electrics: "Oh, we didn't tell you but we'll need a 24/7 IPSec VPN to this 500,000€ piece of equipment (and all its consoles) you just bought from us." Me: "What." General Electrics: "I know your medical imagery dept. is currently airgapped but hey, easy enough to correct, right?" Me: "Yeah, no, it's not that easy." General Electrics: "Then I'm afraid you've got a 500,000€ paperweight until you comply with our demands." That was last year.

      They should just replace all passwords with biometric sensors. I'm in a third world country and a company I worked at before put biometric sensors EVERYWHERE, log into your PC, go through a door they want to restrict access to, unlock a till at one of their branches etc. etc.
      They are cheap enough nowadays to make them a viable alternative.

      --
      There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
    2. Re:Go ahead by Sir_Eptishous · · Score: 2

      Yea, I work at a lab, and a few of our instruments now need to be constantly connected to phone home.
      There is no rationale for this. Just more of the clouded thinking that we now have to live with.

      It's going to be a rough ride when the IoT gets going, with how weak it's "security" is.
      Imagine when "everything" is on a network, with little to no thought about security...

      --
      We play the game with the bravery of being out of range
    3. Re:Go ahead by Anonymous Coward · · Score: 0

      Then, we keep the exact same system we have been using since 1990!

      Bravo, bravo!!

    4. Re:Go ahead by LordWabbit2 · · Score: 1

      Or stop being fvcking stupid and build better security in, we ALREADY know it's a problem, the slow ass law machine should catch up and start penalizing companies who have crappy security NOW, before there are another million unprotected devices. I will wager that it's going to take a couple of high profile deaths before they do anything.

      --
      There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
  29. Apply security where it makes sense by MobyDisk · · Score: 3, Funny

    There are some places where security just isn't needed. Where I work we are having discussions kinda like this:

    Security team: All new products must support two-factor authentication!
    Development: On the juke box??

    1. Re:Apply security where it makes sense by Anonymous Coward · · Score: 0

      Is the jukebox connected to the Internet, and can it be hacked and added to a botnet?

    2. Re:Apply security where it makes sense by MobyDisk · · Score: 1

      It doesn't matter. If you added 2-factor authentication to the juke box, nobody would buy it because it would be too hard to use. Which, I suppose, solves the security problem nicely!

    3. Re:Apply security where it makes sense by Anonymous Coward · · Score: 0

      Or the hypodermic needle or the blood-pressure cuff or the stethoscope. How did medicine make it out of the dark ages without password-protected leeches?

    4. Re:Apply security where it makes sense by MercTech · · Score: 1

      Want to see IT cringe? Let them know you have to implement kiosk computers that have a generic password and only run a specific software package. Or, need a generic password for anyone at all to access a database. These are real world issues.

      When they put all the Material Safety Data Sheets online; IT forgot that you have to have them available for temp. contractors that otherwise have NO computer access, Wanting temp. workers to "stop the job" and proceed to a house employee supervisor to get a printed copy of the MSDS for the chemicals they are using gets to a study in total insanity when you have over a thousand temp workers for a project. Generic "MSDS password" and it is a non-problem.

      Automation is a good thing but scares network security personnel. The automatic flow path,.,.,. worker scans his badge, scans his work package number, scans is legal record dosimeter, inserts an electronic dosimeter on the proximity programmer, Once prompted by the software; he picks up his dosimeter and proceeds to do a nuclear job package. Imagine what it was like when a new "Head of Information Security" mandated that everyone has to have a unique identifying password. Yup, watch the shit show trying to process a couple of hundred workers into a controlled zone when each and every one has to log in and log out. 48 hours later, we had generic passwords for the kiosk log in computers.

      --
      NRRPT/RCT
  30. Maybe interesting.Can you write that in sentences? by raymorris · · Score: 0

    What you just tried to say might be interesting. Can you try writing it as sentences rather than words in seemingly random order with commas inserted at random? Then readers can know what you are trying to say.

  31. 32 years as ER MD, 10 years with EMR by jmooo · · Score: 1

    The chorus will now all sing, "You can't always get what you want" I set my priorities, the IT staff sets their priorities, the administration sets their priorities, etc What about the patients???

    1. Re:32 years as ER MD, 10 years with EMR by Anonymous Coward · · Score: 0

      The trump will now all sing, "trump can't always get what trump wants" I set my trump, the trump staff sets their trump, the trump sets their trump, etc What about the trumps???

  32. "They" are not stupid by tsstahl · · Score: 1

    " and mostly go unnoticed by hospital IT staff."

    and mostly go willfully unnoticed by hospital IT staff.

    Fixed that for you.

    Though it is more correct to say "hospital IT staff turn a blind eye to the practice".

  33. Doc, you haven't even followed the literature. . . by Salgak1 · · Score: 1

    Because, that biometric and password-protected issue-the-drug-machine you mentioned ? Likely a Pyxis SupplyStation, and ***very*** easily hacked. With a screwdriver. They even discussed it here on Slashdot several months ago. . .

  34. The problem has been solved - at least 5 years ago by Anonymous Coward · · Score: 0

    Proximity badges for doors/computers, and fingerprint scanners for medication/supply dispensers solves the problem.

    But since that costs money to implement, management prefers to push the blame for non-compliance to the individual rather than admit the system is hindering efficient work practices.

    Maybe another few committees, a self-learning powerpoint presentation (or five), and a mandatory in-service will show the peons the error of their ways.

  35. I fooled you! by davidwr · · Score: 1

    That's not my work password, it's my debit-card PIN!

    I write my work password down on the back of my debit card.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  36. Solutions: by Anonymous Coward · · Score: 0

    I'm sure there are viable solutions to these kinds of problems, as others have mentioned it's about striking a balance between security and accessibility.

    Personally, I'd think this scenario would best be suited to magnetic/swipe cards.

    You could also take a deterrent approach as opposed to a prevention approach by allowing access to things with no restriction, but unless a security measure is taken an alert is raised, i.e. alarm. This would deter opportunists while allowing staff access in an emergency without a security measure.

  37. I'm facing a similar problem... by kwelch007 · · Score: 1

    I'm the Admin for a High-Tech factory. While we do use some very dangerous chemicals, those are pretty well restricted using physical means. However, on the factory floor itself, the company has historically used shared passwords for most of the manufacturing tools themselves. While this doesn't currently pose much of a safety threat, it does make tracking "who did what" basically impossible. Additionally, we were recently acquired by a Public company, and due to SOX, the whole "shared password" thing is a big no-no. While my problems are not as nearly "life or death" as the Medical scenario, I can relate.

    As a replacement authentication technology, I've been investigating various Biometrics, RFID cards, etc., as possibilities. Some could work, but face potential barriers in my environment (our factory is a "Clean Lab" environment...everyone has to wear Clean Suits, gloves and masks.) Because of the gloves, things like Fingerprint scanners won't work. Face recognition doesn't seem to be up to par yet based on the trials I've done. The use of RFID tags would work, but then you have the issue of potential theft of said tag.

    I haven't had time to try one yet, but years ago at an office building I worked at, they had a sort of "hand measurement" system...basically, you would put your hand on the plate and squeeze some pins between your fingers. Then you would have to enter a PIN on a keypad. I could see something like this working in my environment, but frankly haven't had time to go looking for one.

    In the end, it seems that Password security is the best (especially if it is Multi Factor,) but is not always practical. I wonder what others have used as alternatives.

    1. Re:I'm facing a similar problem... by PPH · · Score: 1

      The use of RFID tags would work, but then you have the issue of potential theft of said tag.

      The theft problem is diminished if the tags are used for facility access control. 'Lose' your tag and you've got to stop by security for a new one (and have the old one deactivated). Actual theft by miscreants attempting unauthorized access has been handled in an innovative way in at least one place. Tags gone missing are 'deactivated' but still work to open one door in a man trap. Then the holder is stuck, having to explain himself to (armed) security. Not willing to go that far? You can still get a photo of the interloper.

      --
      Have gnu, will travel.
  38. Endemic? Endemic? by tlambert · · Score: 1

    Endemic? Endemic? Don't you mean "nosocomial"?

  39. Re:feels familiar here. you can easily fix it. by Sir_Eptishous · · Score: 1

    It also required me to train users on posix permissions and how to properly collaborate in a unix-like environment

    Are you posting from 1993?

    --
    We play the game with the bravery of being out of range
  40. Have they tried... by tonyyeb · · Score: 1

    Endemic1?

  41. Really? by nospam007 · · Score: 3, Informative

    "Hospitals are pretty hygienic places -- except when it comes to passwords, it seems. "

    Hardly. Bad hygiene in hospitals kills over 100.000 people a year in the US alone.

    http://abcnews.go.com/GMA/stor...

    1. Re:Really? by pem · · Score: 1

      I came here to say the same thing, but with more snark. "Citation needed."

  42. And the reason is? by BoRegardless · · Score: 1

    Pressure to perform QUICKLY, ALL THE TIME, on every 16 hour shift.

  43. New Password Post-IT (TM) by Provocateur · · Score: 1

    One company has announced the new product line called Password PostIts, specifically for this misuse.

    These are just as easy to use.
    1.Write the password down on the post It.
    2.Peel off.
    3.Stick in a convenient location, preferably visible to human traffic
    4.Sell them by the gajillions
    5.Profit!

    What makes them unique is they are non-stick postIts. Other than being lime green, they really don't stay on for very long.

    --
    WARNING: Smartphones have side effects--most of them undocumented.
  44. I run Linux on my computer by the_humeister · · Score: 1

    The IT staff felt I was competent enough to be given Admin access to my machine. So I shrank the Windows partition and installed Debian in the empty space. Works great! I can do my work just as well on Debian as I can in Windows

  45. So what is the solution? by houghi · · Score: 3, Insightful

    This is a social problem and IT tries to solve it with a technical solution. Enforcing this technical solution will not solve anything. At least not in the long run.

    The issue is that everybody looks at the problem as a problem with THEIR system and forget that security is not a technical issue. It is a social issue. It is a process and humans are the most important part of that process as well the reason it exists.

    I have some hundred websites with passwords. At mu job I can not even select my login, so that is an added bonus. Not all are maintained systems by our IT department. I am not an IT person, so I have no way of installing some password reminder program on my work PC (OK, I could and get fired for installing software on the system)

    I have one system the rquires me to change the password EVERY FUCKING WEEK!
    So yes, I make use of simpeler passwords. I write down the one that I need to change each week.

    I have asked and not often gotten an answer why I must change my password every 30 days. If I need to change it every 30 days, why not 29, or 7 or every day? If I would need to replace my lock at home every month, I would doubt the security standard of said lock.

    Unfortunately I do not have a solution. I just know what we have now is not workable anymore.

    Perhaps a method where you use an RFID in combination with a PIN or even Bluetooth in combination with a PIN might work. Forgot your RFID? The procedure to get a backup should be pretty easy to implement.
    There should also perhaps be a need for an 'override' procedure.

    Whatever the solution is, you need to work with the people you want it to use.

    --
    Don't fight for your country, if your country does not fight for you.
    1. Re:So what is the solution? by DarthVain · · Score: 1

      Pretty much this. I was vocal about it at work, ignored, and just go with it now. I'm the same I have a million different usernames and passwords for various systems I have access to. There has been some improvement in the last couple of years, where we've managed to consolidate some systems into the same environment where we can share usernames/passwords, but for the most part it is still the same. Then every year some new systems are added to the pile, each with it's own username and passwords... Ideally you would use the same password, or a few, but then you get all these systems with various levels of security validation on what you can use for a password. There are a couple in particular which are so restrictive that, I have to sit there forever like when trying to pick a unique username for your WOW account back in the day... Then they all expire every 30 days, but not all a the same time, but on some random rotation to whenever the fcsk it was you last changed it. At one point I pretty much accused the IT group of just generating work for themselves for all the forgotten password requests they would get in a day, and then being able to report on how many hundreds of thousands of "issues" they've "resolved". However as the saying goes, never attribute to malice what is more likely stupidity. I don't think many people understand security very well. First of all it only has to be good enough in 99% of the cases to simply act as a "reasonable" deterrent. Everything doesn't have to be ironclad. Secondly even if their was a "breach" what is the worst case than can happen most the time? Usually very little. So you can log onto my financial account at work, great now you know how much I make, and can book me some time off, thanks. Not to mention the LAYERS of security. I mean there is the network security, the physical building security, there is my account security, there there are individual applications which have security, some of which also have a second layer of security built in themselves, then there are the account security within each application, etc... Nothing we do is really that terribly important. Then yes we have printers, and copiers, and plotters, and junk that all have their own codes.... So yeah it is no wonder that people write things down or have stupid passwords. As I said when I tried to raise the issue, I was pointed to "Security" and told too bad. I basically said, people are just going to use a post-it note or use stupid passwords, but the response back was well that is against policy, and they would just make them make "stronger" passwords. I finally came to the conclusion after a couple of years that "Security" actually means "scapegoat". If ever there is a breach, the only thing that matters is they can point to how policy was not followed, and it is all somebody else's fault than there's. Never mind they have zero interest in trying to make security actually work well...

    2. Re:So what is the solution? by Anonymous Coward · · Score: 0

      I had actually thought of that, and I DO work in healthcare IT.

      The idea is to have the employee badge contain RFID as well. So it becomes a 2 for 1, no additional dongles or cards to carry. When they reach a terminal, the RFID reader performs the first authentication while a pin of numbers is required to use the system. When they walk away, they lock their machines or the terminal locks because it loses connection with the RFID in their hospital badge.

      The point is what do they possess daily that I can make use of to help me help them.

    3. Re:So what is the solution? by houghi · · Score: 1

      What they posses daily? Their phone. You could even use different things for different people. There are even RFID stickers. They slap that on their phone and done.
      Or if they are required to have a badge, slap the sticker on that. On Ebay you can find then from 30cents to 1USD.

      --
      Don't fight for your country, if your country does not fight for you.
  46. Common Access Card by Anonymous Coward · · Score: 2, Informative

    If you forget a password, someone may die right in front of you.

    I'm surprised that more hospitals haven't implemented CAC:

    https://en.wikipedia.org/wiki/Common_Access_Card

    You generally need a pass card for most offices now anyway, so allowing it may not be a bad idea. When the work day first begins, you login with BOTH the passcard AND a password, which starts a 4/8/10 hour timer window. With-in that window you can only SIMPLY use your card to login, but once it passes you have to re-login. This way if the card is lost you still need two-factor.

    Basically putting a Kerberos ticket on the card for single sign-on for a limited time.

    1. Re:Common Access Card by EndlessNameless · · Score: 1

      CAC is the US DoD implementation of smart cards, and any enterprise can deploy smart cards to its users.

      Basically putting a Kerberos ticket on the card for single sign-on for a limited time.

      That is not at all how smart cards work.

      The card contains one or more certificates, and it will perform some pre-defined authentication operations using the private key if presented with the user's PIN.

      Successful completion of these operations verifies the owner of the certificate is using the machine. The Subject Alternative Name field on the certificate is linked to the user's Active Directory account. Standard verification against OCSP or CRL is used to validate the certificate.

      All machines store, send, and receive both Kerberos TGTs and service tickets the exact same way for smart card users as they do for password-based users. There would be huge compatibility issues if the machines needed to pass tickets through the smart card.

      Putting Kerberos tickets on smart cards would be a logistical nightmare due to those issues, and it completely ignores the fact that Kerberos TGTs must expire periodically to mitigate offline attacks.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
  47. Can't blame the end user staff for password misuse by Anonymous Coward · · Score: 0

    There is a password for seemingly every cabinet, door, closet, med cart, wireless and wired devices (not just your dozen patient record accounts, but little things like glucometers and every other gadget), other computer accounts, etc. and each has it's own rules (length, special chars, caps, numbers) and they expire frequently, but at different intervals. Is it any wonder that people can't remember them all? I have over 100 account at the few hospitals I work at. They are written in a card in my wallet, in marker on my ID, on door frames, and on the wall above the Pyxis (free narcs to anyone who can figure it out).

    The biggest security problem here is the complexity... no one can realistically be expected to commit this mess to memory.

    Fingerprints are not the answer... I wear gloves a lot of the time. My anecdote here is that I needed a med for a patient in distress from a cart that required a fingerprint... I pulled off my glove and the cart wouldn't recognize my sweaty fingerprint. Nurses were running up and down the hall and none of the carts would open. I sprained my ankle trying to kick the door off. The situation progressed to CPR on a young and healthy patient. The situation resolved without any damage to the patient. These situations need to stay anecdotal because they can't be allowed to happen with any frequency. ...But the IT situation gets worse month by month.

  48. At a public hospital in NZ that shall remain .. by Anonymous Coward · · Score: 0

    .. nameless which I worked at in IT at the early 2000's.

    Network security was non existent. A few of us actually had NT4 and Windows 2000 desktops and actual domain accounts to login with, everyone else had Windows 98, and either a shared dept login or would just hit escape to bypass the login screen. At least the different medical apps required users to have a login for each one, but again login sharing was common as was writing down passwords because NOTHING was single sign on.

    The cause of the issue at the end of the day was that IT was usually lumped in under Finance somewhere, and all Finance does is question every dollar spent with no interest in how to do IT properly. So a lack of money, and management leads to that mess.

    Things were being improved around the the time I left a few years later, but as with most publicly funded government run organizations, the systemic issue of middle managers getting them selves involved in everything with their personal agendas basically kills off any hope of getting things done right and properly for the organization as a whole and in a way that the IT staff might actually get some form of enjoyment out of what they're there to do.

  49. Hospitals are cheap by Chewbacon · · Score: 1

    They don't invest the money to make things work smoothly in their IT service, it just has to work. The last hospital I worked for had no central authentication service. You had over a dozen passwords, they all needed to be changed at different times, and all had different requirements.

    Some of the better systems I've seen had a PIN number tied to your longer password. The pin was only good for your shift and you had to change it on your next shift. It resisted brute force by locking out after so many attempts. It was expensive, so of course my hospital didn't want it. However they didn't mind dumping the cash into someone who tirelessly changed passwords all day long.

    --
    Chewbacon
    The Bible is like Wikipedia: written by a bunch of people and verifiable by questionable sources.
  50. Blame Mandatory EMR by Anonymous Coward · · Score: 0

    Patient care cannot be delayed by anything, especially critical patient care. The specter of being slowed down by screwing up typing a complex password, forgetting a complex password and having to retrieve it, or other delays associated with passwords, are a direct threat to patient health and can lead to serious injury or death.

  51. I remember when OSHA... by Anonymous Coward · · Score: 0

    I remember when OSHA proposed a rule requiring a lockout device on a cardiac defibrillator to ensure that only qualified persons could use it. Fortunately that didn't go through, but technically, guarding rules still apply. Technically, the paddles require guarding, because they have voltage above 50 volts between them in normal operation. This would mean some kind of guard to prevent the conductive surfaces of the paddle touching anyone's skin while the device was in use. The guarding rule would also require someone verify the paddles were not energized before they were allowed to touch anyone.

    Makes perfect sense to me - wouldn't want anyone getting shocked by a defibrillator, would we?

  52. Re:Researchers Ignore Real World Concerns Yet Agai by Hognoxious · · Score: 4, Interesting

    Implant all the staff with chips. The kind they use for pets.

    Then they can log on by head-butting the computer.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  53. Re:feels familiar here. you can easily fix it. by Anonymous Coward · · Score: 0

    It also required me to train users on posix permissions and how to properly collaborate in a unix-like environment

    Are you posting from 1993?

    Are you also posting from inside an Escort Wagon?

  54. Re:feels familiar here. you can easily fix it. by Anonymous Coward · · Score: 0

    Mordac, preventer of information services, is that you? Because it seems like all you've accomplished is making things way harder for everyone...

  55. Security of health software is extremely poor by Anonymous Coward · · Score: 0

    Worked with hospital data, patient data, and data from medical test devices for the last 35 years.
    Security across the board is extremely poor, and many companies are secretly trying to monetize health data from private citizens.

    If you find a company that puts medical data 'in the cloud', they will be hacked, or have been hacked already, and the data is 100% insecure.

    For 35 years I have had to attend ethics training, with the same set of ass-clowns that don't have one ethical fiber in their body and don't give a crap about medical data or its security.

    And, it will never improve one bit in the next 35 years either, as the companies in the u.s. don't consider data integrity and security something important.

  56. All this techtalk misses the point by mschuyler · · Score: 1

    The end-user is rarely schooled in ANYTHING IT-related. Keyboards are an obstacle. Mice are an obstacle. Add bureaucracy to this and you have very frustrated users who are not going to take kindly to passwords or any other additional obstacle.

    Last time I saw a doctor he was forced to "code" the X-Ray I was about to get in one of about fifty different codes made necessary by the accounting system. He couldn't see the extended explanations on the page because the data elements had been squished together. Obviously an SQL database. I helped him along.

    "First you need to expand that window to fill the entire screen."
    "How do I do that?"
    "You see that empty square at the top right? Click that."
    (Screen expands. Data is still hidden.)
    "OK. Now take your mouse and grab that very tiny vertical bar separating those two fields and drag it to the right."
    (Fumbles around.)
    "No. Move the mouse until that vertical bar doubles. Now press the left mouse button and drag to the right."
    "My God. Now you can see the whole thing!"
    "Uh huh."

    All the time he was complaining about the bean counters. Finally, he just chose a code at random. I got my X-Ray, then an MRI. Torn meniscus. Still hurts.

    --
    How about a moderation of -1 pedantic.
  57. Re:This Weeks Weak Password for the Hospital is... by Anonymous Coward · · Score: 0

    The Password is...

    AntiBioticResistant.

    Sorry Dave. The password you entered is a vulnerable to a dictionary attack. Please enter a new password conforming to the Information Systems Security Protocol Password Requirements Directive and Manual v2.79191. You have three more attempts before the system locks your account for 30 days.

  58. Why all the passwords by Anonymous Coward · · Score: 0

    We don't need a password on every device and door for security. Patients have a welcome lobby where they are screened for security on the way in. Doctors enter through another door that scans credentials and screens for security. Once inside, that's it! No one should have passwords on ANYTHING.

  59. The problem is passwords. by mr_java66 · · Score: 0

    I don't have passwords with anyone who knows me. They know me. Here is a $10,000,000,000 Idea. Figure out how to get rid of passwords. These insipid things must go!

  60. Re: fault of the programmers by Anonymous Coward · · Score: 1

    That's a pretty short sighted comment considering the audience here.
    A small medical company trying to develop a fetal link monitor to transmit data can do its best to secure its software. But when all the hackers from the US, Russia, Iran, China, and North Korea find a blip on the IP scanners, you can bet they will find a way to compromise the software. And if not the software, there are the API's, OS, protocols, and even hardware that can be vulnerable underneath a hardened application.

  61. Re:Joe 6-pack user's machine by Anonymous Coward · · Score: 0

    Absolutely. Even if walled off to only a local clinic, there would be tens of thousands of patients records accessible.

  62. Re:security is squarely in the way.. by Anonymous Coward · · Score: 0

    That's an argument I hear quite often.

    But the reality is that people usually have lots of time. They are seriously lazy and adverse to security or paperwork or really anything harder than their paychecks direct depositing into their accounts.

    To think of the time savings provided by a system that lets a user access all the patients records from one desk. Without needing to request a paper chart pull or a image from Xray couriered over. And yet they balk at the idea of remembering 8 letters.
    Most physicians are coddled and have a whole team working for them so all they need to do is stroll down the hallway and chat with a few patients while pretending to care. Then they can get back to their live streaming ball game while digitally signing a few prescriptions their PA's filled in.

  63. Re:Doc, you haven't even followed the literature. by I'm+New+Around+Here · · Score: 1

    The machine isn't there to prevent all intrusions, such as someone with a screwdriver or prybar. It is there to prevent medications from randomly going missing. I repair the machines at a few local hospitals. Yes, they are more secure than having unlocked cabinets of pills, and as secure as having locked cabinets of pills.

    The major purpose of them is the fact that the staff have to log in, identify a patient, verify that the patient has certain medicine prescribed, take that medicine, and confirm quantity. For the controlled substances, they are in locked bins within the drawers, so that you can't steal them while getting something else. The common medicines aren't worth the trouble of stealing, so are in unlocked bins.

    But, hey, if you can push the cart down the hall to your truck and drive away, you can have all those dosages of opiates. Good luck on that.

    --
    If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
  64. Re:feels familiar here. you can easily fix it. by Anonymous Coward · · Score: 0

    Yes; welcome to the medical industry.

  65. 32 different passwords by Anonymous Coward · · Score: 0

    I work for a hospital. I just counted 32 different systems that I need different passwords for.
    There are alot of good comments here that all true in our hospital environment.
    Patient care is always top priority and trumps everything else including IT and business needs.
    This isn't a new problem and I'm sure its not unique to health care or other similar industries.

  66. Blame Washington by uncoveror · · Score: 1

    Technology has been a boat anchor dragging down the industry thanks to regulations like Hippa, and requirements that all records be kept electronically. Paper charts are banned. now. This is a classic example of what happens when legislators regulate something they know nothing about. I see it everyday, as I work at the helpdesk of a major midwestern hospital chain. I am convinced all the technology that end users can't figure out has led to dead and injured patients. I am a perma-temp, where I work, not an employee. Outsourcing in healthcare is another problem, but not the one we are talking about here. Anyway, many people working in healthcare are technically illiterate, and refuse to learn. Also software like Epic is too complicated for anyone but engineers. My mother, who was a nurse, is now happily retired. Epic and other high tech whizbangs made her last years in the industry hell. The worst part of it all is cost. Computers, commercial software, and all the support staff needed cost so much more than paper charts did. All they really needed to do was to make PDF of the old paper charts, and let people type into them That would have fixed the problem of scribbly doctor's handwriting. Washington broke it. Will they ever fix it?

    --
    The Uncoveror: It's the real news.
  67. Re:Researchers Ignore Real World Concerns Yet Agai by silas_moeckel · · Score: 1

    They actualy work rather well for my pets the cat flap uses them. Would need more security that just a serial number though.

    --
    No sir I dont like it.
  68. From a Physician's Perspective by Anonymous Coward · · Score: 0

    I am in the process of moving from one large academic medical center to another, which will be my third.

    When I arrived at the second institution, I was amazed at the IT policies. For one, they used some bastardized login system, which only really applied to the medical records system. So if my email was open, then I locked my computer and someone else walked up and logged in, they could read my email.

    The auto-logout timeouts were so short, that if I was using the computer, then a nurse came in and we had a quick conversation, by the time I turned back to my computer, I would have to log in again. I would log in literally 100s of times a day when I was a junior trainee. Each log in took 30-300s to put up a usable EMR. This applied to all computers, even computers that were in physically secure areas (IE, you had to have badge access). Many people would circumvent this system with "mouse wiggle" type apps.

    We only had to change our passwords yearly, but the rules for new passwords were insane and I would end up writing them down.

    There is *no* security to the paging system, so anyone with the thought to Google " paging" could run wild.

    *All* of the doors that I used had keycodes written on the jamb. If they weren't there, I wrote them. I didn't want to have to tell a loved one that their relative died because we couldn't get into the supply room to get the equipment we needed in an emergency.

    At my current institution, when I started it took over a week to get me access to the email system. IT literally couldn't figure it out.

  69. Clarification of title by hey! · · Score: 1

    The password misuse isn't by medical staff. It's IT that is abusing standard password policies that aren't designed for man-rated procedures.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  70. Expiration by markdavis · · Score: 1

    Based on my [very long] experience watching people deal with this in the real word....

    The #1 reason passwords are written down is because of stupid, backwards, unnecessary expiration rules. It is in insane practice that somehow became "best practices" when it should have been declared "WORST practices" decades ago. When your perfectly good and memorized password expires every X days, you are going to either start writing it down, or make it insanely weak (or duplicated with other systems) so it can be remembered.

    The #2 reason passwords are written down is because of stupid, backwards, unnecessary complexity rules. Yes, there have to be some minimum requirements (length, numbers) but some stuff is WAY overkill (I saw one that was it had to be 10 characters, with at least TWO of each- number, symbol, and caps).

    1. Re:Expiration by Anonymous Coward · · Score: 0

      my company does not allow repeat characters(%%%), repeat numbers(222), consecutive numbers(123), or consecutive characters (qwerty). Also all your passwords have to be unique, you can't re-use them at all. Also they expire every 30 days. There's also a secret list of words and passwords that you can't use.

      Oh, and when the system comes back and says "no your password violates the security policy" it won't actually tell you what part of the security policy you violated.

  71. It's not just security that's the problem by speedplane · · Score: 1

    Consultants/Politicians: We're going to move you to electronic healthcare records, you're going to love it!
    Doctors: I know it's old fashioned, but my paper records worked fine, why do we have to change?
    Consultants/Politicians: Ha, ha, that's adorable. Now sign here to get your e-records database for $500k.
    Doctors: Do I have to?
    Consultants/Politicians: Do you like jail?
    Doctors: Okay ... now what?
    Consultants/Politicians: Welcome to the future! Now, you and your staff just have to take this one week course to learn how to use our awesome software!
    Doctors: When do I go back to being a doctor?
    Consultants/Politicians: Ha, silly. Now every you time you see a patient, don't forget to check these sixteen boxes, double click twelve times in the box, and go through the four drop-down menus where the selection is always the second to last. And of course, make sure you click the box releasing us of liability!
    Doctors: This is ridiculous, and these password requirements?
    Consultants/Politicians: We're doing that for your benefit! It's so easy, just change your password twice a week, and make sure to use at least one letter, one number, and three chinese symbols whenever you choose one.
    Doctors: Where's that post-it pad?
    Consultants/Politicians: OMG! You wrote your password down, you have been hacked, how could you possibly break such a fool-proof system!

    --
    Fast Federal Court and I.T.C. updates
  72. This is an area that Google doesn't track by Anonymous Coward · · Score: 0

    thats why. Though I have read recently they are trying to get into surfers medical queries by "making it convenient" or something like that.

    Labs and ICU's are unlikely to take a Windows 10 update with their issues.

    They want your data, meaning the government. Now why would this be? What did Ed Snowden tell the world?

    Let us not forget the government database that Facebook is.

  73. Re:Researchers Ignore Real World Concerns Yet Agai by Anonymous Coward · · Score: 0

    Implant all the staff with chips. The kind they use for pets. Then they can log on by head-butting the computer.

    This was modded interesting but should be modded informative. Took my spouse in for routine surgery recently. Every single staff person used their ID card around their necks to get into EVERYTHING. It was faster and easier than typing a userID/password or even punching in a random keycode. It also provided a layer of authorization to keep staff OUT of more restricted equipment.

    I'll confess my ignorance of the healthcare industry and will ask for a fellow Slashdotter to educate me - why is this not more commonplace?

  74. Re:Researchers Ignore Real World Concerns Yet Agai by Hognoxious · · Score: 1

    Do they have to handle the card to place it in the reader, or can they just bump against it? There are hygiene concerns here.

    My suggestion was a bit facetious, but there are more practical hands free methods.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  75. Re:Endemic? Endemic? by Anonymous Coward · · Score: 0

    And of course they probably meant to be hyperbolic and cute by saying that it was 'Epidemic'. But instead they they were redundant and said that password misuse by hospital staff was not externally caused but instead originated with the staff themselves.

    Frankly I was really surprised that nobody here called the writer on this shit earlier..or is it sooner?

  76. Cryptolocker by Anonymous Coward · · Score: 0

    It's not just passwords , lack of proper security leads to open file shares. That's why many hospitals have been subject to cryptolocker and other malware.
    You just don't hear about it in the news.

  77. Re:Researchers Ignore Real World Concerns Yet Agai by MercTech · · Score: 1

    RFID chips are a wonderful tech to replace passwords, Couple the RFID with some biometrics and you prevent stolen or borrowed card use. Wave the proximity card over the pad and insert hand in the reader... the door unlocks and records who went in at what time. For computer terminals, insert card in ready and scan a thumb print. If the card is withdrawn; the terminal logs you off and goes to sleep mode.

    The biggest bugbear with this system is the "power failure" and "network outage" protocols. You need backup keys to critical doors and someone in charge to open the key box in an emergency. It would probably be best to leave the key to the emergency box in the custody of a senior nurse for a floor. Physicians don't have the mindset to be enabling others to do their job in an emergency.

    This stuff was cutting edge in the 1990s and is proven technology for the nuclear industry since then. In 2003 there was a multi million dollar grant to study the feasibility of such tech which was "turnkey" in industry already. By 2014 you saw a limited use roll out of rfid id cards in, of all places, the Veterans Administration. It has been too long since I was active duty but the new military ID cards sure look like they contain a rfid and a smart chip.

    --
    NRRPT/RCT
  78. hey who leaked it? by gzuckier · · Score: 1

    endemic is my password!

    --
    Star Trek transporters are just 3d printers.
  79. Nosocomial infections by DrYak · · Score: 1

    Pencils are very resistant to virus attacks.

    We're speaking about hospitals.
    Google about "Nosocomial infections", "MRSA", etc.

    Nope. Not even pencils are resistant to virus attacks.
    Just not the same virus.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  80. Mechanical equivalent by DrYak · · Score: 1

    Hey wait, didn't there used to be an invention just like this, but completely mechanical?

    And given the complexity of a modern hospital, you'd have about half a kilogram worth of keys on your keyring just to get around.
    And in some emergency situations, you will need to quickly to yank 4 of them out of your keyring and throw them to a medical student passing by (or a medical nurse passing by which by chance happens not to be required by the emergency) to send them to the pharmacy to bring you some extra medication.

    Long before the invention of password, physical keys used to be "hidden" nearby critical doors.
    (e.g.: Legally, morphine needs to be locked. But morphine can definitely be needed in a case of emergency. Therefor the key to access the box with morphine is hanging on a chain nearby).
    (Actual anecdote in one of the military clinics were I've worked).

    The closest actual equivalent that works up to some point is a wireless keycard (usually integrated into the name tab), with the infrastructure programmed to allow you around depending on it.
    (I.e.: the access doors don't require a specific pin code, but are programmed to allow personal with a keycard which has been validated for that door).
    (More or less done this way in the hospital where I did my studies).

    But even then you'll find problems:

    - You would need to give very broad access rights to very large groups of personnel, which isn't considered as a very bright practice.
    (e.g.: absolutely all doctors and medical students would need to be granted access to nearly every door. Except maybe for the server room, the elevator shaft and the high-voltage transformation station. Because there are actually dozens of emergency scenarios where this will actually be needed)

    - Or you need to find a way to quickly grant access to someone else.

    - And even then, you need to make sure you have a correct strategy to make sure that all the access rights are up to date.

    - You must be sure that the system won't block legitimate emergency access in case of total failure.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  81. Someone might die. by DrYak · · Score: 1

    Also, no, someone won't die right in front of you because of a forgotten password, except maybe in a movie. Real-life healthcare doesn't work like that.

    But real-life insurance, politics and regulation *do*.

    e.g.: "Scheduled substance must always be kept locked" says the regulation. So they're in a locked box.
    (Because, you know... some drug addict my steal them from a hospital for a change instead of trying to cook meth in their garden shed as usual~ )

    But half of those scheduled substances might actually become useful in some emergency cases.

    So the key to this box is hanging on a chain nearby / the pincode is written on a sticky note on the door.
    (I'm not making this up, I've seen such situations).

    A young docotor might be on night shift / rounds in internal medicine.
    Means they are the only on on the whole floor (not only their sector but all the other sector on the same floor), and are the first responder in case of emergency until more staff is summoned and arrives.
    If anything happens, they'll need to have access to all the necessary medication (some not so small backpack, filled with ampoules of nearly every substance needed. Some of which are regulated so the backpack needs to be locked when not in use). They need to have that access unhindered (there should be no confusion because they're not in their usual sector and not know necessarily how to access the backpack).
    Hence the "misuse security" solution above.

    Otherwise they would need to carry their own (not light at all) backpack everywhere with them (I've seen this also on some situations of military medicine or on terrain emergency response).

    And that's just the drugs.

    There's also the problem with devices. Ultrasound images come *EXTREMELY* handy in several emergency situations (to quickly see what's inside, to better and faster pinpoint a blood vessel or a nerve or the airways for some procedures, etc.)
    If you can't get your image *NOW* just because you need to log into the fucking computer, somebody is going to die.

    At least for that situation the tendency is changing. Instead of the just honking "computer on a tray with an US-imaging head" attached to it, emergency medicine is starting to rely on very small portable device (the size of a netbook, a tablet, or even a smartphone) that are completely offline (their only mean of communication with the outside world is a USB or SD port to save picture to- / upload updates from-) and contain no patient related data (the only attached metadata is the current time the picture was taken. And by "metadata attached", I mean it's part of the file name, because the device doesn't even bother to fill in the corresponding DICOM fields.
    (= it a standard medical imaging format. A bit like what JPEG is for internet picture. And just like JPEG can have EXIF, a DICOM can contain a lot of information from the patient file)

    So it's just: open the device, shoot the picture, done. No fumbling wiht stupid passwords.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  82. Overstaffed hospitals ? by DrYak · · Score: 1

    Woah! That sounds like a wonderful place to work in!

    I wish I did my intership there instead of the usual understaffed place, similar to the one described above.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  83. Smartcards by DrYak · · Score: 1

    That was the strategy in place in the hospital were I've done most of my internship.

    The name tab doubles as a smartcard.

    Except that, to be able to actually function, they need to give very broad access rights to very large segment of their personnel.

    e.g.: all doctors, and nearly all medical students, can open almost any door (with very few exceptions like high voltage transf. station, elevator shaft, etc.)

    Which isn't the best practice from a security point of view, but is the best compromise between regulation (everything needs to be locked !!!) and emergency situations (need to send the student to get some medication).

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]