You are receiving this email because either we have met, chatted, or you’ve visited our website cerbos.dev and asked us to keep you up-to-date. If you have been forwarded this email, please use this link to subscribe and receive future updates. If you prefer not to receive these updates you can unsubscribe below, but we hope you stay!
Policy Workshop
Ever wondered how to get started with your first policy, or even which policy to start with? Then reach out for a 30 minute call with one of our developers at your convenience.
Cerbos Playground
We have just released a big upgrade to http://play.cerbos.dev which allows you to prototype policies right in your browser:
Folders - you can nest policies in folder as you would if you were working locally
Autocomplete & Validation - the Playground Editor gives you in-line feedback about the syntax of policies as well as autocomplete suggestions
Attribute Schema - you can provide JSONSchema for the attributes of your principal and resources and these will be checked in the demo panel and let you know if a request doesn’t comply
We have a number of updates still to come, including the ability to define and run tests for your policies - stay tuned in the coming weeks for more!
Cerbos v0.15 is out!
The latest release of Cerbos includes a number of updates to make the policy authoring experience easier:
REPL - A new REPL (read-evaluate-print-loop) for developing conditions for policies. It provides an interactive environment where all the special variables like request can be set and referenced in CEL expressions to get feedback about the effects of executing those expressions.
IDE Support - Schemas describing the structure of the Cerbos policies are now publicly available and can be used with editors (VSCode, Jetbrains and more) that support schemas to make the policy editing experience better.
Improved Testing Output - One of the core features of Cerbos is the policy testing framework. This release includes many improvements to the test runner to make the test output easy to consume by both humans and automated tools.
This blog post shows how context-aware permissions promote anywhere-anytime access by making controls intelligent enough to sense and react to their environment. The post also looks at why and when to use context-aware permissions.
This post reviews how an authorization model plays a vital role in securing an enterprise’s sensitive data. Businesses often code additional custom logic on top of traditional access control solutions like Active Directory. However, as businesses expand, they need access controls that can scale to match their growth.
The author covers how within microservices environments he goes from a simple flag to Role Based Access Controls (RBAC) and then onto Attribute Based Access Controls (ABAC). This article made it to the HackerNews frontpage and some interesting comments can be found here.
DeSimone comments on and provides the so-what for the new White House memo on zero trust. An example passage from the memo:
“In a zero trust architecture, every request for access should be evaluated to determine whether it is appropriate, which requires the ability to continuously evaluate any active session. If undue risk is identified, mitigations could include requiring reauthentication, limiting access until confirmation that the user requested action is appropriate, or denying access entirely.”
“Continuous verification means every single access request should be authorized. Every. Single. Request. Verification should not stop just because the previous one was accepted.”
We’ve growing very fast and need an experienced developer relations person as the face of Cerbos in the developer community. We’d love this person to engage with developers to discover and remedy pain points, produce accessible technical content and help build an inclusive community of Cerbos users.
If you know amazing DevRel professionals who we should be talking to, please let us know at join.us@cerbos.dev!
Do you want a Cerbos t-shirt?
Good! We want to give you a t-shirt! And we also want to talk to you about Cerbos and get your feedback, both what you like and dislike, what are your primary use cases, if you are missing any particular functionality or suggestions on how you would like us to improve the product.