consoleme VS glide

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

Especially for occasional access, I recommend implementing a request/approval workflow. It is still an early product, but Common Fate has a tool for this that I’m really excited about. https://github.com/common-fate/common-fate

Take a look at Common Fate

Honestly? I don’t know. On a more granular level, each of the above problems have their own solution. Talk to your coworkers about how you trust them, you just don’t want to take unnecessary risks. Make sure to do good security design before you need to pay KPMG $25 million to fix it for you. Talk to your coworkers about what their jobs actually are. Check out our Github repo, etc. etc.

If you want to check out the code for yourself, here’s a Go Playground link. And if you’re interested in seeing how we’ve implemented this in our own project, you can check out our gconfig package.