regolibrary
armo-helm
Our great sponsors
regolibrary | armo-helm | |
---|---|---|
5 | 1 | |
108 | 6 | |
2.8% | - | |
9.5 | 9.0 | |
6 days ago | over 1 year ago | |
Open Policy Agent | Smarty | |
Apache License 2.0 | 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.
regolibrary
-
CNCF accepts Kubescape as its first security and compliance scanner project
The question you're asking is missing the important piece: how useful are they _to whom_.
To a developer, think of them as glorified linters (most of them are, including Kubescape, I believe). Someone on your team chooses which included things should be flagged (e.g. "require resource limits to be set on pods", see the list here: https://github.com/kubescape/regolibrary), and then the tool yells at you when you try to do something it doesn't like. It's then up to you to figure out how to comply with the tool's decisions. Some people really like them, some people really hate them.
To an engineering manager or SRE team, I think they're great at preventing common errors that would otherwise be enforced through code reviews or other processes; they're basically the remediation after an outage where a pod OOMed ("if we set sane resource limits and enforce them, this won't happen" --> enforce resource limits policy).
To your company's legal and compliance team, they usually fulfill a checkbox requirement along the way to $COMPLIANCE_FRAMEWORK. By the time your company is at sufficient scale, you'll have a number of these, and automation is the only way to keep everyone sane (developers and auditors alike).
In general, I think they're well intentioned, and can be useful, but aren't a panacea--they aren't going to catch anything you're not already looking for, they're just going to make it easier to remedy/enforce the problems you already know about.
-
Kubescape: a Kind Insurance Inspector for Your Kubernetes Investments
Kubescape retrieves the Kubernetes objects from the API server and scan them by running a set of snippets developed by ARMO.
- GitHub - armosec/regolibrary
-
Are you scanning your Kubernetes cluster with Kubescape? What are your thoughts?
I guess I was not understood correctly and I apologize for that. When a new CVE is reported, we publish a control testing and alerting users if they are exposed. For example when CVE-2021-25742 was reported, we published the control less than a day later.
armo-helm
-
Kubescape: a Kind Insurance Inspector for Your Kubernetes Investments
You may install kubescape with or without pre-registering your cluster on the portal (in the first case, a secret key is provided). A helm chart is available for convenient installation.
What are some alternatives?
kubescape - Kubescape is an open-source Kubernetes security platform for your IDE, CI/CD pipelines, and clusters. It includes risk analysis, security, compliance, and misconfiguration scanning, saving Kubernetes users and administrators precious time, effort, and resources.
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
regal - Regal is a linter for Rego, with the goal of making your Rego magnificent!
docker-security-checker - Dockerfile Security Checker using OPA Rego policies with Conftest
ingress-nginx - Ingress-NGINX Controller for Kubernetes
lens-extension - A Lens extension for viewing Kubescape security information
gatekeeper-library - 📚 The OPA Gatekeeper policy library