Jump to: navigation, search

Consistent and Secure Default Policies Popup Team

Revision as of 20:47, 30 June 2021 by Ghanshyam Mann (talk | contribs) (Team Progress)

Problem Description

Existing policy defaults suffer from three major faults:

  1. the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
  2. insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
  3. related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

Team Goal

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

Popup Team Completion Criteria

This team will be disbanded after:

  1. The majority of the projects listed below have completed their policy migrations
  2. A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
  3. A community goal is proposed and accepted by the TC


Use topic:secure-rbac in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.


The Secure Default Policies popup team holds public biweekly meeting:

Everyone interested in the Secure Default Policies and planning to implement those in your project should attend!




  1. Raildo Mascena <rmascena@redhat.com> (raildo)
  2. Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)


  • Barbican: Douglas Mendizábal (redrobot)
  • Nova: Ghanshyam Mann (gmann)
  • Neutron: Miguel Lavalle (mlavalle)
  • Cinder: Brian Rosmaita (rosmaita)
  • Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
  • Manila: Goutham Pacha Ravi (gouthamr)


  • Mohammed Naser <mnaser@vexxhost.com>
  • Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
  • Ade Lee (ade_lee) - barbican
  • Miguel Lavalle (mlavalle) - neutron
  • Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
  • Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
  • Tobias Rydberg (tobberydberg)
  • Erik McCormick <emccormick@cirrusseven.com> (emccormick)
  • Tergel Munkhbat tergel@fibo.cloud
  • Ghanshyam Mann (gmann)
  • Vishakha Agarwal (vishakha)-  Keystone

Pre-work to provide a smooth migration path to the new policy

Team Progress

Gerrit Topic: https://review.opendev.org/q/topic:%2522secure-rbac%2522+status:open

Projects Completed the new RBAC

Projects started the work

Projects Planning in next cycle