{'fraction_non_alphanumeric': 0.021438450899031812, 'fraction_numerical': 0.0, 'mean_word_length': 5.402654867256637, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Cryptographic Roles in the Age of Wikileaks: Implementation Models for Cryptographically Enforced RBAC

Role-based access control (RBAC) is the de facto access control model used in current information systems, also in military environments. This is because RBAC can be used to describe multi-level secure access control (AC) policies so common in military environments handling information from multiple levels of classification. Cryptographic access control (CAC), on the other hand, is an implementation paradigm intended to enforce AC policies cryptographically. CAC-methods are also attractive in military cloud and tactical environments due to their distributed and offline nature of operation. Combining the capabilities of both RBAC and CAC fully seems elusive, though. This paper studies the feasibility of implementing RBAC with respect to read-rights using a recent type of cryptographic schemes called attribute-based encryption (ABE). We present an implementation model based on the Extensible Access Control Markup Language (XACML) reference architecture and evaluate how the current state ABE can realize the different RBAC standard model components. We will show that it is feasible to implement at least the Core RBAC with standard XACML architecture and ABE models, and that the expressiveness of the ABE-schemes can reach nearly all the way in terms of symmetric RBAC commands and functions, such as Dynamic Separation of Duty.