A kubectl plugin for security risk analysis of Kubernetes resources like pods, deployments, daemonsets, and statefulsets.
kubectl-kubesec is a kubectl plugin that performs security risk analysis on Kubernetes resources. It scans pods, deployments, daemonsets, and statefulsets to identify security misconfigurations and provides actionable recommendations to improve security posture. The plugin integrates with the kubesec.io service to analyze resources and assign security scores.
Kubernetes administrators, DevOps engineers, and security teams who need to identify and fix security issues in their Kubernetes workloads before deployment.
Developers choose kubectl-kubesec because it provides specific, actionable security advice directly within their kubectl workflow, supports both cloud and self-hosted scanning options, and helps prevent common security misconfigurations in Kubernetes resources.
Security risk analysis for Kubernetes resources
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides specific, actionable recommendations like enforcing runAsNonRoot and dropping capabilities, directly helping users fix security misconfigurations based on scan outputs.
Installs as a kubectl plugin via krew or curl, allowing scans to be performed with familiar kubectl commands without leaving the CLI workflow.
Supports running kubesec locally with Docker, enabling use in air-gapped or private networks where cloud services are prohibited, as shown in the README examples.
Assigns a numerical security score to each resource, making it easy to prioritize fixes based on the severity of issues identified, such as critical vs. advisory items.
Only scans pods, deployments, daemonsets, and statefulsets, omitting other critical resources like services or configmaps that might have security implications.
By default, sends scan data to the hosted kubesec.io service, which could raise privacy, security, and availability concerns for sensitive workloads unless self-hosted.
Requires manual execution for each scan, lacking built-in automation for continuous monitoring or seamless integration into existing security pipelines without additional scripting.