United States: Best Cybersecurity Practices For Healthcare Organizations – Insider-Caused Data Loss

This article is part of a series of blog posts exploring the recommendations and guidance Health & Human Services (HHS) provides to healthcare organizations in its Cybersecurity Best Practices report. For previous articles in the series, click here.

While any security incident may cause an entity heartburn, when the incident is traced back to an insider, the feeling turns to heartache in an instant. While there is a certain element of pity associated with a run-of-the-mill hack, admitting to patients, regulators and staff that a fox was invited into the henhouse by the entity gives an air of complicity.

Didn't you do a background check? Why weren't you closely surveilling and logging that type of staff activity? What's the bad guy's name? Did you fire the person? What else did the person have access to? How do you know everything the person accessed? Does the person have a history of violence or mental health issues? How could you have hired someone like this?!

These are the uncomfortable questions posed in the wake of an intentional insider-perpetrated incident (in addition to all the normal post-incident questions about the security measures that were in place). Accidental data loss often creates slightly less panic, but the questions still have an undercurrent of "how could you employ this person (who isn't cautious enough to make sure the attachment/email address/fax number is correct)?" And frequently, whether intentionally or accidentally, the administrators and the public are often asking the same questions.

The report on cybersecurity best practices (Report) attributes accidental and intentional insider-caused data loss to the following:

  • Files containing sensitive data accidentally emailed to incorrect or unauthorized addressees.
  • Lack of adequate monitoring, tracking and auditing of access to patient information on EHR systems.
  • Lack of adequate logging and auditing of access to critical technology assets, such as email and file storage.
  • Lack of technical controls to monitor the emailing and uploading of sensitive data outside the organization's network.
  • Lack of physical access controls.
  • Lack of training about social engineering and phishing attacks.

To help combat these issues, the Report provides some practices to consider for each entity size.

For Small, Midsize and Large Entities

Train staff and IT users on data access and financial control procedures to mitigate social engineering or procedural errors. For small entities, the Technical Volume suggests that staff education should include how to recognize phishing techniques, leveraging an encryption add-on within the email system to make it easier for workforce members to send information in a protected format, and stressing the importance of being "extra careful" when sending and receiving emails containing PHI. For midsize and large entities, the guidance is much more robust and delves into how to make the education as effective and sticky as possible. (See Section 1.M.D on page 18 of the Technical Volume for Medium and Large Health Care Organizations.) No matter what the entity size, evidence of these training modules and emails should be kept, as an OCR investigation will likely ask an entity to prove it was keeping up with workforce education.

For Midsize and Large Entities

Implement and use workforce access auditing of health record systems and sensitive data. At the heart of this recommendation is HIPAA's "minimum necessary" principle, which requires entities to allow access to only as much PHI as is necessary for a particular workforce member to do his or her job. This also helps shrink the potential scope of PHI that a particular user can accidentally or intentionally misuse or disclose. Importantly, access controls that effectuate the minimum necessary standard are relevant not only during user account creation. When a user changes jobs or ends his or her relationship with the covered entity, there are other triggers for evaluating and limiting or ending access to PHI.

During the access provisioning stage (at the start of employment or the beginning of a new role), the Technical Volume suggests the following:

  • Identify common systems that all users will need to access and the most basic access rights required for each of those systems, and define them in organizational policies, procedures or standards. Procedures should be established to ensure consistent provisioning of basic access rights, and an automated tool may be considered to help boost accuracy and reliability.
  • Establish procedures and workflows for provisioning access required to information and systems beyond the most basic needs. Entities should pay special attention to cloud-based systems and consider a two-part process that allows users to request access but requires a second individual to approve the request prior to granting access. A common approach is to designate an employee's supervisor as the approving party.

For deprovisioning, the Technical Volume recommends entities adhere to the following principles:

  • Establish procedures to terminate access to user accounts, and execute them promptly at the time of termination. This too could be an automated process triggered after receiving notification of termination from the system of record (usually the HR system). Whether manual or automated, the termination should include steps to prevent active sessions (e.g., email logins on mobile phones) from remaining active after the employee leaves the organization.
  • Establish an "urgent termination" process outside the normal termination procedures to be used in cases of sensitive termination, such as an involuntary termination.
  • Ensure that termination procedures include both critical business systems and ancillary or auxiliary systems, particularly cloud-based systems accessible outside the entity's network, as these systems will remain accessible to the user if only system-based deprovisioning occurs.
  • Build automatic timeouts for nonuse in critical systems. These timeouts can catch edge cases where deprovisioning procedures are not executed, ultimately reducing the exposure to unauthorized access.

Implement and use privileged access management tools to report access to critical technology infrastructure and systems. The Technical Volume acknowledges both the inherent weakness of password-based authentication and the fact that there is currently no alternative. That said, the Technical Volume does provide four password authentication practices for entities to consider:

  • Centralized authentication: This allows an entity to manage access rights and passwords from a central location, allowing for timely deprovisioning and enterprise-wide password standards. Once hackers find a way into a system and a valid user name (neither of which are difficult given social media and search engines), they use tools to try "dictionary words" hundreds of times a second in search of the one used as a password. Entities should consider implementing the following password management policies to help thwart these brute-force, dictionary attacks: 1) Limit how frequently a user can attempt to enter his or her password. 2) Use cryptographically strong hashing and salting for password storage. 3) Use passphrases in place of passwords. Require a minimum of eight characters and permit up to 64 characters and spaces. 4) Implement dictionary-based password checking and compromised password blacklists. Prohibit users from establishing risky passwords, such as those used in previous breaches; repetitive or sequential characters; or context-specific words (such as a name of a service, username or derivatives thereof).
  • Privileged account management: Entities likely have privileged administrative accounts, which gives an IT administrator god-like access to some or all systems and applications within the organization to perform tasks like provisioning, testing, software deployments and updates. The Technical Volume warns entities to provision at least two accounts to an IT administrator: one account for use completing day-to-day activities and a separate administrative account with access only to systems required by the IT administration function. This is because the use of privileged accounts during normal day-to-day business may expose these accounts to malware attacks, giving an attacker elevated access to the organization's environment. To limit this exposure, the Technical Volume suggests the following controls for managing privileged accounts: 1) Ensure that the passwords set for service accounts are large and complex (at least 32 characters, preferably 64). 2) Rotate these passwords on a defined frequency, but certainly if the password is ever compromised. 3) Escrow privileged systems' credentials, making them unique for each system or device. 4) Link privileged access to problem, change or service tickets in the organization's ticketing system. 5) Require the use of a jump server when elevating privileges, and ensure full recording and auditing of the jump server. 6) Require brokered access to a privileged account that registers which user is using the privileged account and records all actions taken. 7) Require multi-factor authentication for all privileged accounts used interactively. 8) Conduct regular reviews of privileged access. 9) Limit actions that privileged accounts can take by using access control lists. Check for the use of sensitive commands and alert the IT or Information Security department if there is misuse.
  • Local application authentication: Where applications do not support a centralized authentication model, entities must maintain solid access control procedures to manage user accounts. This requires designating a responsible IT owner who will manage and regularly review these accounts to prevent continued access by an employee after he or she leaves the organization. The Technical Volume recommends the following extra controls: 1) Designate an IT owner for each legacy/cloud-based system. 2) Establish a distribution list in the organization that includes IT owners as members, and submit terminations to the distribution list as they occur. 3) Ensure that IT owners comply with standard operating procedures for the onboarding, review and, most importantly, termination of users.
  • Monitor authentication attempts: Monitor both regular and privileged user accounts for security and compliance purposes.

Implement and use data loss-prevention tools to detect and block leakage of PHI and PII via email and web uploads. DLP tools can ensure that sensitive data are used in compliance with an organization's policies, detecting when defined types of information are moved in potentially policy-violating ways. For more on this issue, please see our post about loss or theft of equipment or data.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Related Topics
 
Related Articles
 
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Mondaq Sign Up
Gain free access to lawyers expertise from more than 250 countries.
 
Email Address
Company Name
Password
Confirm Password
Country
Position
Industry
Mondaq Newsalert
Select Topics
Select Regions
Registration (please scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaq’s use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributor’s own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions

Mondaq.com (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of www.mondaq.com

To Use Mondaq.com you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these Terms or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaq’s Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.

Disclaimer

The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use of the Content or performance of Mondaq’s Services.

General

Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaq’s right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions