RBAC like it was meant to be
How we got from DAC (unix permissions, secret URL), to MAC (DRM, MFA, 2FA, SELinux), to RBAC. Details how the latter allows for better modeling of policies, ACLs, users and groups.
- from
- IAM
- added
- 2026-10-10
- likes
- 0
similar
-
The Case for Granular Permissions cerbos.dev
Discuss the limitations of RBAC and how ABAC (Attribute-Based Access Control) addresses them.
-
How to Implement Role-Based Access Control (RBAC) Authorization in Golang permit.io
A guide to implementing Role-Based Access Control (RBAC) in Golang, including code examples, covering various methods to secure app endpoints with role-based authorization.
-
AWS IAM Roles, a tale of unnecessary complexity infosec.rodeo
The history of fast-growing AWS explains how the current scheme came to be, and how it compares to GCP's resource hierarchy.
-
rbacr github.com
Role-Based Access Control system with a clean, type-safe DSL for roles, privileges, and authorization logic
-
RAML (⭐3.8k) github.com
A RESTful API Modeling Language that allows software engineers to design and create efficient APIs by modeling resources, endpoints, and interactions.
-
The never-ending product requirements of user authorization alexolivier.me
How a simple authorization model based on roles is not enough and gets complicated fast due to product packaging, data locality, enterprise organizations and compliance.
IAM › Authorization > Policy models: “How we got from DAC (unix permissions, secret URL), to MAC (DRM, MFA, 2FA, SELinux), to RBAC. Details how the latter allows for better modeling of policies, ACLs, users and groups.”