Overview

Important
Limited Access - This capability is enabled selectively for Orgs and is not available to all Prod Orgs.

Overview

Attribute-Based Access Control (ABAC) enhances the existing roles available in the platform to meet the evolving demands of complex systems. ABAC provides a more flexible and dynamic approach to control access by considering a wide range of contextual attributes. This addresses the need for fine-grained access control and enhanced security in organizations.

Only Org Admin can configure ABAC rules, policies, and custom roles.

Implementing Attribute-Based Access Control (ABAC)

The Attribute-Based Access Control (ABAC) implementation involves the following three steps:

• Step 1 - Create Rules: In ABAC, rules are formulated based on attributes associated with the projects, resources, and resource types. By creating rules, you define whether a specific action should be allowed or denied.

• Step 2 - Create Policies: Policies is a collection of one or more rules that is referenced as part of creation of Custom Roles.

• Step 3 - Custom Roles: A Custom Role configuration includes selection of a base role along with the necessary overlay ABAC policies.

ABAC Sequences

The sequence diagram below captures the high-level steps to create ABAC Rules, Policies, and Custom Roles.

Step 1: ABAC Roles

New Version Save Changes Add Rules Navigate to ABAC Rules Login to Console
Only Org Admin Mandatory: Version, Resources, and Resource Type From System menu Create new rule version Settings: General, Project Selector, and Resource Edit to add multiple versions.

Step 2: ABAC Policies

New Version Save Changes Add Policy Navigate to ABAC Policies
Mandatory: Version, Rule, and its versions Create new policy version Settings: General and ABAC Policy Rules Edit to add multiple versions.

Step 3: ABAC Custom Roles

Save Changes Add Role Navigate to ABAC Custom Roles
Mandatory: Name, Base Role Selection, Policies and its versions Create new role Settings: General, Base Role, and ABAC Policies.