gosec
Go security checker (by securego)
docker-bench-security
The Docker Bench for Security is a script that checks for dozens of common best-practices around deploying Docker containers in production. (by docker)
Our great sponsors
| gosec | docker-bench-security | |
|---|---|---|
| 19 | 13 | |
| 7,426 | 8,878 | |
| 1.2% | 1.1% | |
| 8.8 | 5.9 | |
| 10 days ago | 6 days ago | |
| Go | Shell | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
gosec
Posts with mentions or reviews of gosec.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-31.
-
Top 10 Snyk Alternatives for Code Security
6. Gosec
-
Safety in Go
You can (and definitely should!) also use gosec.
-
We have getrandom at home
The crypto source in Go is great, no complaints there. Lints like gosec even recommend using it when generating crypto entropy. Go did a good job here, and I expect Rust will do the same sometime after getrandom reaches 1.0 so the API questions are settled, plus whatever makes sense for the future-proofing the standard library needs.
-
any open source that checks security vulnerabilities in code?
i think there's https://github.com/securego/gosec linter
-
Goast: Generic static analysis for Go Abstract Syntax Tree by OPA/Rego
Various static analysis tools are available for the Go language, and existing static analysis tools can check general best practices. For example, gosec is a tool to check secure Go coding, and I use it myself. However, coding rules in software development are not only based on best practices, but can also be software- or team-specific. For example
-
Vulnerability Management for Go
What's the difference between this a https://github.com/securego/gosec?
-
Github template for Golang services
A github actions workflow is provided to run go fmt, vet, test and gosec. An initial configuration for dependabot is also provided.
-
What tools exists, or you recommend, for code review, quality and/or security review
Besides what was mentioned, we use : staticcheck.io and https://github.com/securego/gosec
-
Container security best practices: Comprehensive guide
For application code, there are different SAST (Static Application Security Testing) tools like sonarqube, which provide vulnerability scanners for different languages, gosec for analyzing go code and detecting issues based on rules, linters, etc.
-
Static code analysis tool for pipeline
Try gosec for security vulnerabilities.
docker-bench-security
Posts with mentions or reviews of docker-bench-security.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-21.
-
Understanding Container Security
Scanning your container images for vulnerabilities is a good approach. But this scanning is not one time job, it should be done regularly (weekly, monthly, etc.) You need to follow vulnerability reports and fix all of the vulnerabilities as soon as possible. I recommend some open-source tools that could be useful: Trivy, Docker-Bench, Grype.
-
Security docker app
For Docker configuration I have used this in the past (it utilizes the CIS Docker Benchmark): https://github.com/docker/docker-bench-security
- What's your favourite Docker Image, and why?
-
How to Secure Your Kubernetes Clusters With Best Practices
Use Docker Bench for Security to audit your container images
-
Container security best practices: Comprehensive guide
Other tools you can use are linux-bench, docker-bench, kube-bench, kube-hunter, kube-striker, Cloud Custodian, OVAL, and OS Query.
- hardening my container: am i doing things right?
-
Docker Security Cheat Sheet
CIS Docker benchmark is a very extensive rule set for assessing docker host, daemon, images and containers from the security perspective.
It comes with a very handy tool as well https://github.com/docker/docker-bench-security
What are some alternatives?
When comparing gosec and docker-bench-security you can also consider the following projects:
golangci-lint - Fast linters Runner for Go
hadolint - Dockerfile linter, validate inline bash, written in Haskell
kube-bench - Checks whether Kubernetes is deployed according to security best practices as defined in the CIS Kubernetes Benchmark
gokart - A static analysis tool for securing Go code
go-tools - Staticcheck - The advanced Go linter
pre-commit-golang - Pre-commit hooks for Golang with support for monorepos, the ability to pass arguments and environment variables to all hooks, and the ability to invoke custom go tools.
checkov - Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.
SonarQube - Continuous Inspection
rustsec - RustSec API & Tooling
tfsec - Security scanner for your Terraform code
gokart-action - Integrate GoKart security static analysis to GitHub Actions
golang-standards/project-layout - Standard Go Project Layout
gosec vs golangci-lint
docker-bench-security vs hadolint
docker-bench-security vs kube-bench
gosec vs gokart
gosec vs go-tools
gosec vs pre-commit-golang
docker-bench-security vs checkov
docker-bench-security vs SonarQube
gosec vs rustsec
docker-bench-security vs tfsec
gosec vs gokart-action
gosec vs golang-standards/project-layout