consoleme VS cerbos

Why are you using (very expensive) GPT, or any LLM for that matter, when this was already a solved problem using rulesets? Netflix for example has open source that does this already: https://github.com/Netflix/consoleme

Instead of analyzing your code, you just run your code with no permissions and it automatically detects permission failures and thens open those permissions, with a UI showing you what it did so you can remove any permissions you don't want.

That actually seems much more secure than trying to divine the rules from reading the code.

What value is the LLM adding here?

You may also want to look into Netflix’s ConsoleMe https://github.com/Netflix/consoleme

This is the way. I’ve seen this happen countless times. It’s happened to me too. It’s happened to colleagues.

The worst case I’m aware of from first-hand knowledge was a large cluster of resources that got deployed for a product demo by a sales engineer and forgotten about. Turned into a nice ~$100,000 surprise in the quarterly budget.

Netflix built a tool for managing IAM permission requests as an auditable workflow, called ConsoleMe: https://github.com/Netflix/consoleme

There’s this tool as well https://github.com/Netflix/consoleme among others, check them out and see if the overhead is ok for you all now, but keep it simple to start.

Perhaps Consoleme from Netflix is a useful tool for you?

For sure, you can DM me. Might want to check out https://github.com/Netflix/consoleme too

The tool is in a similar space to iamlive, policy_sentry, and consoleme (all of which are worth checking out too if you're interested in making AWS security easier) but the main points of difference I see are:

After you read the resources, you can stand on the "shoulders of giants" https://github.com/Netflix/consoleme

Here, Cerbos comes into the picture.

In this tutorial you will learn how to use Cerbos to add fine-grained access control to any Nuxt web application, simplifying authorization as a result.

In my work with Cerbos, I apply the lessons learned from Da Vinci to tackle authorization challenges. Our approach is to create solutions where functionality seamlessly integrates with developer experience. Constantly iterating and viewing the tools through the users' lens, helps ensure that our access control solutions are robust and dev-friendly.

You may already know of our open source solution - Cerbos Policy Decision Point (PDP); a devtool which helps developers enforce access control over different parts of their software. If you need to learn more about Cerbos in general, we strongly recommend checking out the website and the docs.

GitHub: https://github.com/cerbos/cerbos URL: https://cerbos.dev

Cerbos Hub is a managed service offering for the open source authorization product, Cerbos.

Hello fellow devs! I'm with Cerbos (https://cerbos.dev/), a tool designed to manage who can do what in your software applications.