OPA

If you already run OPA, AI agents don't require a new policy engine — they require a richer input schema, ephemeral identity, and enforcement at every layer. Learn how to evolve your OPA setup for delegated, multi-hop agentic authorization with Zero Standing Permissions, production-grade Rego, and OPAL-backed real-time enforcement.

Learn how Open Policy Agent (OPA) is revolutionizing the way developers approach authorization. From managing policies with Rego to handling complex relationship-based access control (ReBAC) scenarios, discover practical OPA strategies, advanced use cases, and real-world insights.

Learn about database permissions and authorization, exploring data filtering strategies like application-level checks, PDP filtering, and partial evaluation to enhance security, performance, and scalability for managing user access.

Explore the Policy Engines Showdown: OPA vs. OpenFGA vs. Cedar – Dive into the strengths, trade-offs, and use cases of leading policy engines. Discover how OPA compares to OpenFGA and Cedar for authorization, scalability, and adoption.

Learn about Policy as Code, its use cases, and challenges from leading software developers. Discover tools and frameworks for policy as code implementation, and dive into policy languages like Rego, Cedar, and OpenFGA.

Learn how AI identity security is reshaping Identity and Access Management (IAM) and how to tackle these changes with proactive identity security.

Learn about the benefits of policy and code, the challenges presented by OPA's Rego and Policy-as-Graph, and possible solutions.

Open Policy Administration Layer (OPAL) is an open-source administration layer for OPA and AWS' Cedar Agent that allows you to keep your authorization layer up-to-date in real time

Discover the possible tradeoffs when building fine-grained authorization (FGA). Learn from a real-world use case how to examine such tradeoffs and build better software.

Learn how to implement hybrid cloud security using the multi-layer approach. Explore best practices with practical examples of IAM security and authorization.

Attribute-Based Access Control (ABAC) and Relationship-Based Access Control (ReBAC) - how to make the most suitable choice for your application?

Policy languages and frameworks like OPA, Cedar, and OpenFGA are rising in popularity. Explore the solutions they provide, and the benefits of using them.

Get ready to rumble! Join us on a quest to find the best authorization policy model in an epic battle royale: RBAC vs. ABAC vs. ReBAC

Learn how to implement Relationship-Based Access Control (ReBAC) with OPA - an open source policy engine for controlling access to systems and resources.

Choosing the right policy agent to handle your authorization is not a simple task - each offers its benefits and has its drawbacks. How to choose? Read here.

Graph-based or policy-as-code? Explore access control systems in this comparative analysis. Discover pros, cons, and a hybrid solution.

What are the benefits of policy as code, and how does OPA's Rego language differ from AWS' new Cedar policy language?

How Netflix solved the challenge of authorizing millions of users by using OPA, how you can adopt this solution, and possibly create something even better

IAM is huge in DevSecOps, with seemingly infinite buzzwords and terms. Here are the main ones every engineer and security professional should know.

Kong is a popular API gateway, but managing access to its APIs and services is hard - especially when required advanced permissions models like RBAC/ABAC/ReBAC

An Intellyx BrainBlog for Permit.io by Jason English

A view of OPAL + OPA as an alternative to XACML

A guide to figuring out which data fetching method is best for you, with full knowledge of each method’s ‘Good, Bad, and Ugly’ aspects.

How to Build The Right App Authorization Solution - An Intro to Open Policy Agent

The Bikini Bottom guide to ABAC authorization models and their implementation with OPA

The Bikini Bottom guide to RBAC authorization models and their implementation with OPA

Cloud-native / microservice-based products are complex. Building access control and managing permissions for them is only getting worse by the pull request.