Vis enkel innførsel

dc.contributor.authorMsgna, Mehari Gebrehaweriya
dc.contributor.authorKatsikas, Sokratis
dc.contributor.authorGkioulos, Vasileios
dc.date.accessioned2023-03-31T08:36:19Z
dc.date.available2023-03-31T08:36:19Z
dc.date.created2022-01-19T07:35:08Z
dc.date.issued2022
dc.identifier.isbn9783030937461
dc.identifier.urihttps://hdl.handle.net/11250/3061341
dc.description.abstractAuthenticating a user the correct way is paramount to IT systems, where the risk is growing more and more in number and complexity. This is specially important in mobile phones, where a number of applications require continuous device authentication following the Point-of-Entry user authentication. Existing common approach in systems that require strict security rules and regulations is to use a One-Time-Password (OTP). Usually the OTP is generated using a special hardware device or another application that is synchronised with the back-end system. Another approach is to use SMS based activation/approval codes such as used by Telegram, Facebook, Twitter and other social media platforms. However, this approach has three major drawbacks: (1) it requires active user participation/interaction which could be annoying if repeated continuously, (2) SMS messages can be accessed by service provider’s employees, and (3) it does not consider the authenticity of the device from which the services are being accessed. The later is particularly serious as access sessions can be hijacked by malicious entities. In this paper, we investigate the possibility of using the user’s address book (contacts list) to continuously authenticate the device to ensure the services are only accessed from the mobile phone that belongs to the legitimate user. We call this authentication the Who-You-Know (WYK) scheme. For our research, we developed three components, the WYK-Mobile-Service, WYK-API-Server and a Mobile-Demo-Application. The WYK-API-Server exposes a set of authentication server APIs and the WYK-Mobile-Service consumes these APIs to authenticate the device every time the mobile applications are launched and make a request to the API server. Finally, the Mobile-Demo-Application will extract user’s data from the server if the device is successfully authenticated.en_US
dc.language.isoengen_US
dc.publisherSpringeren_US
dc.relation.ispartofEmerging Technologies for Authorization and Authentication 4th International Workshop, ETAA 2021, Darmstadt, Germany, October 8, 2021, Revised Selected Papers
dc.titleWYK: Mobile Device Authentication Using the User’s Address Booken_US
dc.title.alternativeWYK: Mobile Device Authentication Using the User’s Address Booken_US
dc.typeChapteren_US
dc.description.versionacceptedVersionen_US
dc.identifier.doi10.1007/978-3-030-93747-8_1
dc.identifier.cristin1984225
cristin.ispublishedtrue
cristin.fulltextpostprint
cristin.qualitycode1


Tilhørende fil(er)

Thumbnail

Denne innførselen finnes i følgende samling(er)

Vis enkel innførsel