A new paradigm for cloud access management(demo.symops.com)
demo.symops.com
A new paradigm for cloud access management
https://demo.symops.com/
6 comments
It doesn't look like this can be tried out by users, so it's not eligible for Show HN. See https://news.ycombinator.com/showhn.html. You're welcome to come back and post a Show HN when there's something for people to try out. That is—assuming it's your own personal work, since that is also a Show HN rule!
If you don't like videos: direct docs link https://docs.symops.com/docs ; some examples: https://symops.com/use-cases
Overall, this seems to be a "security changes as a service" -- you set up all your internal resources to point to sym's servers (or self-hosted sym runner), and in return you can apply security changes like temporary access grants via nifty UIs based on web and Slack, all scripted using Python.
The pricing is unknown, "contact sales for details".
Overall, this seems to be a "security changes as a service" -- you set up all your internal resources to point to sym's servers (or self-hosted sym runner), and in return you can apply security changes like temporary access grants via nifty UIs based on web and Slack, all scripted using Python.
The pricing is unknown, "contact sales for details".
I always wonder about security with these cloud management companies. Instead of the KGB/NSA/hackers trying to break into AWS etc, they go for a cloud management company and get access to lots of companies. I’m not sure how it could be helped - it’s the nature of the beast, but I personally have concerns.
Really excellent point. The way we try to handle this is by sealing off the part of the system that has any access to customer credentials, and making sure those credential are as minimal as possible (e.g. we can grant and revoke permissions to an existing user, but we cannot create new users or new permissions).