Glossary/Security, Access & Deployment

Attribute-Based Access Control (ABAC)

Attribute-Based Access Control is an access model that grants permissions based on attributes of the user, resource, action, and environment, evaluated using policies rather than predefined roles.

ABAC makes access decisions by evaluating contextual attributes against defined policies. For example, an analytics platform might grant access only if the user's department is "Finance" AND the data classification is "Internal" AND the access occurs during business hours AND the user has passed security training. This approach handles complex, dynamic scenarios that role-based systems struggle with, particularly in large organizations where access requirements cross traditional organizational boundaries.

Compared to RBAC, ABAC is more flexible but also more complex to implement and maintain. It requires defining policy logic and ensuring consistent attribute values across user and resource systems. ABAC works especially well in analytics contexts where access must respond to data sensitivity levels, project membership, time-based restrictions, or geographic policies. Many organizations use ABAC layered on top of RBAC: RBAC handles basic organizational access patterns while ABAC enforces additional attribute-based constraints.

Key Characteristics

  • Evaluates multiple attributes (user, resource, action, environment) against defined policies
  • Supports dynamic, context-dependent access decisions
  • Requires consistent attribute management across systems
  • Scales effectively to handle complex organizational structures and cross-functional teams
  • Policy evaluation can be computationally intensive at scale
  • Demands clear governance of attribute definitions and policy ownership

Why It Matters

  • Handles complex access scenarios that rigid role structures cannot express
  • Reduces access granted by default by enforcing specific policy conditions
  • Adapts automatically when attributes change without requiring policy rewrites
  • Supports matrix organizations and cross-functional team structures
  • Enables fine-grained compliance controls like time-based or location-based restrictions
  • Reduces privilege escalation by restricting access to necessary attributes

Example

A healthcare organization uses ABAC to govern access to patient analytics. Access is granted only when: the user's role is "Clinical Researcher," the data classification is "Research," the study is approved by the ethics committee, access occurs from approved facilities, and the specific patient dataset is in the user's assigned studies. When a study is completed, removing the "approved" attribute automatically revokes access for all associated researchers.

Coginiti Perspective

Coginiti enables ABAC through flexible workspace policies and semantic model controls that restrict access based on user attributes, project membership, and data classification levels. Combined with row-level and column-level security controls on connected platforms, Coginiti enforces fine-grained attribute-based restrictions that adapt dynamically without requiring policy rewrites across all analytics tools.

See Semantic Intelligence in Action

Coginiti operationalizes business meaning across your entire data estate.