Abstract

AbstractRole Back Access Control model (RBAC) allows devices to access cloud services after authentication of requests. However, it does not give priority in Big Data to devices located in certain geolocations. Regarding the crisis in a specific region, RBAC did not provide a facility to give priority access to such geolocations. In this paper, we planned to incorporate Location Time‐ (GEOTime) based condition alongside Priority Attribute role‐based access control model (PARBAC), so requesters can be allowed/prevented from access based on their location and time. The priority concept helped to improve the performance of the existing access model. TIME‐PARBAC also ensures service priorities based on geographical condition. For this purpose, the session is encrypted using a secret key. The secret key is created by mapping location, time, speed, acceleration and other information into a unique number, that is, K(Unique_Value) = location, time, speed, accelerator, other information. Spatial entities are used to model objects, user position, and geographically bounded roles. The role is activated based on the position and attributes of the user. To enhance usability and flexibility, we designed a role schema to include the name of the role and the type of role associated with the logical position and the rest of the PARBAC model proposed using official documentation available on the website for Azure internet of things (IoT) Cloud. The implementation results utilizing a health use case signified the importance of geology, time, priority and attribute parameters with supporting features to improve the flexibility of the existing access control model in the IoT Cloud.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call