Auditing rbac

Through RBAC, you can control what end-users can do at both broad and granular levels

You can designate whether the user is an administrator, a specialist user, or an end-user, and align roles and access permissions with your employees’ positions in the organization

The RBAC API is a set of roles that administrators can configure to limit access to the Kubernetes resources

The ExtensiveRoleCheck automates the searching process and outputs the risky roles and rolebindings found in the RBAC API

Make Changes: Once the current security status and roles are understood (not to mention a policy is written), it’s time to make the changes

Continually Adapt: It’s likely that the first iteration of RBAC will require some tweaking

Early on, you should evaluate your roles and security status frequently