Share E-Book
Scan to open this page

Scan with your phone to open this page

Author: Phil Windley

Improve security and standardize policy enforcement by automating authorization and access control! Stale permissions and manual access policy enforcement are a constant security risk. Dynamic authorization—automatic systems that eliminate permanent access grants and manual review-and-revise processes—can radically improve access control. This practical, focused book shows you how to switch from crude yes/no permissions to flexible, policy-driven rules that adapt instantly. Authorization in Action shows you how to: Establish RBAC, ABAC, and ReBAC for dynamic authorization Design adaptive access control policies Implement policy-based access control (PBAC) Integrate decision logic with organizational data Establish clear authorization governance structures Access control needs evolve as users require short-term data access, location-based services, temporary work assignments, or changing employment status. Dynamic authorization systems adapt access in real time. Authorization in Action presents a view of dynamic authorization that merges role-based, attribute-based, and relationship-based models into a single framework. You’ll learn exactly how dynamic authorization works, as well as the governance, architecture, and team structures necessary to sustain the approach in the enterprise. about the reader For IT workers, executives, directors, and product managers who know the basics of systems architecture. about the author Phil Windley is co-founder and organizer of the Internet Identity Workshop and Executive Director of the IIW Foundation, advancing human-centered digital identity. He was Founding Chair of the Sovrin Foundation (2016–2020) and most recently served as Senior Software Development Manager at AWS Identity.

AI Reading Assistant

Whole-book reading guide from stratified index samples; jump to passages in the text

AI guide
【One-Line Pitch】 A practical guide to replacing stale, static permissions with policy-based, real-time authorization that adapts to context, relationships, and business change. Best for identity architects, developers, product managers, and IT leaders who already know authentication basics and want to design and govern dynamic access control. 【Book Arc】 - **Opening (~0%–13%)**: Frames authorization as architecture, not a security checkbox, using the 2013 Target breach to show how weak access boundaries and poor visibility turn a minor compromise into catastrophe. - **Early (~13%–33%)**: Builds the conceptual foundation—digital identity as relationship management, the proximity problem, authentication vs. authorization, and why policy-based access control (PBAC) externalizes decision logic from application code. - **Middle (~33%–58%)**: Diagnoses the limits of static models (Unix permissions, ACLs, RBAC) across scalability, flexibility, maintainability, efficiency, auditability, Zero Trust, and consistency—showing where role proliferation and over-permissioning originate. - **Late (~58% onward)**: Moves toward dynamic authorization that merges role-, attribute-, and relationship-based models, with policy design, decision-logic integration, and governance structures (excerpts do not cover later chapters in detail). - **Ending (beyond excerpt coverage)**: Promises emerging challenges such as access control for AI agents and a full design-implement-govern arc across nineteen chapters, but the excerpts do not cover these final stages. 【Key Takeaways】 - **Authorization is architecture, not a checklist** (Early): Treating access control as a first-class design concern enables product features and security simultaneously, rather than bolting it on later. - **Digital identity exists to manage relationships** (Early): Systems must recognize, remember, and relate to entities—people, services, things, or AI agents—making identity foundational to both security and usability. - **Static authorization fails at scale** (Middle): ACLs, groups, and roles become unwieldy as principals, resources, and context multiply, forcing manual updates and workarounds. - **Context is the hard problem static lists cannot solve** (Middle): Time, location, device status, on-call status, and just-in-time elevation require runtime evaluation, not precomputed permissions. - **Role proliferation obscures accountability** (Middle): Special-purpose roles like "Contractor-Editor" accumulate, making it difficult to predict or audit who can access what. - **PBAC externalizes decision logic** (Early): Moving policy out of application code yields flexible, fine-grained, auditable decisions that are easier to author, maintain, and enforce consistently. - **Governance gaps create compliance risk** (Middle): Without a central policy view, business leaders cannot verify that their intent—such as GDPR data residency—is actually enforced. - **Zero Trust is impractical with static tools alone** (Middle): Retrofitting every system is expensive, so organizations settle for partial controls unless they adopt dynamic authorization. 【Reading Tips】 - Deep-read the early chapters on identity, relationships, and PBAC—they establish the vocabulary the rest of the book depends on. - Skim the static-authorization limitation sections if you already know RBAC/ACL pain points, but note the concrete failure scenarios (Target, EHR, multi-national retail) as ammunition for stakeholder buy-in. - Pay close attention to the ACME Corp case study threaded through the book; it converts abstract models into design decisions. - Treat governance and team-structure material as equally important as policy syntax—sustainable authorization depends on organizational alignment, not just engines. - Since this is a MEAP edition, expect later chapters on AI agents and advanced implementation to be less settled; verify against the final release. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first 58% of the book, primarily the opening, foundational, and static-authorization critique chapters. Later implementation, governance, and AI-agent material is referenced but not detailed in the excerpts.
Excerpt 1
ed as Senior Software Development Manager at AWS Identity. MEAP Edition Manning Early Access Program Authorization in Action Build policy-based access contro...
View in text
Page 7
ion—can turn a minor compromise into a catastrophic failure. The Target breach underscores the critical importance of not only knowing who is accessing your...
View in text
Page 9
access logic from sapplication code as shown in figure 1.1. Externalizing the logic allows for flexible, fine-grained, and auditable access decisions that ar...
View in text
Page 11
nurses, patients, administrators, and insurance processors. Doctors are allowed to update patient records, nurses can view and edit vitals and medications, a...
View in text
Page 13
efficient access management across diverse environments. 1.3 Authorization matters Most developers, product managers, technical managers, and business leader...
View in text
Page 15
ations require that employee access be sensitive to context. For example, the Health Insurance Portability and Accountability Act (HIPAA) mandates that acces...
View in text
Page 18
operly functioning managed devices when accessing them. 1.4.2 Policy as Data: Storing and managing access rules dynamically In contrast to Policy as Code, wh...
View in text
Page 20
cy as Code enforces strict policies based on best practices. Policy as Data allows real-time adjustments without changing policy. Auditability—Policy as Code...
View in text
Tags
AI categories
CybersecuritySoftwareTechnology
Publish Year: 2026
Language: English
Pages: 477
File Format: PDF
File Size: 19.0 MB
Text Preview (First 20 pages)
Registered users can read the full content for free

Register as a Gaohf Library member to read the complete e-book online for free and enjoy a better reading experience.

Generating text preview…