Back to all scenarios
Scenario #225
Security
K8s v1.20, On-Premise
Insufficient RBAC Permissions Leading to Unauthorized Access
Insufficient Role-Based Access Control (RBAC) configurations allowed unauthorized users to access and modify sensitive resources within the cluster.
Find this helpful?
What Happened
The RBAC configurations were not properly set up, granting more permissions than necessary. As a result, unauthorized users were able to access sensitive resources such as secrets, config maps, and deployments.
Diagnosis Steps
- 1Reviewed RBAC policies and roles and found that users had been granted broad permissions, including access to sensitive namespaces and resources.
- 2Verified that the principle of least privilege was not followed.
Root Cause
RBAC roles were not properly configured, resulting in excessive permissions being granted to users.
Fix/Workaround
• Reconfigured RBAC roles to ensure that users only had the minimum necessary permissions.
• Applied the principle of least privilege and limited access to sensitive resources.Lessons Learned
RBAC should be configured according to the principle of least privilege to minimize security risks.
How to Avoid
- 1Regularly review and audit RBAC configurations to ensure they align with the principle of least privilege.
- 2Implement strict role definitions and limit access to only the resources necessary for each user.