kubescape
git-secrets
kubescape | git-secrets | |
---|---|---|
76 | 32 | |
9,713 | 12,048 | |
0.7% | 0.8% | |
9.5 | 1.0 | |
10 days ago | 26 days ago | |
Go | Shell | |
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.
kubescape
-
CodiumAI PR-Agent Dominates the Dev World with Versatility and Open-Source Power
CodiumAI PR-Agent’s influence extends deeply within open-source projects. An exemplary illustration is Kubespace, a Cloud Native Computing Foundation (CNCF) sandbox project. Since its adoption in August, Kubespace has been utilizing the PR-Agent service. They also recently had a public bug bounty collaboration with CodiumAI. This program added an extra layer of community-driven scrutiny, encouraging contributors to utilize simple commands like /describe for effective pull request messages. Here the contributor wanted to better describe the PR, so he used the /describe prompt.
-
Kubescape 3.0 is available to enhance your K8s security experience
Kubescape is the first Kubernetes security scanner that was accepted to the cloud native computing foundation. Kubescape 3.0 is a major release that extended the functionality of the original misconfiguration scanner to include vulnerabilities and usabillty improvements. If you are interested in an overview, feel free to check out the blog post. To dive straight into the code check out the repo. I'd love it hear what you think. What you like, what can be improved and of course, if you have any questions, hit me up.
- Shrink to Secure: Kubernetes and Secure Compact Containers
-
An Overview of Kubernetes Security Projects at KubeCon Europe 2023
Kubescape is a comprehensive Kubernetes security platform and CNCF sandbox project. It can scan clusters, Helm charts, and YAML manifests to detect misconfigurations. It supports various frameworks, including NSA-CISA, MITRE ATT&CK®, and the CIS Benchmark.
-
My CNCF LFX Mentorship Spring 2023 Project at Kubescape
Publishing
- K8s security just got easier. A single Open-Source security tool that seamlessly integrates into your entire stack.
- Scan manifest files (YAML and helm charts) directly from GitHub even with no clusters in place + assisted remediation for FREE.
- Don't let Kubernetes misconfigurations delay your deployment. Auto-scan manifest files directly from GitHub + assisted remediation.
- Detect critical vulnerabilities earlier in the development process and prevent CVEs from reaching production environments.
- Kubescape makes RBAC easy. Instantly reveal all the roles, resources, and relevant relationships to manage secure clusters.
git-secrets
-
Fired for leaked credentials. How do I explain this?
Well, this doesn't really happen at places that don't suck. They had no least privilege access to critical secrets and no processes (like pre-commit hooks using git-secrets) to prevent them being committed.
-
Recovering from Accidentally Pushing Sensitive Information to a Remote Git Repository
# macOS brew install git-secrets # Linux git clone https://github.com/awslabs/git-secrets.git cd git-secrets make install
- Managing secrets like API keys in Python - Why are so many devs still hardcoding secrets?
-
If you pay for an API key depending on the amount of requests, is it safe to push your code to GitHub?
You could use Git hooks to prevent someone from being able to author a commit when you suspect there is a secret being committed. In addition to this, you could also perform this check server-side, in case someone did not run their Git hooks for whatever reason. For example, check out git-secrets.
-
Securing the software supply chain in the cloud
git-secrets
-
How to deal with unintended information leakage when using GitHub as your GIT?
Install git-secrets. Go into each of your repos, scan for past mistakes, and add a git-commit hook:
- GitHub Access Token Exposure
-
Security scanning
I agree that code scanning is really important, the best way to convince others is to identify high-risk threats in source code and present them to the decision-makers. For example, scanning Secrets is great for showing how repositories can be a massive vulnerability and identifying some low-hanging fruit, especially in the git history. Attackers are really after git repository access for this reason and there are plenty of open-source or free tools that you can use to illustrate the problem. Git-Secrets, Truffle Hog. These aren't great for a long-term commercial solution, something like GitGuardian is a better commercial tool but if the goal is just to illustrate the problem then finding some high-value secrets with free tools is a good way to convince the security personnel to invest in some solutions. Then the door is open to having more conversations as you have already proven the risk.
-
Toyota Accidently Exposed a Secret Key Publicly on GitHub for Five Years
I worked for a big startup last year and was on a contract deadline for integrating a vendor framework into a React Native app.
It was taking too long to get a new temp demo license key and GitHub search with clever filters helped me track down a demo key that was recently uploaded to a test repo.
This is also why I use git-secrets in my repos.
https://github.com/awslabs/git-secrets
-
Marking findings as FPs in recurring scans
Under the covers, it is simply looking up an 'ignore' list stored in YML during each scan. If you are building your own, you might also want to see how AWS Labs is doing it in their solution git secrets.
What are some alternatives?
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
trufflehog - Find and verify secrets
falco - Cloud Native Runtime Security
gitleaks - Protect and discover secrets using Gitleaks 🔑
kubeaudit - kubeaudit helps you audit your Kubernetes clusters against common security controls
secretlint - Pluggable linting tool to prevent committing credential.
checkov - Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
grype - A vulnerability scanner for container images and filesystems
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
kubesec - Security risk analysis for Kubernetes resources
SecretFinder - SecretFinder - A python script for find sensitive data (apikeys, accesstoken,jwt,..) and search anything on javascript files