liveBook · Manning

Attribute-based access control

Also called ABAC

Attribute-based access control is an authorization model that evaluates subject, resource, action, and contextual attributes against policies to make access decisions.

How 4 Manning books explain it

Authorization in Action

Attribute-based access control (ABAC) is an authorization approach that makes decisions by evaluating attributes of subjects, resources, actions, and contextual conditions against rules.

How it is used
Uses ABAC for fine-grained, context-sensitive enterprise authorization alongside broader role and relationship models.
How deep it goes
Explains attribute categories, runtime policy evaluation, architecture, layered constraints, and operational limitations.
Examples
Illustrates deployment clearance and on-call checks, financial-document access, and a managed-device constraint.
What you can do after
Apply it via Cedar by combining attribute constraints with other policy patterns and layering global restrictions.

Read how Authorization in Action explains attribute-based access control →

Software Security for Developers

An attribute-based access rule is a condition that grants or denies access by comparing relevant subject, resource, or environmental attributes.

How it is used
Uses user, resource, and environmental attributes to make fine-grained authorization decisions when predefined roles are insufficient.
How deep it goes
Defines attributes, gives matching-rule examples, and discusses monolith and service deployment, but defers policy-engine implementation details.
Examples
Uses department-matched documents, regional invoices, clearance levels, working hours, IP addresses, and inconsistent regional values.
What you can do after
Evaluate/understand it by choosing ABAC for dynamic, attribute-dependent access and identifying consistency risks across services.

Read how Software Security for Developers explains attribute-based access control →

Secure APIs

Attribute-based access control is an authorization model that determines permissions from attributes of users, resources, and contextual conditions.

How it is used
Determines API access by evaluating user attributes against requested data or operations.
How deep it goes
Explains token-derived identity, database lookups, hierarchical scopes, and business rules, while warning that complexity makes validation difficult.
Examples
Uses project-management scopes, geographical attributes, read/write functions, and bank-account verification tests.
What you can do after
Diagnose authorization failures by testing whether required user attributes and state conditions are enforced.

Read how Secure APIs explains attribute-based access control →

Architecting an Apache Iceberg Lakehouse

Attribute-based access control is an authorization technique that makes permission decisions from attributes of users, resources, actions, or context.

How it is used
Governs catalog permissions by evaluating user attributes when controlling access to tables and namespaces.
How deep it goes
Defines attribute-based decisions and architectural placement, but stops short of specifying policy syntax or enforcement implementation.
Examples
Uses department and location attributes to illustrate authorization decisions for catalog-managed tables and namespaces.
What you can do after
Evaluate catalog requirements and determine how attribute-based policies should integrate with identity systems and query-engine enforcement.

Read how Architecting an Apache Iceberg Lakehouse explains attribute-based access control →

Also covered in

What to know first

Related concepts

Questions about attribute-based access control

What is attribute-based access control?

Attribute-based access control is an authorization model that evaluates subject, resource, action, and contextual attributes against policies to make access decisions.

Which Manning books explain attribute-based access control?

Authorization in Action, Software Security for Developers, Secure APIs and Architecting an Apache Iceberg Lakehouse.

What should I know before learning attribute-based access control?

Manning books that teach attribute-based access control usually introduce authorization, identity and access management, metadata and JSON Web Token first.

What is the difference between attribute-based access control and role-based access control?

Attribute-based access control is an authorization model that evaluates subject, resource, action, and contextual attributes against policies to make access decisions. Role-based access control is an authorization model that assigns permissions to roles and grants users or other principals access through their assigned roles.

What is attribute-based access control a kind of?

Attribute-based access control is a kind of access control. Access control is the set of policies and mechanisms that determines which users or processes may access resources and what actions they may perform.

What is attribute-based access control also called?

Attribute-based access control is also called ABAC.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.