Skip to main content
Products
PLATFORM
Optimum security and flexibility for the modern management of your Kubernetes clusters.
KubeOps KOSI
An effective software solution for the improvement and security of Kubernetes installations.
Request a demo
Book an appointment now to see a live demonstration of our KubeOps solutions in action.
Services
Managed Kubernetes Service
Comprehensive management of Kubernetes environments from setup to ongoing maintenance.
Academy
Advanced training and certification courses in Kubernetes for IT professionals and teams.
Consulting
Specialized Kubernetes solutions with a focus on security and comprehensive consulting.
Security
Security Library
Comprehensive security management and risk-minimizing measures for Kubernetes clusters.
Container Hardening
The 5-level hardening by KubeOps gives you more security for your container images and installation packages
Blog
Careers
About Us
Get in touch
Products
PLATFORM
Optimum security and flexibility for the modern management of your Kubernetes clusters.
KubeOps KOSI
An effective software solution for the improvement and security of Kubernetes installations.
Request a demo
Book an appointment now to see a live demonstration of our KubeOps solutions in action.
Services
Managed Kubernetes Service
Comprehensive management of Kubernetes environments from setup to ongoing maintenance.
Academy
Advanced training and certification courses in Kubernetes for IT professionals and teams.
Consulting
Specialized Kubernetes solutions with a focus on security and comprehensive consulting.
Security
Security Library
Comprehensive security management and risk-minimizing measures for Kubernetes clusters.
Container Hardening
The 5-level hardening by KubeOps gives you more security for your container images and installation packages
Blog
Careers
About Us
Get in touch
Measures
RBAC
Important Measures
The following questions need to be addressed:
Who is allowed to create clusterroles/roles and bindings?
Should only one person be responsible for this, or e.g. someone for clusterroles, someone else for roles and again someone else for the respective bindings?
Which clusterroles should there be?
Which Roles should there be?
Which naming convention makes sense?
What is not covered by RBAC?
How are elements not covered by RBAC handled?
Included in the following risks
Set Kubernetes application roles/rights