FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2287674310> ?p ?o ?g. }

• W2287674310 endingPage "107" @default.
• W2287674310 startingPage "99" @default.
• W2287674310 abstract "Abstract—Enabling the healthcare infrastructure with In-ternet of Things (IoT) will significantly improve quality ofservice, reduce the costs and efficiently manage remote andmobile patients. To be efficacious, IoT and eHealth infrastruc-ture essentials as well as their associated security and privacyissues should be thoroughly recognized to effectively manage theInfoSec risks involved. Unfortunately, there has been a potentiallack of research comprehensively addressing these issues jointlywhile InfoSec risk management solutions are devised for IoT-based eHealth. In this paper, we have highlighted the necessaryknowledge while approaching InfoSec risk management in IoT-eHealth as per a standard process, assessed it against standardand proposed requirements and identified the current trends andgaps to set directions for future research.Keywords—Internet of Things (IoT); Remote Patient Monitor-ing; Risk Management; Security & Privacy; eHealth. I. I NTRODUCTION Internet of Things (IoT) is a global internet architectureconnecting various wired and wireless technologies designedto meet specific objectives [1]. Beside its anticipated benefits invarious private and business domains, enabling IoT in welfarespheres, such as healthcare, will greatly facilitate the societyas a whole. A patient can now be monitored remotely ina continuous fashion thus making the health services moremobile, extendable and effective. Though offering a great dealof benefits, IoT is still facing a number of critical challengessuch as networking, security and privacy, QoS, standardization,etc., which needs to be sorted out and yet remain open [2].Among these challenges, the most threatening are the securityand privacy concerns. Connecting diverse technologies maylead to new threats with much grander risk of security. Thesethreats become more drastic when considered in the contextof a continuous service, such as healthcare, where the concernis not limited to a patient’s privacy but, there is a threat to thebreach of trust, leading to the exploitation of a welfare service.Standards, guidelines and good practices concerning In-foSec Risk Management (ISRM), such as ISO 27005, NIST,CRAMM, ISACA RiskIT, etc., recommend to approach ISRMin a methodological fashion, i.e., understand the target businessfunction, service or system, identify the security and privacy(S&P) concerns and threats, analyze the risk faced, and managethe risk to reduce it to an acceptable level. To qualify this pro-cess, IoT-driven eHealth as a continuous real-time service willneed an intelligent security system that can dynamically predictand estimate the risk faced and mitigating it autonomously tobe more resilient and adaptable in the face of changing securitythreats [3]. A number of architectural designs, security issues,risk management (RM) models and surveys are presentedconcerning eHealth [1], [2], [4]–[7]. However, such studiesare either focused on the mentioned individual topics, targeta specific technology or presents abstract modeling. Hence,there is a lack of literature that provides a holistic study ofthe related topics as per the standard RM process to approachISRM in IoT-based eHealth.In this paper, we will highlight IoT-eHealth infrastructureessentials, the associated S&P issues and will explore variousISRM approaches to establish an understanding of how ISRMcan be modeled in IoT driven eHealth. Existing literatureis evaluated against standard and projected requirements andcurrent trends and gaps are identified. We identified that thecurrent system and S&P modeling are focused only on theprimitive requirements and is done in an empirical manner.Whereas vital operations, key system components and neces-sary S&P services are overlooked. Suitability of various ISRMmodels and methods is explored and it was concluded thatmost of them have a subjective influence which makes themdifficult to be adopted in a dynamic-real-time environmentsand lacks intelligent risk analysis and management capabilities,such as context awareness and self-adaptation, which aredeemed to be essential for IoT driven eHealth [3]. We stronglybelieve that this contribution will provide a reference pointfor future researchers and will enable them to understandthe requirements, challenges, options, methods and techniquesnecessary to consider while approaching ISRM in IoT driveneHealth.The rest of the paper is organized as follow: In Section II,an overview of the related work will be highlighted. Section IIIwill elaborate the current literature highlighting architecturaldesigns, S&P services, issues and threats and modeling secu-rity risks in the perspective of IoT-based eHealth. In SectionIV, evaluation of the current literature will be highlighted byaligning them with a set of standard and proposed require-ments. In Section V, current trends and gaps will be identifiedby discussing the evaluated knowledge. Finally, concludingremarks and future research endeavors will be underlined inSection VI.II. R" @default.
• W2287674310 created "2016-06-24" @default.
• W2287674310 creator A5007276490 @default.
• W2287674310 creator A5035646995 @default.
• W2287674310 date "2013-11-17" @default.
• W2287674310 modified "2023-09-30" @default.
• W2287674310 title "An Empirical Research on InfoSec Risk Management in IoT-based eHealth" @default.
• W2287674310 cites W1409618541 @default.
• W2287674310 cites W1558089875 @default.
• W2287674310 cites W162778990 @default.
• W2287674310 cites W187902790 @default.
• W2287674310 cites W1966959421 @default.
• W2287674310 cites W1967561194 @default.
• W2287674310 cites W1971350314 @default.
• W2287674310 cites W1984961057 @default.
• W2287674310 cites W1991948390 @default.
• W2287674310 cites W1992595252 @default.
• W2287674310 cites W1997545358 @default.
• W2287674310 cites W2006958567 @default.
• W2287674310 cites W2011483500 @default.
• W2287674310 cites W2018222233 @default.
• W2287674310 cites W2024834490 @default.
• W2287674310 cites W2029384299 @default.
• W2287674310 cites W2038825059 @default.
• W2287674310 cites W2079603347 @default.
• W2287674310 cites W2081754796 @default.
• W2287674310 cites W2086384654 @default.
• W2287674310 cites W2098727156 @default.
• W2287674310 cites W2099794868 @default.
• W2287674310 cites W2102859083 @default.
• W2287674310 cites W2105103777 @default.
• W2287674310 cites W2118672770 @default.
• W2287674310 cites W2125936181 @default.
• W2287674310 cites W2127158876 @default.
• W2287674310 cites W2128232860 @default.
• W2287674310 cites W2128381560 @default.
• W2287674310 cites W2134466149 @default.
• W2287674310 cites W2138029461 @default.
• W2287674310 cites W2139657587 @default.
• W2287674310 cites W2139824794 @default.
• W2287674310 cites W2144423176 @default.
• W2287674310 cites W2149577166 @default.
• W2287674310 cites W2159269282 @default.
• W2287674310 cites W2159456336 @default.
• W2287674310 cites W2162537638 @default.
• W2287674310 cites W2171397272 @default.
• W2287674310 cites W2180813244 @default.
• W2287674310 cites W2246268386 @default.
• W2287674310 cites W2343373042 @default.
• W2287674310 cites W2535627876 @default.
• W2287674310 hasPublicationYear "2013" @default.
• W2287674310 type Work @default.
• W2287674310 sameAs 2287674310 @default.
• W2287674310 citedByCount "0" @default.
• W2287674310 crossrefType "book-chapter" @default.
• W2287674310 hasAuthorship W2287674310A5007276490 @default.
• W2287674310 hasAuthorship W2287674310A5035646995 @default.
• W2287674310 hasConcept C10138342 @default.
• W2287674310 hasConcept C108827166 @default.
• W2287674310 hasConcept C111472728 @default.
• W2287674310 hasConcept C111919701 @default.
• W2287674310 hasConcept C112930515 @default.
• W2287674310 hasConcept C138885662 @default.
• W2287674310 hasConcept C144133560 @default.
• W2287674310 hasConcept C160735492 @default.
• W2287674310 hasConcept C162324750 @default.
• W2287674310 hasConcept C188087704 @default.
• W2287674310 hasConcept C202645933 @default.
• W2287674310 hasConcept C2779530757 @default.
• W2287674310 hasConcept C32896092 @default.
• W2287674310 hasConcept C38652104 @default.
• W2287674310 hasConcept C41008148 @default.
• W2287674310 hasConcept C50522688 @default.
• W2287674310 hasConcept C81860439 @default.
• W2287674310 hasConcept C98045186 @default.
• W2287674310 hasConceptScore W2287674310C10138342 @default.
• W2287674310 hasConceptScore W2287674310C108827166 @default.
• W2287674310 hasConceptScore W2287674310C111472728 @default.
• W2287674310 hasConceptScore W2287674310C111919701 @default.
• W2287674310 hasConceptScore W2287674310C112930515 @default.
• W2287674310 hasConceptScore W2287674310C138885662 @default.
• W2287674310 hasConceptScore W2287674310C144133560 @default.
• W2287674310 hasConceptScore W2287674310C160735492 @default.
• W2287674310 hasConceptScore W2287674310C162324750 @default.
• W2287674310 hasConceptScore W2287674310C188087704 @default.
• W2287674310 hasConceptScore W2287674310C202645933 @default.
• W2287674310 hasConceptScore W2287674310C2779530757 @default.
• W2287674310 hasConceptScore W2287674310C32896092 @default.
• W2287674310 hasConceptScore W2287674310C38652104 @default.
• W2287674310 hasConceptScore W2287674310C41008148 @default.
• W2287674310 hasConceptScore W2287674310C50522688 @default.
• W2287674310 hasConceptScore W2287674310C81860439 @default.
• W2287674310 hasConceptScore W2287674310C98045186 @default.
• W2287674310 hasLocation W22876743101 @default.
• W2287674310 hasOpenAccess W2287674310 @default.
• W2287674310 hasPrimaryLocation W22876743101 @default.
• W2287674310 hasRelatedWork W2228136528 @default.
• W2287674310 hasRelatedWork W2618181306 @default.

• next