Kontrol akses berbasis peran data (RBAC data) adalah model keamanan yang membatasi akses pengguna ke data berdasarkan peran pengguna dalam organisasi. Dengan RBAC data, administrator dapat menentukan cakupan dan menetapkannya kepada pengguna untuk membantu memastikan bahwa pengguna hanya dapat mengakses data yang diperlukan untuk fungsi tugas mereka.
RBAC data dan RBAC fitur sering digunakan bersama untuk menyediakan sistem kontrol akses yang komprehensif. Perbedaannya adalah sebagai berikut:
RBAC fitur mengontrol akses ke fitur atau fungsi tertentu dalam sistem. RBAC fitur menentukan fitur mana yang dapat diakses oleh pengguna berdasarkan perannya.
RBAC data mengontrol akses ke data atau informasi tertentu dalam sistem. RBAC data mengontrol akses pengguna untuk melihat dan
memodifikasi data berdasarkan peran mereka.
Misalnya, pengguna mungkin diizinkan untuk
mengakses fitur tertentu (RBAC fitur) dan dalam fitur tersebut, aksesnya
ke data tertentu mungkin lebih dibatasi berdasarkan perannya (RBAC data).
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-21 UTC."],[[["\u003cp\u003eData RBAC (role-based access control) restricts user access to data based on their organizational roles, ensuring they can only access data necessary for their job.\u003c/p\u003e\n"],["\u003cp\u003eData RBAC works in conjunction with feature RBAC, where feature RBAC controls access to system functionalities, and data RBAC controls access to specific data within those features.\u003c/p\u003e\n"],["\u003cp\u003eData RBAC allows administrators to define scopes and assign them to users, enabling granular control over data visibility and modification rights.\u003c/p\u003e\n"],["\u003cp\u003eData RBAC is supported in Google SecOps, with resources available to understand, set up, and evaluate its impact on features.\u003c/p\u003e\n"]]],[],null,["# Introduction to data RBAC\n=========================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n\n*Data role-based access control* (*data RBAC*) is a security model that\nrestricts user access to data based on the user's roles within an\norganization. With data RBAC, administrators can define scopes and assign them\nto users to help ensure that users can access only the necessary data for their job\nfunctions.\n\nData RBAC and feature RBAC are often used together to provide a comprehensive\naccess control system. The differences are the following:\n\n- Feature RBAC controls access to specific features or\n functionalities within a system. Feature RBAC determines which features are accessible to\n users based on their roles.\n\n- Data RBAC controls access to specific data or\n information within a system. Data RBAC controls user access to view and\n modify data based on their roles.\n\nFor example, a user might be allowed to\naccess a specific feature (feature RBAC) and within that feature, their access\nto specific data might be further restricted based on their role (data RBAC).\n\nTo understand how data RBAC works, see [Overview of Data RBAC](/chronicle/docs/administration/datarbac-overview).\n\nFor information about the data RBAC impact on features, see [Data RBAC impact on features](/chronicle/docs/administration/datarbac-impact).\n\nTo get started with configuring data RBAC, see [Configure data RBAC](/chronicle/docs/administration/configure-datarbac-users).\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
