Data governance in Data 360 provides a robust framework for securing and managing data through the combined use of tags, classifications, user attributes, and policy-based governance. It helps make sure that the right people can get the right data, at the right time. It also helps with privacy, data security, compliance, size, consistency, and adaptability.
All customers (whether new or existing) will receive an “Allow All” policy for their Data 360 objects. However, to enable granular control, system admins must create and assign access policies for their users.
The Data Governance features will follow a staggered release starting July 21.
With data governance in Data 360, you can control access to data by using: Role-based Access Control (RBAC), Attribute-based Access Control (ABAC), or Allow All Access.
Role-Based Access Control (RBAC)
RBAC allows you to manage data access by assigning permissions to users based on their roles. In Data 360, you can use RBAC to grant access to specific data objects, such as data lake objects (DLOs), data model objects (DMOs), and calculated insight objects (CIOs), within a data space through permission sets. When using RBAC, access is assigned to individual objects.
Attribute-Based Access Control (ABAC)
ABAC grants or denies access to data based on a combination of attributes belonging to the user and the data. This method provides fine-grained control based on data context. To implement ABAC policies, you'll be required to tag object, field, and rows and assign custom permissions to users.
Allow Access to All Object in Data Space (Based on Data Space Permissions)
If users don’t require granular access control, an Allow All policy grants access based on permission set and data space assignments. The Allow All policy is created by default in Data 360 orgs. It preserves current access behavior based on data space assignment through permission sets, without requiring any action from admins.
To set up access, grant users access to the data space and to required Data 360 objects.
1. Associate a Permission Set to a Data Space
Grant access to Data Space by associating it to the permission set for a feature.
2. Identify Impacted Objects
Identify all associated objects (DLOs, DMOs, CIOs, UDMOs) you need to grant permissions. This can be found in the feature documentation. *You must grant access to objects in each data space. Object names in non default Data Space follow the convention of <DataSpace Prefix>_<Object Name>.
3. Grant Access to Data 360 Objects
Then identify the policy needed (ABAC, RBAC). Based on the policy, follow the associated steps. See Assign Data Access for more information.
005094232

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.