基础设施工程师的RBAC

发布于 2025-02-03 22:04:11 字数 160 浏览 5 评论 0原文

我觉得这是一个相当基本的问题,但是不知何故我找不到一个好的答案。

最近,审计师抱怨我们的云设置基于角色的访问控制。我的团队负责云基础架构(又称云工程,站点可靠性工程或DevOps),因此我们基本上拥有所有权利。我个人认为这是有道理的,因为我们有责任设置所有内容,并在必要时再次将其删除。我们是湿婆。

I feel this is a rather basic question, but somehow I'm unable to find a good answer.

Recently auditors are complaining about the Role Based Access Control for our cloud set-up. My team is responsible for the Cloud infrastructure (aka Cloud engineering, Site reliability engineering or DevOps) so we have basically all the rights. Personally I think this makes sense, given that we are responsible for setting everything up and where necessary remove it again. We're Shiva. ????

But I also understand this is a problem; especially because we can see into all the databases, buckets, etc. So what I'm looking for is an access level (say "maintainer") that is able to create and delete databases, but not look into them.

Does this exist and what is called?
If it doesn't, how then is this commonly solved?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

橘寄 2025-02-10 22:04:11

RBAC应该以这种方式剥夺:

  1. 定义系统中的角色。例如,“数据库管理员”,“数据库用户”,“数据库BI用户”。
  2. 将基础架构权限分配给每个角色。
  3. 分配每个用户执行职责所需的角色。
  4. 执行和监视您的RBAC政策。准备在船上和卸货用户准备程序。
  5. 自动化所有可能的一切。

RBAC should be aproached this way:

  1. Define the ROLES in your system. For example, "database administrator", "database user", "database BI user".
  2. Assign the infrastructure permisions to each role.
  3. Assign each user the roles it needs to perform its duties.
  4. Enforce and monitor your RBAC policies. Prepare prepare procedures onboard and offboard users.
  5. Automate everything you can.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文