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

推荐订阅源

N
Netflix TechBlog - Medium
T
The Blog of Author Tim Ferriss
aimingoo的专栏
aimingoo的专栏
A
About on SuperTechFans
Stack Overflow Blog
Stack Overflow Blog
B
Blog RSS Feed
Microsoft Security Blog
Microsoft Security Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
人人都是产品经理
人人都是产品经理
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
J
Java Code Geeks
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
B
Blog
MongoDB | Blog
MongoDB | Blog
L
LangChain Blog
WordPress大学
WordPress大学
小众软件
小众软件
IT之家
IT之家
腾讯CDC
月光博客
月光博客
量子位
Blog — PlanetScale
Blog — PlanetScale
P
Proofpoint News Feed
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

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
Cerbos Hub Playground: Recent updates
Alex Olivier · 2026-02-06 · via Cerbos - All Posts

The Cerbos Hub Playground has seen a steady stream of improvements over the past few months, transforming it from a simple policy testing tool into a full-featured authorization development environment.

Here's a rundown of everything that's shipped.

Permissions matrix view

Permissions matrix view.png

Testing individual requests is useful, but understanding the full picture of who can do what across your system requires a broader view. The playground now includes a matrix check view that displays permission evaluation results in a comprehensive grid format. Select your principals, resources, and actions, and the matrix renders the complete set of authorization outcomes. This is particularly useful during demos and policy reviews where stakeholders need to see the overall access landscape at a glance.

README support

Playgrounds are increasingly used as shareable examples — for onboarding new team members, demonstrating authorization patterns, or collaborating on policy designs. To support this, playgrounds now render README.md files as formatted markdown when opened. READMEs can include relative links to other files in the playground and external links (shown with a confirmation dialog). When a playground has a README and no file is selected, it displays automatically, giving visitors immediate context about what they're looking at.

Create a playground from a store

One of the most requested features: you can now create a playground directly from an existing policy store. This lets you pull your production policies into an isolated sandbox where you can experiment freely without affecting live authorization decisions. It's also a quick way to use an existing store as a starting point when developing new policies, saving you from rebuilding complex policy structures from scratch.

Test case output diff view

When a test case fails, understanding why it failed is half the battle. The playground now provides a side-by-side diff comparing expected output with actual output. The visual comparison highlights the specific differences — whether it's a missing permission, an unexpected denial, or an incorrect output value — so you can quickly identify the root cause and fix failing tests with confidence.

Execution traces in the explore tab

Execution traces in the explore tab.png

Execution traces are now available directly in the playground's explore tab. As you experiment with different principals, resources, and actions, you can inspect the complete policy evaluation path in real time. Every rule evaluation, condition check, and variable resolution is visible, making it straightforward to debug complex policy logic and verify that your authorization rules behave as expected before deploying them.

Drag-and-drop file support

Before zip support landed, we shipped the ability to drag and drop individual policy and test files from your local machine directly into the playground editor. No more copy-pasting file contents — just drop your files and start testing.

Role policy and constants templates

The playground template picker now includes examples for role policies and policy constants. These templates make it easier to get started with advanced policy features without needing to look up the syntax from scratch.

Effective derived roles display

When evaluating policies in the playground, the effective derived roles for a user are now displayed alongside the authorization result. This helps you understand which derived roles were activated during a request — useful for debugging scenarios where role assignment logic interacts with resource policies in unexpected ways.

Engine settings

We covered this in a previous post, but for completeness: the playground now supports engine settings, including default policy version, lenient scope search, and globals. These settings let you match the playground's behavior to your production PDP configuration, ensuring that what you test in the playground matches what happens in production.

Accessibility improvements

Icon-only buttons throughout the interface now have proper accessibility labels for screen reader users. Identifiers such as policy names, resource kinds, and action names are displayed in a fixed-width font for improved readability.

The playground continues to be the fastest way to develop, test, and debug Cerbos authorization policies. All of these features are available now in Cerbos Hub. If you have feedback or feature requests, join us on Slack or open an issue on GitHub.