惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Recent Announcements
Recent Announcements
J
Java Code Geeks
U
Unit 42
GbyAI
GbyAI
大猫的无限游戏
大猫的无限游戏
L
LangChain Blog
D
Docker
F
Fortinet All Blogs
N
Netflix TechBlog - Medium
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
罗磊的独立博客
I
InfoQ
The Cloudflare Blog
小众软件
小众软件
V
Visual Studio Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Engineering at Meta
Engineering at Meta
S
SegmentFault 最新的问题
爱范儿
爱范儿
Hugging Face - Blog
Hugging Face - Blog
P
Proofpoint News Feed
V
V2EX
月光博客
月光博客
Martin Fowler
Martin Fowler

Cerbos - All Posts

Authentik vs Keycloak: Self-hosted IdP comparison Mapping business requirements to authorization policy for automotive Fine-grained authorization for AI gateways EIC 2026: Stop counting agents, protect what they can touch Agent skill for writing authorization policies in Claude Desktop Identity security in 2026 EIC 2026 takeaways: the identity stack built for humans will not hold up for AI agents Already have authentication? Here's the authorization layer you still need. Tokens are authorization decisions: a guide to policy-driven token issuance What is a Runtime Authorization Platform It's a dimmer switch, not a kill switch. How CISOs are rethinking AI agent governance From maps to bitmaps (and from bitmaps to bitmaps) AuthZEN, Shared Signals, SCIM Events, IPSIE: Notes from the OpenID Enterprise Panel How do you update authorization policies without redeploying your application? IIW42 recap: Where agent authorization got real Cerbos PDP v0.52.0/v0.53.0: Engine performance, security hardening, and CEL path functions Authorization Management Platforms: what they do, how they work, and where they fit PocketOS AI coding agent deleted a production database in 9 seconds Non-Human Identity management still has a blind spot Supabase alternative in 2026: Best open source auth options Benefits of on-premise authorization: Why enterprises are moving toward self-hosted Authorization policies: How to write, test, and validate them (faster with AI) Agent skill for writing authorization policies How much does it cost to build authorization in-house? Why centralized authorization governance reduces incident response time OPA alternative Why AI agents make authorization a right now problem Modernizing legacy application authorization: why it’s your biggest security blind spot How to add authorization to legacy applications without code changes 5 authorization blind spots auditors find, and how to fix them
What is ABAC (Attribute-based access control)?
Alex Olivier · 2023-10-03 · via Cerbos - All Posts

Read on to understand what attribute-based access control is, the advantages of using ABAC, and it's key components.

What is attribute-based access control (ABAC)

Attribute-Based Access Control, also referred to as ABAC, is a method of managing access to systems or resources based on the user’s attributes. Compared to traditional access control methods it is considered to be more flexible and dynamic.

With Attribute-Based Access Control, access is allowed or prohibited based on an evaluation of various attributes defined within the access policy. These attributes typically include, but are not limited to, an individual’s department, location, and user role along with the context in which the access request is made.

Advantage of ABAC

Attribute-based access control is a flexible and comprehensive approach to access control. Instead of just looking at roles, ABAC considers multiple factors, or attributes of the user, which are: the resource, the environment, and the action.

Although ABAC is more complicated than RBAC, ABAC actually provides a high-degree of versatility and subtle control over system access.

ABAC is the way to go, in cases when versatility and security are of paramount importance.

Key components of the ABAC access control system

Attributes

Attributes are characteristics assigned to all the players in an access event that the system uses to determine whether access should be granted. Attributes typically take the form of information about the user, the resources the user is attempting to access and the context in which they are making their access request. So, for instance, access may be granted in one context but denied in a different context

Attributes can also be applied to the resources themselves, and can be based on a wide range of characteristics such as a file’s owner, its creation date, sensitivity of data and more.

Access request evaluations

Whenever a user requests access, the ABAC system evaluates that request by weighing the principal’s personal attributes along with which resources they are attempting to access and the context in which the request is being made.

Centralized policy management

More often than not, ABAC involves a centralized policy management system. The goal of such a system is to provide a uniform framework for defining and enforcing an organization’s access control policies.

Fine-grained access

When compared to more generalized access control models - typically referred to as "coarse-grained access" - the ABAC's fine grain-access model enables more nuanced control over who gains access to what. While this can make it somewhat more complex to devise and implement, many organizations relish the more sophisticated control.

Policies and access rules

Access rules are the main components that determine who can access resources and under what conditions.

Policies are where these access rules live; they are collections of rules, intended as a way to organize and manage access control within an organization.

Scalability

The fine-grained control provided by the ABAC model can be applied just as easily to mid-sized organizations as it can to multinational conglomerates.