{'fraction_non_alphanumeric': 0.020275162925416364, 'fraction_numerical': 0.0, 'mean_word_length': 4.831223628691983, '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}}
Unified RB-DAC Approach with Secure Authentication Using Smart Card Architecture

There has been recently considerable interest in Role-Based Access Control (RBAC) as an alternative to traditional DAC and MAC access control schemes. The interest in RBAC is due to its simplicity in implementation, since it adapts to the working environment of any organization effortlessly. Every cloud computing resource subjects are categorically divided into the predefined roles and policies are defined for each role. Hence the RBAC is defined as a mapping between user to roles and the roles to privileges making the access control design simple, adaptable and easily implementable. DAC scheme provides complete control to the owner of the object on the decision of access control using access control matrix and list. The problem in the present RBAC scheme is that all subjects who are in same role can access the data specified for that particular role, but we can't specify data for any particular subject in a particular role. Our system combines the concept of ACL (Access Control List) & ACM (Access Control Matrix) of DAC with the RBAC to enhance the data integrity in RBAC. Thus to achieve this, we have to add ACL to all the objects (data) and ACM to all the objects (roles) in the system, this restricts other subjects of the same role from accessing one particular subject's data.