gosec VS cfn_nag

6. Gosec

You can (and definitely should!) also use gosec.

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.

i think there's https://github.com/securego/gosec linter

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

What's the difference between this a https://github.com/securego/gosec?

A github actions workflow is provided to run go fmt, vet, test and gosec. An initial configuration for dependabot is also provided.

Besides what was mentioned, we use : staticcheck.io and https://github.com/securego/gosec

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.

.pre-commit-config.yaml – contains the cfn-lint and cfn_nag pre-commit hooks.

For generic CloudFormation templates, check CFN-NAG.

If you use CDK, you should implement CDK nag; otherwise, use cfn-nag.

cfn_nag

CodeBuild will run a linting check against the CloudFormation Template using cfn-lint and will then run cfn-nag to check for patterns that indicate insecure resources within the CloudFormation template.

Security checks for the Cloudformation stack using cfn-nag

cdk-nag contains several Aspects to check your applications for best practices. It is especially useful if you need to be HIPAA-compliant or have other compliance requirements. It is inspired by cfn_nag which is a a tool checking for patterns in your CloudFormation templates.

cfn-lint and cfn_nag or other tools of that nature to check as you write so you don't need to continually try to deploy only to find that you've done something dumb.

There is another tool called cfn_nag that can check your code for potentially any insecure infrastructure. When you read the documentation around this tool, the author says it can check for things such as:

I recently wanted to use the cfn-nag tool on some templates I was writing but couldn't find any instructions to install on Windows, but I have found a way to do it.