Live data from Hacker News

Show HN: Sym, define just-in-time access workflows in code

symops.com

11–12 of 12 posts

Re: Show HN: Sym, define just-in-time access workflows in code

#11

Impressive solution. I see great potential. In a startup of 30 people that needs SOC2 compliance - me as DevOps / security team - I have a problem with access requests from engineering / marketing / sales etc. On the one hand, I want to do them as quickly as possible, because I know how frustrating the lack of access is. On the other hand, our current flow for reporting change history / review / onboarding / offboard…

Thanks so much for the feedback!

> I was thinking of launching an access management project myself. Most access management systems are focused around SSO, and this - due to the SSO tax - is not for every application in a small organization.

Great point. SSO integrations also don’t necessarily provide the level of control you need to grant people appropriate permissions. Like you can add/remove people from the application but not give them appropriate access within it. Would love to learn how you’re thinking about the problem, send us a note if you want to talk more!

> I wonder what would be operational issues with this tool if this access was given for weeks / months instead of hours?

You can configure access duration flexibly with Sym. That being said, part of our philosophy is to make it easy for teams to transition to shorter access durations because the friction to re-grant access is reduced.

> I see your solution as pretty similar to Granted Approvals which are also open-source. What motivated you to start something of your own? I think Netflix open-sourced one solution for AWS too.

There are some great tools in the space for sure. Our motivation is to build a flexible engine for access and approvals that you can layer in to any modern platform stack.

Re: Show HN: Sym, define just-in-time access workflows in code

#12

Nice idea. Struggling with this problem too. My thoughts is that once you have all IaC set up hopefully this becomes less of a problem since you do things through PRs not clickops, and we might be setting up the roles via pulimi (or terraform) anyway. I guess the value here is in the exceptions, where you quickly want to give a human access to an area to dive in and solve a production issue?

Great point on doing things through PRs not clickops. As your practices mature, the need for approvals can shift from the care and feeding of your infrastructure to managing risk. Even with IaC in place, having controls around who can access customer data, internal admin panels, and other resources with a high blast radius is critical. We built Sym to serve as a flexible approvals layer that can adapt along with you as your stack evolves. There will always be new services and teams to incorporate, and we want to ensure you can always easily add in guardrails that give you sufficient control and visibility into what teams are up to without introducing unneeded bottlenecks.
Post reply on HN