How Deception Technology Helps HIPAA Compliance

How Deception Technology Helps HIPAA Compliance

1 | SECURITY GUIDE : HIPAA Compliance How DeceptionWHITE PAPER Technology Helps HIPAA Compliance A TrapX Security Guide by Moshe Ben Simon Founder and Vice President, TrapX Security © 2016 TrapX Security. All Rights Reserved. 2 | SECURITY GUIDE : HIPAA Compliance Contents Notice .....................................................................................................................................................3 Disclaimer ...............................................................................................................................................3 HIPAA Overview ....................................................................................................................................4 HIPAA Compliance Penalties .................................................................................................................5 Table 1 - Civil Violation Penalties .................................................................................................................................... 6 Who Must Comply with HIPAA? ............................................................................................................7 Health Care Providers ..................................................................................................................................................... 7 Health Plans ..................................................................................................................................................................... 7 Health Care Clearinghouses ............................................................................................................................................ 7 Business Associates ......................................................................................................................................................... 7 Privacy Rule and PHI ..............................................................................................................................8 Security Rule ..........................................................................................................................................9 Administrative Safeguards .............................................................................................................................................. 9 Physical Safeguards ....................................................................................................................................................... 10 Technical Safeguards ..................................................................................................................................................... 10 Supporting Specific HIPAA Requirements with TrapX Deception Technology ...................................11 Table 2 - §164.306 - Security Standards: General Rules ............................................................................................... 11 Table 3 - §164.308 - Administrative Safeguards ........................................................................................................... 12 Table 3 - §164.308 - Administrative Safeguards (Continued) ....................................................................................... 13 Table 4 - §164.312 - Technical Safeguards .................................................................................................................... 14 Notes: TrapX Security Compliance Support .......................................................................................15 Deception Technology and HIPAA Compliance ..................................................................................17 Appendix A: HIPAA Resolution Agreements and Civil Monetary Penalties ......................................18 Resolution agreements reported in 2016 year-to-date include the following: ............................................................ 18 Appendix B: Ransomware Implications for HIPAA .............................................................................19 July 11 Guidance by HHS OCR on HIPAA With Respect to Ransomware.................................................................... 19 Appendix C: Medical Device Hijack (MEDJACK) and HIPAA Compliance .........................................20 © 2016 TrapX Security. All Rights Reserved. 3 | SECURITY GUIDE : HIPAA Compliance Notice TrapX Security reports, white papers, and posi- These materials may be changed, improved, or tion papers are made available for educational updated without notice. TrapX Security is not re- purposes and general information only. Although sponsible for any errors or omissions in the content the information in our reports, white papers, and of this report or for damages arising from the use of updates is intended to be current and accurate, the this report under any circumstances. information presented herein may not reflect the most current developments or research. Disclaimer The Health Insurance Portability and Accountability Counsel or Outside Counsels, or HIPAA Information Act of 1996 (HIPAA) is complex legislation. This Technology Specialists) to review in support of a document is not meant to substitute for legal advice decision to utilize Deception Technology as part of with respect to this legislation. It is meant only a cyber-defense strategy. to provide supplemental information for HIPAA experts (Privacy Officer, Security Officer, General © 2016 TrapX Security. All Rights Reserved. 4 | SECURITY GUIDE : HIPAA Compliance HIPAA Overview The Health Insurance Portability and Accountability HHS published a final Security Rule in February Act of 1996 (HIPAA), also identified as Public Law 2003, with compliance required as of April 20, 2005 104-191, required the U.S. Department of Health for large entities and on April 20, 2006 for smaller and Human Services to define national standards health plans. for electronic health care transactions and security procedures. The legislation outlined how protected HHS enacted a final Omnibus rule, implementing health information (PHI) should be safeguarded by a number of provisions of the Health Information the entities that hold it. Technology for Economic and Clinical Health (HITECH) Act to strengthen the health information The U.S. Department of Health and Human Services privacy and security protections established under (HHS) published the Privacy Rule in December HIPAA. The HITECH Act was enacted as part of the 2000 and updated it in August 2002. The Privacy American Recovery and Reinvestment Act of 2009 Rule set standards for the protection of individually and signed into law on February 17, 2009. identifiable health information. Compliance with the Privacy Rule became mandatory on April 14, 2003 for large entities and on April 14, 2004 for smaller health plans. © 2016 TrapX Security. All Rights Reserved. 5 | SECURITY GUIDE : HIPAA Compliance HIPAA Compliance Penalties Financial penalties are designed to act as a visible Table 1 lists civil violations and the prescribed range and strong deterrent. The goal is to hold covered of associated penalties. Civil violation penalties entities accountable for their actions and help to are administered by the Department of Health and ensure that they take necessary steps as stipulated Human Services, Office of Civil Rights. by the HIPAA regulations to protect the privacy and confidentiality of health care information. Criminal penalties are generally prosecuted by the Department of Justice. Individuals that “knowingly” Financial penalties for failure to comply with HIPAA disclose or obtain protected health information can be severe. Subtitle D of the HITECH Act can be fined up to $50,000 and be imprisoned for includes several provisions that strengthen the civil up to one year. The addition of “false pretenses” and criminal enforcement of the HIPAA rules to can increase the fine to $100,000 and the length allow a penalty of up to $1.5 million for all violations of imprisonment to five years. Offenses committed of an identical provision. In 2016 alone, a cursory with the intent to use or sell the protected health in- review of the public resolution agreements (see formation can further increase the fine to $250,000 Appendix A) reveals many millions of dollars in fines and extend the length of imprisonment to 10 years. levied against health care organizations. © 2016 TrapX Security. All Rights Reserved. 6 | SECURITY GUIDE : HIPAA Compliance Table 1 - Civil Violation Penalties CLASSIFICATION DESCRIPTION HIPAA PENALTY Category 1 Unaware. The minimum penalty is $100 per violation, with an annual maximum The covered entity or business of $25,000 for repeat violations. associated was unaware of the violation and could not have avoided it, even The maximum penalty can be if reasonable care had been taken to $50,000 per violation, with an annual comply with the HIPAA regulations. maximum for this violation category of $1,500,000 Category 2 Reasonable cause. The minimum penalty is $1,000 per violation, with an annual maximum The covered entity or business of $100,000 for repeat violations. associate should have been aware but committed the infraction due to reasons The maximum penalty can be other than “willful neglect.” $50,000 per violation, with an annual maximum for this violation category of $1,500,000. Category 3 Willful neglect but corrected within The minimum penalty is $10,000 per time period. violation, with an annual maximum of $250,000 for repeat violations. The covered entity or business associate violation

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    21 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us