A Kubernetes RBAC static analysis tool that identifies security risks and visualizes RBAC design.
Krane is a Kubernetes RBAC static analysis and visualization tool that helps identify security risks in role-based access control configurations. It scans RBAC rules to detect dangerous permissions and misconfigurations, providing actionable reports and a dashboard to visualize the security posture. The tool is designed to be integrated into CI/CD pipelines or run as a continuous monitoring service within clusters.
Platform engineers, SREs, and security teams managing Kubernetes clusters who need to audit and secure RBAC permissions. It's also valuable for DevOps practitioners integrating security checks into their deployment pipelines.
Krane offers a comprehensive, graph-based approach to RBAC analysis, enabling deep querying of permission relationships and providing an intuitive dashboard for visualization. Its flexibility to run locally, in CI/CD, or as a service makes it adaptable to various workflows.
Kubernetes RBAC static analysis & visualisation tool
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Indexes RBAC entities in RedisGraph, enabling efficient, ad-hoc queries with CypherQL for deep permission analysis, as shown in the querying examples in the README.
Supports CLI, CI/CD integration, and standalone service modes, allowing use in local development, pipelines, or continuous cluster monitoring, per the portability features listed.
Provides tree and graph network views to visually explore RBAC structures and security posture, making complex relationships easier to understand.
Allows extending built-in risk rules with custom YAML definitions and whitelists, enabling tailored security checks for specific cluster needs.
Requires RedisGraph as a separate dependency, adding deployment overhead and maintenance, evident in the docker-compose and Helm setup instructions.
Creating custom risk rules demands knowledge of Ruby for writer expressions and CypherQL for graph queries, which may deter non-developer users.
Limited to reporting and visualization without real-time enforcement capabilities, so it doesn't prevent RBAC misconfigurations as they occur.
Labeled as beta in the README, indicating potential instability, breaking changes, or incomplete features that might not be production-ready for all users.