2013
DOI: 10.1002/sec.879
|View full text |Cite
|
Sign up to set email alerts
|

Enforcing mobile security with location-aware role-based access control

Abstract: This paper describes how location-aware role-based access control (RBAC) can be implemented on top of the Geospatial eXtensible Access Control Markup Language (GeoXACML). It furthermore sketches how spatial separation of duty constraints (both static and dynamic) can be implemented using GeoXACML on top of the XACML RBAC profile. The solution uses physical addressing of geographical locations, which facilitates easy deployment of authorisation profiles to the mobile device. Location-aware RBAC can be used to i… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2015
2015
2021
2021

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(1 citation statement)
references
References 18 publications
0
1
0
Order By: Relevance
“…One promising approach to BYOD security is to use context-aware policies, which enforce access control based on devices' runtime context [62]. For instance, a policy may deny access from devices whose TLS libraries have not been updated [105], or grant access to devices that are physically located in the enterprise boundary [95], or only allow the use of a sensitive service only if administrators are online [59,94]. In each of these scenarios, we desire to make security decisions based on additional "threat signals", such as the device location, library version, or even the status of other devices in the network.…”
Section: Introductionmentioning
confidence: 99%
“…One promising approach to BYOD security is to use context-aware policies, which enforce access control based on devices' runtime context [62]. For instance, a policy may deny access from devices whose TLS libraries have not been updated [105], or grant access to devices that are physically located in the enterprise boundary [95], or only allow the use of a sensitive service only if administrators are online [59,94]. In each of these scenarios, we desire to make security decisions based on additional "threat signals", such as the device location, library version, or even the status of other devices in the network.…”
Section: Introductionmentioning
confidence: 99%