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

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
V
V2EX
WordPress大学
WordPress大学
U
Unit 42
I
InfoQ
A
About on SuperTechFans
宝玉的分享
宝玉的分享
J
Java Code Geeks
博客园 - 司徒正美
爱范儿
爱范儿
Engineering at Meta
Engineering at Meta
G
Google Developers Blog
人人都是产品经理
人人都是产品经理
小众软件
小众软件
Microsoft Security Blog
Microsoft Security Blog
L
LangChain Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Hugging Face - Blog
Hugging Face - Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
aimingoo的专栏
aimingoo的专栏
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Last Week in AI
Last Week in AI
腾讯CDC
Recent Announcements
Recent Announcements

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
Upgraded user-defined output, audit log improvements, and...
Alex Olivier · 2024-02-13 · via Cerbos - All Posts

The v0.33 release of Cerbos PDP is packed with new features including an upgraded user-defined output, audit log improvements, and more.

We have been working closely with Cerbos users like Utility Warehouse on this release. Utility Warehouse, per their own words, uses Cerbos as it allows their team to focus on business use cases and getting rid of technical debt, instead of wondering how to write a policy evaluation language. We can’t wait to hear more about what you would like to see in future releases - join our Slack community to join the conversation.

Upgraded user-defined output in policy evaluation

The user-defined output from a policy evaluation now has a when.conditionNotMet option that produces an output when a rule's condition is not satisfied. This improvement simplifies the crafting of policies for scenarios where it's important to know which criteria led to a denial.

In addition, we improved the structure of the output block. It is now clearer and easier to understand, though old policies will still work.

Old syntax:

- actions: ['view']
  effect: EFFECT_ALLOW
  roles: ["user"]
  condition:
    match:
      expr: request.resource.attr.public == true
  output:
    expr: >
      "%s allowed to view".format([request.principal.id])

New Syntax:

- actions: ['view']
  effect: EFFECT_ALLOW
  roles: ["user"]
  condition:
    match:
      expr: request.resource.attr.public == true
  output:
    when:
      ruleActivated: >
        "%s allowed to view".format([request.principal.id])

Audit log improvements

Audit log entries now contain store-specific metadata about the policies used to make each decision. For example, if a git store is used, the audit log captures the git commit hash of the policy used by the Cerbos engine. This information can then be used during a security investigation to match access control decisions with the revision history of the policy repository.

Additionally, the API response now includes a unique call ID generated by Cerbos for each request, enabling applications to cross-reference Cerbos audit logs with application logs.

Breaking changes

This release removes the deprecated `client` package which has been superseded by github.com/cerbos/cerbos-sdk-go. Additionally, support for configuring traces using the tracing section of the config file has been dropped. For the new way of configuring traces, refer to the migration instructions.

You can find the full release notes for v0.33 on docs.cerbos.dev, and if you have any questions join our Slack community.