Difference between revisions of "Information security"

From Clinfowiki
Jump to: navigation, search
m (Information Security Goals)
 
(35 intermediate revisions by 5 users not shown)
Line 1: Line 1:
'''Introduction:'''
+
'''Information security''' is maintaining [[confidentiality]] and availability  simultaneously. Information should be hidden, safe, private, and also ready for immediate use.
'''Security''':” state of freedom from danger or risk”.
+
  
'''Information Security:'''
+
== Introduction ==
Maintaining:
+
• Confidentiality: Keeping your information:
+
  
1. Hidden
+
Computer equipment that handles or stores information needs to be protected from harm or unauthorized intrusion.  Computer hardware, software, and tthe data stored on these systems is always potentially at risk. Information, especially medical information that is confidential, non-replaceable, or whose loss of would cost time and money must be protected from a variety of threats. The most common threats are natural disasters and hazards, computer failures, media failures, malicious attacks, and sometimes, ourselves.
  
2. Safe
+
If you look up the definition of “Information Security” on the Web, you will find a host of different interpretations (see below), many of them with questionable foundations. Strangely enough, the '''US Code''' probably contains the best definition:
  
3. Private
+
'''US Code Title 44, Chapter 35, Subchapter III, § 3542'''<ref name="US Code Title 44,  Chapter 35, Subchapter III, § 3542">US Code, http://www.law.cornell.edu/uscode/text/44/3542/</ref>
  
• Availability: Making sure IT resources are:
+
(1) The term “information [[security]]” means protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide—
 +
   
 +
    (A) integrity, which means guarding against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity;
 +
    (B) confidentiality, which means preserving authorized restrictions on access and disclosure, including means for protecting personal privacy and proprietary information; and
 +
    (C) availability, which means ensuring timely and reliable access to and use of information.
  
1. Present
+
This definition is based on the concept that a person, business or government will suffer harm if there is a loss of confidentiality, integrity or availability of information and that it is the role of information security to minimize the possibility that such harm will occur. Other commentators have tried to expand on this approach and argued that other elements should be added (see CERT<ref name="CERT"> US CERT WebPage, https://www.us-cert.gov/</ref> and Donn Parker<ref name="Donn Parker"> Donn Parker Biography, http://computer.org/computer-pioneers/pdfs/P/Parker%20Donn.pdf</ref>). These expansive approaches tend to create a confusing definition that detracts the user from focusing on harm or risk. In effect, they over complicate the issue. <ref name="US Code"> US Code Title 44, http://www.law.cornell.edu/uscode/text/44/3542</ref>
  
2. Ready for immediate use!
+
==Information Security Goals==
 +
The four (4) primary goals of information security are:
  
Integrity: Knowing and using information that is sound and unchanged by anyone who is not authorized.
+
#Confidentiality
 +
#Integrity
 +
#Availability
 +
#Non-repudiation.
 +
(Accomplishing these is a management issue before it's a technical one, as they are essentially business objectives.)
  
'''What do we need to protect?'''
 
• Hardware
 
  
• Software
+
'''Confidentiality''' is about controlling access to files either in storage or in transit. This requires systems configuration or products (a technical job). But the critical definition of the parameters (who should be able to access what) is a business-related process.
  
• Data
+
'''Integrity''' is a matter of version control - making sure only the right people can change documents. It also requires an audit trail of the changes, and a fallback position in case changes prove detrimental. This meshes with non-repudiation (the change record must include who as well as what and when).
  
1. Your time
+
'''Availability''' is the Cinderella of information security as it is rarely discussed. But however safe from hackers your information is, it is no use if you can't get at it when you need to. So you need to think about data back-ups, bandwidth and standby facilities, which many people still leave out of their security planning.<ref name=”Barwise 2006”> Barwise, M. Four Goals of Security. http://www.computerweekly.com/opinion/Four-goals-of-security</ref>
2. Your money
+
3. Confidential or non-replaceable information
+
  
      '''From whom?'''
+
==[[EMR|Electronic medical record]] security==
  
• Natural Hazard
+
===Pros===
• Computer Failure / Media Failure
+
• Malicious People
+
• Sometimes, yourself
+
  
Information Security Goals:
+
EHRs can provide great privacy and security, e.g.,
  
• Data Integrity
+
* Access controls can be more granular
• Data is correct
+
* Authentication mechanisms provide audit trails and non-repudiation
• No unauthorized modification
+
* Disaster recovery plans assure greater availability
• Data Confidentiality
+
* Encryption can provide confidentiality and data integrity
• Only authorized parties can view
+
• Data Accessibility
+
• Authorized parties can easily and quickly access
+
• Often a casualty of information security
+
  
EHR security:
+
===Cons===
  
Pros:
+
* Information flows more easily, risk of mishap is greater
EHRs can provide great privacy and security, e.g.,  
+
* Collection of large volumes of data more feasible and risky
o Access controls can be more granular
+
* Sharing of information for treatment, payment, and operations misunderstood
o Authentication mechanisms provide audit trails and non-repudiation
+
* New methods to attack data are continuously being developed
o Disaster recovery plans assure greater availability
+
o Encryption can provide confidentiality and data integrity
+
  
Cons:
+
== Flow of information in health care have many points to “leak” ==
o Information flows more easily, risk of mishap is greater
+
o Collection of large volumes of data more feasible and risky
+
o Sharing of information for treatment, payment, and operations misunderstood
+
o New methods to attack data are continuously being developed
+
  
  Flow of information in health care have many points to “leak”:
+
==Direct patient care:==
  
Direct patient care:
+
* Provider / Primary Care physician
Provider
+
* Clinic Personnel/ Medical Staff
Clinic
+
* Hospital Admissions
Hospital
+
* Patient
Support activity:
+
* Insurance company
• Payers
+
* Researchers
• Quality reviews
+
* Employees / other hospital employees
• Administration
+
“Social” uses:
+
Insurance eligibility
+
• Public health
+
• Medical research
+
Commercial uses:
+
• Marketing
+
• Managed care
+
• Drug usage
+
  
NB: Even “de-identified” data is not necessarily secure
+
==Support activity:==
 +
 
 +
* Payers
 +
* Quality reviews
 +
* Administration
 +
 
 +
==“Social” uses:==
 +
 
 +
* Insurance eligibility
 +
* Public health
 +
* Medical research
 +
 
 +
==Commercial uses:==
 +
 
 +
* Marketing
 +
* Managed care
 +
* Drug usage
 +
 
 +
NB: Even [[Identifiable Health Data|de-identified]] data is not necessarily secure
 +
 
 +
 
 +
==The Shields:==
 +
 
 +
==1-Risk assessment==
  
The Shields:
 
1-Risk assessment
 
 
We should balance :
 
We should balance :
• risk,
 
• benefit,
 
• cost and
 
• loss of accessibility
 
  
2-Access Restriction
+
* risk,
Authentication
+
* benefit,
Access Control
+
* cost and
Accounting
+
* loss of accessibility
 +
 
 +
==2-Access Restriction==
 +
 
 +
* Authentication
 +
* Access Control
 +
* Accounting
 +
 
 +
== Security Policies==
  
3-Security Policies
 
 
We should set documented:
 
We should set documented:
• goals
 
• procedures
 
• organization
 
• responsibilities
 
  
Technologies to secure information:
+
* goals
 +
* procedures
 +
* organization
 +
* responsibilities
  
Deterrents
+
==Technologies to secure information:==
Alerts
+
 
Audit trails
+
 
 +
== Deterrents==
 +
 
 +
* Alerts
 +
* [[Audit trails]]
 +
 
 +
== System management precautions==
  
• System management precautions
 
 
-Software management
 
-Software management
-Analysis of vulnerability
 
  
• Obstacles
+
-Analysis of vulnerability
– Authentication
+
– Authorization
+
– Integrity management
+
– Digital signatures
+
– Encryption
+
– Firewalls
+
– Rights management
+
  
Conclusion:
+
== Obstacles==
  
• The threats are real and dangerous
+
* [[Authentication]]
• Recovery cost large
+
* Authorization
• We must shield ourselves in as many ways as possible with a reasonable loss of accessibility
+
* Integrity management
 +
* Digital signatures
 +
* [[Encryption]]
 +
* Firewalls
 +
* Rights management
  
References:
+
==Conclusion==
  
Introduction to Biomedical Informatics, William Hersh; 2007
+
The threats are real and dangerous and recovery costs are large. We must shield ourselves in as many ways as possible with a reasonable loss of accessibility
  
EHRs/NHII: HIPAA Security and EHRs, a Near Perfect Match by:
+
==References==
Margret Amatayakul, RHIA, CHPS, FHIMSS
+
<references/>
Steven S. Lazarus, PhD, FHIMSS
+
  
Privacy, information technology, and health care, Thomas C. Rindfleisch;1997.
+
# Introduction to Biomedical Informatics, William Hersh; 2007
+
# EHRs/NHII: HIPAA Security and EHRs, a Near Perfect Match by: Margret Amatayakul, RHIA, CHPS, FHIMSS Steven S. Lazarus, PhD, FHIMSS
Submitted by Dahlia Abd-Ellatif
+
# Privacy, information technology, and health care, Thomas C. Rindfleisch;1997.
[[category:BMI-512-W-08]]
+

Latest revision as of 20:15, 28 April 2015

Information security is maintaining confidentiality and availability simultaneously. Information should be hidden, safe, private, and also ready for immediate use.

Introduction

Computer equipment that handles or stores information needs to be protected from harm or unauthorized intrusion. Computer hardware, software, and tthe data stored on these systems is always potentially at risk. Information, especially medical information that is confidential, non-replaceable, or whose loss of would cost time and money must be protected from a variety of threats. The most common threats are natural disasters and hazards, computer failures, media failures, malicious attacks, and sometimes, ourselves.

If you look up the definition of “Information Security” on the Web, you will find a host of different interpretations (see below), many of them with questionable foundations. Strangely enough, the US Code probably contains the best definition:

US Code Title 44, Chapter 35, Subchapter III, § 3542[1]

(1) The term “information security” means protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide—

    (A) integrity, which means guarding against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity; 
    (B) confidentiality, which means preserving authorized restrictions on access and disclosure, including means for protecting personal privacy and proprietary information; and 
    (C) availability, which means ensuring timely and reliable access to and use of information.

This definition is based on the concept that a person, business or government will suffer harm if there is a loss of confidentiality, integrity or availability of information and that it is the role of information security to minimize the possibility that such harm will occur. Other commentators have tried to expand on this approach and argued that other elements should be added (see CERT[2] and Donn Parker[3]). These expansive approaches tend to create a confusing definition that detracts the user from focusing on harm or risk. In effect, they over complicate the issue. [4]

Information Security Goals

The four (4) primary goals of information security are:

  1. Confidentiality
  2. Integrity
  3. Availability
  4. Non-repudiation.

(Accomplishing these is a management issue before it's a technical one, as they are essentially business objectives.)


Confidentiality is about controlling access to files either in storage or in transit. This requires systems configuration or products (a technical job). But the critical definition of the parameters (who should be able to access what) is a business-related process.

Integrity is a matter of version control - making sure only the right people can change documents. It also requires an audit trail of the changes, and a fallback position in case changes prove detrimental. This meshes with non-repudiation (the change record must include who as well as what and when).

Availability is the Cinderella of information security as it is rarely discussed. But however safe from hackers your information is, it is no use if you can't get at it when you need to. So you need to think about data back-ups, bandwidth and standby facilities, which many people still leave out of their security planning.[5]

Electronic medical record security

Pros

EHRs can provide great privacy and security, e.g.,

  • Access controls can be more granular
  • Authentication mechanisms provide audit trails and non-repudiation
  • Disaster recovery plans assure greater availability
  • Encryption can provide confidentiality and data integrity

Cons

  • Information flows more easily, risk of mishap is greater
  • Collection of large volumes of data more feasible and risky
  • Sharing of information for treatment, payment, and operations misunderstood
  • New methods to attack data are continuously being developed

Flow of information in health care have many points to “leak”

Direct patient care:

  • Provider / Primary Care physician
  • Clinic Personnel/ Medical Staff
  • Hospital Admissions
  • Patient
  • Insurance company
  • Researchers
  • Employees / other hospital employees

Support activity:

  • Payers
  • Quality reviews
  • Administration

“Social” uses:

  • Insurance eligibility
  • Public health
  • Medical research

Commercial uses:

  • Marketing
  • Managed care
  • Drug usage

NB: Even de-identified data is not necessarily secure


The Shields:

1-Risk assessment

We should balance :

  • risk,
  • benefit,
  • cost and
  • loss of accessibility

2-Access Restriction

  • Authentication
  • Access Control
  • Accounting

Security Policies

We should set documented:

  • goals
  • procedures
  • organization
  • responsibilities

Technologies to secure information:

Deterrents

System management precautions

-Software management

-Analysis of vulnerability

Obstacles

Conclusion

The threats are real and dangerous and recovery costs are large. We must shield ourselves in as many ways as possible with a reasonable loss of accessibility

References

  1. US Code, http://www.law.cornell.edu/uscode/text/44/3542/
  2. US CERT WebPage, https://www.us-cert.gov/
  3. Donn Parker Biography, http://computer.org/computer-pioneers/pdfs/P/Parker%20Donn.pdf
  4. US Code Title 44, http://www.law.cornell.edu/uscode/text/44/3542
  5. Barwise, M. Four Goals of Security. http://www.computerweekly.com/opinion/Four-goals-of-security
  1. Introduction to Biomedical Informatics, William Hersh; 2007
  2. EHRs/NHII: HIPAA Security and EHRs, a Near Perfect Match by: Margret Amatayakul, RHIA, CHPS, FHIMSS Steven S. Lazarus, PhD, FHIMSS
  3. Privacy, information technology, and health care, Thomas C. Rindfleisch;1997.