| Literature DB >> 32522216 |
Dong-Won Kim1, Jin-Young Choi1, Keun-Hee Han2.
Abstract
BACKGROUND: Infectious diseases that can cause epidemics, such as COVID-19, SARS-CoV, and MERS-CoV, constitute a major social issue, with healthcare providers fearing secondary, tertiary, and even quaternary infections. To alleviate this problem, telemedicine is increasingly being viewed as an effective means through which patients can be diagnosed and medications prescribed by doctors via untact Thus, concomitant with developments in information and communication technology (ICT), medical institutions have actively analyzed and applied ICT to medical systems to provide optimal medical services. However, with the convergence of these diverse technologies, various risks and security threats have emerged. To protect patients and improve telemedicine quality for patient safety, it is necessary to analyze these risks and security threats comprehensively and institute appropriate countermeasures.Entities:
Keywords: Medical information security; Smart medical security; Telecare security; Telemedicine security
Mesh:
Year: 2020 PMID: 32522216 PMCID: PMC7286211 DOI: 10.1186/s12911-020-01145-7
Source DB: PubMed Journal: BMC Med Inform Decis Mak ISSN: 1472-6947 Impact factor: 2.796
Fig. 1Telemedicine system architecture
Fig. 2Seven areas related to telemedicine security threats
Fig. 3Telemedicine home network
Fig. 4Telemedicine service provider
Fig. 5Attack tree
Fig. 6Telemedicine system risk assessment phase
Asset value evaluation criteria [19, 44, 49–52]
| Division | Low | Moderate | High |
|---|---|---|---|
| Confidentiality | 1 | 2 | 3 |
| Integrity | 1 | 2 | 3 |
| Availability | 1 | 2 | 3 |
| Asset contribution | 1 | 2 | 3 |
Categorization of asset values [19, 44, 49–52]
| Security objective | Potential impact | Description |
|---|---|---|
| Confidentiality | High | Should be available internally to authorized persons only; unauthorized exposure can result in harm to individual privacy and/or fatal damage to telemedicine system |
| Moderate | Can be disclosed internally but in case of external exposure may cause significant problems with respect to individual privacy and/or telemedicine system | |
| Low | If exposed to external persons, will have negligible effect on individual privacy and telemedicine system | |
| Integrity | High | Accidental or intentional changes may result in extreme harm to individual privacy or telemedicine system |
| Moderate | Accidental or intentional changes may cause significant damage to individual privacy or telemedicine system | |
| Low | Accidental or intentional changes will have negligible effect on individual privacy or telemedicine system | |
| Availability | High | Service interruption may cause fatal damage to operation of telemedicine system |
| Moderate | Service interruption may result in significant damage to telemedicine system | |
| Low | Service interruption will cause negligible damage to telemedicine system | |
| Asset Contribution | High | Asset is essential to telemedicine system services |
| Moderate | Asset is partially necessary for telemedicine system services | |
| Low | Asset plays a supporting role in telemedicine system services |
Definitions of grades for information classification [19, 44, 49–52]
| Importance grade | Total score | Description |
|---|---|---|
| 1 | 4–5 | May cause damage to assets but has almost no influence on telemedicine system |
| 2 | 6–7 | If asset is damaged, has little effect on related domain or system |
| 3 | 8–9 | Asset damage results in significant loss to telemedicine business |
| 4 | 10–11 | Asset damage leads to very significant loss to telemedicine business |
| 5 | 12 | Asset damage leads to very high loss to telemedicine business, which may stop functioning |
AOP evaluation criteria [51, 52]
| Division | Low | Moderate | High |
|---|---|---|---|
| 1 | 2 | 3 | |
| AOP | 1–50% | 51–80% | 81–100% |
Ratings for various aspects of attack potential [51, 52]
| Factor | Level | Value |
|---|---|---|
| Elapsed time | ≤1 day | 0 |
| ≤1 week | 1 | |
| ≤1 month | 4 | |
| ≤3 months | 10 | |
| ≤6 months | 17 | |
| > 6 months | 19 | |
| not practical | ∞ | |
| Expertise | Layman | 0 |
| Proficient | 3 | |
| Expert | 6 | |
| Multiple experts | 8 | |
| Knowledge of system | Public | 0 |
| Restricted | 3 | |
| Sensitive | 7 | |
| Critical | 11 | |
| Window of opportunity | Unnecessary/unlimited | 0 |
| Easy | 1 | |
| Moderate | 4 | |
| Difficult | 10 | |
| None | ∞ | |
| Equipment | Standard | 0 |
| Specialized | 4 | |
| Bespoke | 7 | |
| Multiple bespoke | 9 |
ASP ratings [51, 52]
| Values | Attack potential required to identify and exploit attack scenario | ASP |
|---|---|---|
| 0–9 | Basic | 5 |
| 10–13 | Enhanced-basic | 4 |
| 14–19 | Moderate | 3 |
| 20–24 | High | 2 |
| ≥25 | Beyond high | 1 |
Examples of ASP estimates [51, 52]
| Attack | Elapsed time | Expertise | Knowledge of system | Window of opportunity | Equipment | Required attack potential | |
|---|---|---|---|---|---|---|---|
| Sum | Rating | ||||||
| Leakage of patient information from telemedicine device | 0 | 6 | 7 | 4 | 4 | 21 | High |
| Forgery via wiretapping and spoofing | 0 | 3 | 0 | 4 | 4 | 11 | Moderate |
| MITM attacks using rogue AP | 0 | 6 | 3 | 10 | 4 | 23 | High |
| Health information sniffing | 0 | 0 | 0 | 4 | 4 | 8 | Basic |
RV ratings [51, 52]
| Values | Grade |
|---|---|
| 1–12 | Low |
| 13–32 | Normal |
| ≥33 | High |
Examples of telemedicine risk assessment estimates
| Asset | AV | Concern | AOP | ASP | RV | ||
|---|---|---|---|---|---|---|---|
| Telemedicine device | RTOS/ GPOS/ gateway | 5 | Patient information leakage | 1 | 2 | 10 | L |
| 5 | Weak password set | 2 | 5 | 50 | H | ||
| 5 | Critical information transmitted owing to device operation errors | 3 | 4 | 60 | H | ||
| 5 | Loss due to improper management of telemedicine device | 2 | 5 | 50 | H | ||
| 5 | Access to internal system used by unapproved device | 1 | 1 | 5 | L | ||
| 5 | Information leakage by device because of malware infection | 1 | 1 | 5 | L | ||
| 5 | Saving important information in device | 2 | 4 | 40 | H | ||
| 5 | Leakage of significant information from lost/stolen device | 2 | 4 | 40 | H | ||
| 5 | Access to internal system and disclosure of important information owing to application vulnerabilities of device | 2 | 4 | 40 | H | ||
| 5 | Device ↔ plaintext transmission between internal system | 3 | 5 | 75 | H | ||
| 5 | Device ↔ plaintext transmission between telemedicine system | 3 | 5 | 75 | H | ||
| 5 | Device ↔ MITM attacks between telemedicine system | 3 | 1 | 15 | M | ||
| 5 | Gateway ↔ plaintext transmission between internal system | 3 | 3 | 27 | M | ||
| 5 | Information leakage because of malware infection (vaccine or latest patch) | 1 | 2 | 10 | L | ||
| 5 | Significant information disclosure by gateway hacking | 2 | 1 | 10 | L | ||
| 5 | MITM attacks using rogue gateway | 2 | 1 | 10 | L | ||
| 5 | Significant information leakage from lost/stolen gateway device | 2 | 3 | 30 | M | ||
| PC | PC | 4 | Forgery via wiretapping and spoofing | 3 | 5 | 60 | H |
| 4 | Unauthorized access via MITM attacks | 2 | 3 | 24 | M | ||
| 4 | Gateway ↔ plaintext transmission between telemedicine system | 3 | 5 | 60 | H | ||
| 4 | MITM attacks using rogue AP | 2 | 1 | 8 | L | ||
| 4 | Information leakage because of malware infection (vaccine or latest patch) | 1 | 2 | 8 | L | ||
| 4 | Significant information disclosure owing to gateway hacking | 1 | 1 | 4 | L | ||
| 4 | Internal access to national communication networks by bypassing physical security controls | 1 | 1 | 4 | L | ||
| 4 | Internal access to national communication networks by exploiting wireless network vulnerability | 1 | 1 | 4 | L | ||
| 4 | Leaving working seat for a long period after logging in | 2 | 5 | 40 | H | ||
| 4 | Nonrepudiation failure by not saving accessed records | 1 | 5 | 20 | M | ||
| 4 | Accident due to telemedicine system operation errors | 1 | 5 | 20 | M | ||
| S/W | Telemedicine software | 4 | Access to internal system and important information disclosure by exploiting vulnerabilities of application used for telemedicine treatment | 1 | 1 | 4 | L |
| 4 | Access to internal system via update files for application used for telemedicine treatment | 1 | 1 | 4 | L | ||
| Data transmission software | 3 | Access to internal system and important information disclosure by exploiting vulnerability of application used for data transmission | 1 | 1 | 3 | L | |
| Patient medical information software | 3 | Access to internal system via update files for software | 2 | 1 | 6 | L | |
| Monitoring software | 2 | Access to internal system via update files for software | 2 | 1 | 4 | L | |
| ECG software | 5 | Access to internal system via update files for telemedicine system | 2 | 1 | 10 | L | |
| Information | Personal information | 4 | Sniffing | 3 | 3 | 36 | H |
| Health information | 4 | Health information sniffing | 3 | 3 | 36 | H | |
| Medical information | 5 | Sending invalid prescriptions by changing medical information during telemedicine treatment | 1 | 1 | 5 | L | |
| 5 | Misuse of medical information by analyzing network packets during telemedicine treatment | 2 | 1 | 10 | L | ||
| 5 | Accidents caused by telemedicine system operation errors | 2 | 5 | 50 | H | ||
| 5 | Forgery via network eavesdropping and spoofing during patient information exchange | 2 | 3 | 30 | H | ||
Fig. 7Example of a user or patient attack tree
Fig. 8Examples of RV estimates