Epic Goal

Our goal is to enhance the precision of RBAC (Role-Based Access Control) permissions within our product by removing wildcards from permission definitions. We aim to streamline our code to operate on the minimum necessary permissions.

Why is this important?

RBAC permissions play a critical role in ensuring that only authorized users have access to the appropriate resources within our system. However, the use of wildcards in permission definitions can lead to security vulnerabilities and unintended access, potentially compromising the integrity and confidentiality of our data

Scenarios

1. Wildcards in RBAC permissions could potentially grant unintended access to sensitive resources.
2. Wildcards may result in overly broad access permissions, allowing users more privileges than necessary.

Acceptance Criteria

• [] Develop validation mechanisms to detect and prevent wildcard usage in RBAC permissions.
• [] Implement strict enforcement policies to disallow the use of wildcards in permission definitions.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.