berglas
gitleaks
berglas | gitleaks | |
---|---|---|
37 | 36 | |
1,224 | 15,280 | |
0.1% | 1.0% | |
6.9 | 8.1 | |
23 days ago | 2 days ago | |
Go | Go | |
Apache License 2.0 | MIT License |
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.
berglas
-
How to deploy a Django app to Google Cloud Run using Terraform
Secret Manager: secure storage for sensitive data e.g passwords.
- How do you handle sensitive variables with a service-worker?
-
Increasing Your Cloud Function Development Velocity Using Dynamically Loading Python Classes
Google Secret Manager
-
Getting started using Google APIs: API Keys (Part 2)
API keys are easy to "leak" or compromise, so best to not only use the restrictions presented to you when you create them but physically protect them as well. Don't code them in plain-text, don't check them into GitHub, etc. Store them in a secure database or use a service like GCP Secret Manager.
-
Need some advice on API key storage
I've been looking at Google Secret Manager which sounds promising but I've not been able to find any examples or tutorials that help with the actual practical details of best practice or getting this working. I'm currently reading about Cloud Functions which also sound promising but again, I'm just going deeper and deeper into GCP without feeling like I'm gaining any useful insights.
-
Secure GitHub Actions by pull_request_target
In this post, I described how to build secure GitHub Actions workflows by pull_request_target event instead of pull_request event. Using pull_request_target, you can prevent malicious codes from being executed in CI. And by managing secrets in secrets management services such as AWS Secrets Manager and Google Secret Manager and access them via OIDC, you can restrict the access to secrets securely. To migrate pull_request to pull_request_target, several modifications are needed. And pull_request_target has a drawback that it's difficult to test changes of workflows, so it's good to introduce pull_request_target to repositories that require strong permissions in CI. For example, a Terraform Monorepo tends to require strong permissions for CI, so it's good to introduce pull_request_target to it.
-
Need Help with Deploying Directus on Google Cloud Platform (GCP)
If you want to make these secrets more secure and get versioning and access logs for them, you may want to switch to Secret Manager later on. They can still be exposed as environment variables to your code. It's a little more setup work, so start with the simple approach at the top.
-
Has anyone been able to implement the OpenAI API with a Firebase Function (which is needed for the env variable API Key)?
https://cloud.google.com/secret-manager https://aws.amazon.com/secrets-manager/
- Securely storing Social Security Numbers with Firebase?
- Dónde van las credenciales cuando voy a subir un código a la nube para correr 24/7?
gitleaks
-
Cloud Security and Resilience: DevSecOps Tools and Practices
1. Gitleaks: https://github.com/gitleaks/gitleaks Gitleaks provides a way for developers to find and prevent security breaches by scanning Git repositories for secrets like passwords and API keys.
-
How to use Lefthooks in your node project?
install gitleaks in your machine gitleaks
-
I Analyzed StackOverflow for Secrets
> gitleaks : fatal error: runtime: out of memory
Should be fixed now: https://github.com/gitleaks/gitleaks/pull/1292. Thanks for highlighting this simple change I've been putting off :)
-
[Help Needed] Securing Customized Gitleaks and Backend Communication?
I work in IT and we're enhancing our 'Shift Left Security' approach to prevent sensitive data leaks in our GitHub repositories. We've customized Gitleaks to send git-related information (like remote repository, author details, commit hash etc.) to our backend after each commit. This setup helps us monitor Gitleaks usage among our developers. (gitleaks)
-
Go Security Scanner
Cool. What features/capabilities are different compared to gitleaks?
-
My boss keeps committing his creds into git
To add my anecdote, testing out Trufflehog versus Gitleaks and detect-secrets the other tools seemed superior on detection rate and easier to work with.
-
Tools for very basic security audits
Some tools to consider: Gitleaks - open-source secret scanner for git repositories, files, and directories. Retire.js - dependency check tool for client JS code. Censys - It’s a search engine that you can use, for example, to scan any IP address and check open ports, software versions, location of the servers, etc. If you want to check more tools, you can download this free ebook with a list of recommended security tools: https://brightinventions.pl/blog/app-security-free-ebook/ The listed tools are free or offer free trials.
-
About secret scanning
bonuses: - https://github.com/trufflesecurity/trufflehog - https://github.com/gitleaks/gitleaks
-
Someone has access to my private repos = I lost 140k
I GET IT I need to follow best practice and not upload any sensitive information, even if its a private repo. But through my 10 yeras of coding it happened twice. However these keys only lived in 2 areas: my laptop and GITHUB. My laptop is pretty secured, and the timing of the above events just make me really think someone internally at Github is running https://github.com/gitleaks/gitleaks on private repos he / she has access to.
-
any open source that checks security vulnerabilities in code?
Maybe https://github.com/gitleaks/gitleaks is what you are looking for
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
trufflehog - Find and verify secrets
helm-charts
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
kube-secrets-init - Kubernetes mutating webhook for `secrets-init` injection
git-secrets - Prevents you from committing secrets and credentials into git repositories
cocert - Split and distribute your private keys securely amongst untrusted network
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
husky - git hooks made easy
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
semgrep - Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.