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

推荐订阅源

V
Visual Studio Blog
Stack Overflow Blog
Stack Overflow Blog
G
Google Developers Blog
Microsoft Azure Blog
Microsoft Azure Blog
Engineering at Meta
Engineering at Meta
L
LangChain Blog
T
The Blog of Author Tim Ferriss
J
Java Code Geeks
Y
Y Combinator Blog
月光博客
月光博客
雷峰网
雷峰网
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
F
Fortinet All Blogs
A
About on SuperTechFans
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
P
Proofpoint News Feed
小众软件
小众软件
H
Help Net Security
Last Week in AI
Last Week in AI
B
Blog RSS Feed
宝玉的分享
宝玉的分享
N
Netflix TechBlog - Medium
博客园 - 叶小钗
The GitHub Blog
The GitHub Blog

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 policy-based access control (PBAC)?
Alex Olivier · 2024-03-23 · via Cerbos - All Posts

Policy-Based Access Control (PBAC) is a method of managing user access to one or more systems. With PBAC, the organizational role of the user is combined with access policies to determine exactly what privileges the user should be granted. Unlike RBAC, Policy-Based Access Control is an ever-evolving type of access control necessitated by ever-evolving data usage needs.

With PBAC identifying information along with contextual factors such as roles, attributes and policies are used to determine whether or not a user should be provided access to certain resources. This enables a more dynamic policy enforcement and, among other things, provides a business with the ability to adjust on the fly and stay current with changing business or legal dynamics.

How it works

PBAC is a method of providing access to typically sensitive business assets based on a set of policies. Policy-Based Access Control typically weighs four kinds of attributes to determine if a user should be allowed to access the requested resource, and if so, what permissions they will have in regard to the resource. Those four types of attributes are:

  • Subject attributes: These may include the user’s job title and/or their department.
  • Object attributes: These are the attributes of the resource the user wishes to access.
  • Action attributes: These are the actions the user wishes to execute (reading, editing, sharing etc…).
  • Contextual attributes: These include date, time, location and other details related to the context in which the request is being made.

Access is granted in PBAC by weighing these attributes against system policies - which typically use “if, then” logic to assess an access request - and evaluating whether the request is legitimate. Access is only granted if all the conditions are satisfied.

Why is policy-based access control popular?

PBAC offers myriad advantages over other methods of access control such as RBAC and ABAC. These advantages include:

  • Real-time data protection: By providing fine-grain policy control over sensitive resources PBAC ensures those resources stay within their established boundaries.
  • Security compliance: With PBAC, companies have greater flexibility when it comes to enforcing compliance with SOC2, ISO27001 and other data handling standards and regulations.
  • Cost savings: PBAC enables you to establish centralized control over policies that ensures consistent enforcement across multiple applications. As a result, authorization policies can be reviewed and updated across the enterprise, reducing the costs normally associated with such activities. Policies can also be adjusted to reflect new requirements in real-time.