Hello fellow devs!
I'm with Cerbos (https://cerbos.dev/), a tool designed to manage who can do what in your software applications.
For a couple of years now, Open Worldwide Application Security Project (OWASP) is naming authorization a top 10 API security risk:
We are excited to announce that Cerbos Hub is now in public beta!
Join the beta and help us shape the future of authZ: https://hub.cerbos.cloud/
Cerbos Hub is a managed service offering for the open-source authorization product, Cerbos. Cerbos lets teams provide the right access to the right person and the right service, across any application and at web scale and is used by hundreds of organizations in production with hundreds of millions of authorization checks being done monthly.
You can think of Cerbos Hub as a management interface and policy distribution infrastructure for Cerbos PDP. The Hub simplifies the process of collaboratively authoring, testing and distributing authorization policy updates in real-time even to the edge and end client devices via its WebAssembly extension. It is a stateless, scalable and collaborative solution for teams who want to save time, streamline their workflows and confidently roll out authZ updates.
The goal of this launch is the opening up the beta of Cerbos Hub to make the deployment and management of authZ everywhere in the stack - including the edge or client devices, possible.
We’re inviting you to try this out, especially if you’re interested in making sure your systems are secure and well-managed without extra hassle.
Our commitment at Cerbos is to make it as easy as possible for developers, product and security teams to manage authorization.
Currently, hundreds of organizations are using Cerbos PDP in production today, and tens of millions of authorization checks are being done every week, powering countless applications, processes and decisions.
Cerbos is unique in authZ realm as it employs the stateless design, which also means it can scale without bounds. As the need for application use and complex authorization rules increases, Cerbos can expand to meet these demands with no inherent limits. Cerbos uses a policy-centered approach that consolidates authorization rules in one place, keeping them apart from the code. This enables roles and permissions rules to be updated without rewriting code, all while maintaining strong audit logs, a requirement for regulated industries.
If you have any questions, ideas, or suggestions - let me know. I'll be around to provide answers, and are more than open to hearing what you have to say!
You're more than welcome to join the beta!
Not much into managed stuff but you appreciate open-source. Help us more reach more people by supporting us on GitHub.
Help us shape the future of authZ, help your teams focus on innovation!
Top comments (0)