KubiScan
rbac-tool
KubiScan | rbac-tool | |
---|---|---|
10 | 9 | |
1,284 | 881 | |
1.0% | 3.5% | |
4.5 | 5.0 | |
2 days ago | 2 days ago | |
Python | Go | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
KubiScan
- Looking for Tips on Open Sourcing a kubernetes security tool
- KubiScan
-
Kubernetes Security Checklist 2021
RBAC Rights should be audited regularly (KubiScan, Krane)
- cyberark/KubiScan - A tool to scan Kubernetes cluster for risky permissions
rbac-tool
-
Getting started with kubectl plugins
Link to GitHub Repository
-
Data and System Visualization Tools That Will Boost Your Productivity
A simpler alternative to Krane is rbac-tool, which can be installed as kubectl plugin. It can also analyze, audit, interrogate RBAC rules, but most importantly, it can visualize them:
-
Interesting tools?
Tool to create and visualize RBAC in cluster: https://github.com/alcideio/rbac-tool
-
Kubernetes Multi-Cluster Part 3: Authentication and Access Control
Other tools that can also audit your existing RBAC permissions and Kubernetes setups are rbac-tool and rbac-audit.
-
What would make your life easier when using Kubernetes?
And of course a quick google search shows that someone has already created something like that for RBAC: https://github.com/alcideio/rbac-tool
- rbac-tool
-
Kubernetes Security Checklist 2021
Role-Based Access Control (RBAC) should be configured for the Kubernetes cluster. Rights need to be assigned within the project namespace based on least privilege and separation of duties (RBAC-tool)
-
Compiled list of ClusterRoles for better/safer RBAC
I've been tasked with defining and documenting some ClusterRoles with clear permissions that should (mostly) be enough for any kind of cluster. The idea is for admins (who don't necessarily do the devops behind) to be able to understand what each CR does, to assign these CRs to users on the fly, to update a user's access as their needs change, to view a list of policy rules, who can do what etc... For this maintenance and tracking part we use rbac-manager and rbac-tool, which are excellent tools imo.
-
Ask r/kubernetes: What are you working on this week?
I've just started using rbac-manager and rbac-tool to apply and track rbac on our clusters :)
What are some alternatives?
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
Kyverno - Kubernetes Native Policy Management
grype - A vulnerability scanner for container images and filesystems
teleport - A WebXR teleport for three.js
krane - Kubernetes RBAC static analysis & visualisation tool
cvehound - Check linux sources dump for known CVEs.
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
kube-bench - Checks whether Kubernetes is deployed according to security best practices as defined in the CIS Kubernetes Benchmark
checkov - Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.
kube-hunter - Hunt for security weaknesses in Kubernetes clusters
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.