ERBAC : Encrypted Role Based Access Control
SECURITY AND PRIVACY · 2026-05 · 9 (3)
DOI: 10.1002/spy2.70222 ↗Kurz gefasst
Fachartikel in der Zeitschrift SECURITY AND PRIVACY, online erschienen am 03.05.2026. Verfasst von Karunamoy Maji und 2 weiteren Autor:innen. Die Arbeit nennt 36 Literaturangaben.
Abstract (Originalsprache)
Leading enterprises typically choose for a centralized, large‐scale database storage system. Data security is crucial for communication and database preservation. The principal issue is governing unauthorized access to the database. Role‐based access control (RBAC) is a recognized approach for maintaining confidentiality in database systems. Nevertheless, System Administrators (SA) and Database Administrators (DBA) can obtain critical information even within the RBAC architecture. An approach based on encryption has been developed to address this issue. The primary concern is the secure distribution of keys among individuals with shared data access and a group of individuals needing access to shared data, viewed as having a common objective. We have instituted row‐level security (RLS) in database design to establish safe access control, called Encrypted Role‐Based Access Control (ERBAC). Additionally, we deployed Enterprise Resource Planning (ERP) systems, which are essential applications where security concerns are critical. ERBAC integrates effortlessly with an operational ERP system. We offer security, performance analysis, and encrypted query processing for role‐based encrypted data storage when the database contains identical data in many forms.
Zitieren
APA
Maji, K., Mandal, C., & Mitra, P. (2026). ERBAC : Encrypted Role Based Access Control. SECURITY AND PRIVACY, 9(3). https://doi.org/10.1002/spy2.70222
Vancouver
Maji K, Mandal C, Mitra P. ERBAC : Encrypted Role Based Access Control. SECURITY AND PRIVACY. 2026;9(3). doi:10.1002/spy2.70222
BibTeX
@article{Maji2026,
author = {Maji, Karunamoy and Mandal, Chittaranjan and Mitra, Pabitra},
title = {ERBAC : Encrypted Role Based Access Control},
journal = {SECURITY AND PRIVACY},
year = {2026},
volume = {9},
number = {3},
doi = {10.1002/spy2.70222}
}
EUVIMED