consoleme VS slauth-cli

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

Hi HN, We're Daniel and Bruno and working on [Slauth.io]([https://slauth.io/](https://slauth.io/)). Slauth.io is a CLI to auto-generate secure IAM policies for AWS, and GCP (Azure in the next few days!). We enable development teams to speed up creating secure policies and reduce over-permissive policies being deployed to the cloud.

Check out the [video](https://www.loom.com/share/bd02211659eb4c7f9b335e34094b57cb?...) or give our open-source CLI a try with one of the sample repo's on [GitHub]([https://github.com/slauth-io/slauth-cli](https://github.com/...)

We got into the cloud access market by coincidence and were amazed by the amount of money spent on IAM. Current tooling such as [Ermetic.com]([http://Ermetic.com](http://ermetic.com/)) and [Wiz.io]([http://Wiz.io](http://wiz.io/)) visualize IAM misconfigurations post deployment but don't actually change engineering behavior, leaving organizations in a constant loop of engineers deploying over-permissive policies ⇒ security engineers/CISO's getting alerts ⇒ Jira tickets created begging developers to remediate ⇒ New over-permissive policies being deployed again.

We interviewed hundreds of developers and DevOps engineers and discovered two key pain points:

1. *IAM is a Hassle:* Developers despise dealing with IAM intricacies.