A Standard Mutual Authentication Protocol for Cloud Computing Based Health Care System

Abstract

Telecare Medical Information System (TMIS) supports a standard platform to the patient for getting necessary medical treatment from the doctor(s) via Internet communication. Security protection is important for medical records (data) of the patients because of very sensitive information. Besides, patient anonymity is another most important property, which must be protected. Most recently, Chiou et al. suggested an authentication protocol for TMIS by utilizing the concept of cloud environment. They claimed that their protocol is patient anonymous and well security protected. We reviewed their protocol and found that it is completely insecure against patient anonymity. Further, the same protocol is not protected against mobile device stolen attack. In order to improve security level and complexity, we design a light weight authentication protocol for the same environment. Our security analysis ensures resilience of all possible security attacks. The performance of our protocol is relatively standard in comparison with the related previous research.

Cryptanalysis and improvement of a biometric‐based remote user authentication protocol usable in a multiserver environment

“…To evaluate execution time of our scheme with other existing schemes, the hash function, bio-hash function, symmetric key encryption or decryption operation, modular exponentiation operation, elliptic curve point multiplication, and bilinear operation take 0.0005, 0.02102, 0.0087, 0.522, 0.0503, and 0.0621 seconds, respectively. 59,60 As in the work of He et al, 68 the execution time for a fuzzy extractor function is near about equal to an elliptic curve point multiplication. The estimated computational time of the protocols of Amin and Biswas, 30 Irshad et al, 51 Li et al, 18 Maitra et al, 19 Li et al, 52 Lin et al, 53 Maitra and Giri, 54 Pippal et al, 16 Wen et al, 55 Yoon and Yoo, 56 and Amin and Biswas, 44 and our proposed protocol are 0.05404, 0.7684, 2.098, 0.0652, 0.4164, 0.2609, 0.0438, 3.658, 0.095, 0.2112, 0.98304, and 0.8701 seconds, respectively.…”

“…Our proposed protocol has computation costs 7 T h +2 T p m +1 T f e and 23 T h +13 T p m +1 T f e for the registration phase and the login and authentication phase, respectively, whereas the other schemes have 24 T h +2 T b h , 24 T h +12 T p m +6 T s +2 T f e , 20 T h +4 T m e , 26 T h +6 T s , 28 T h +6 T p m +2 T f e , 15 T h +4 T p m +6 T s , 18 T h +4 T s , 9 T h +7 T m e , 16 T h +10 T s , 20 T h +4 T p m , and 24 T h +16 T p m +2 T b p +2 T b h operations, respectively, for performing the registration phase and the authentication phase. To evaluate execution time of our scheme with other existing schemes, the hash function, bio‐hash function, symmetric key encryption or decryption operation, modular exponentiation operation, elliptic curve point multiplication, and bilinear operation take 0.0005, 0.02102, 0.0087, 0.522, 0.0503, and 0.0621 seconds, respectively . As in the work of He et al, the execution time for a fuzzy extractor function is near about equal to an elliptic curve point multiplication.…”

Mutual Authentication Protocol for D2D Communications in a Cloud-Based E-Health System

“…Mohit et al [6] and Chiou et al [7] considered a cloud server an auxiliary entity that stores patients' data, such as measures collected from sensors coupled to their bodies. Such data are encrypted and transmitted over public channels from the entities involved with the cloud server and vice versa, after the execution of mutual authentication and the generation of a session key.…”

Secure Data Encryption for Cloud-Based Human Care Services

“…Zhang et al [36] described survey results on searchable encryption schemes and proposed searchable encryption to provide security and privacy on healthcare applications. Mohit et al [37] proposed a mutual authentication protocol for a cloud-computingbased health care system. Mekala et al [38] proposed a homomorphic encryption technique for healthcare multicloud computing which uses the Dynamo DB and Amazon Web Services (AWS).…”