trufflehog
talisman
Our great sponsors
trufflehog | talisman | |
---|---|---|
25 | 5 | |
13,863 | 1,832 | |
2.7% | 1.3% | |
9.9 | 7.0 | |
5 days ago | 17 days ago | |
Go | Go | |
GNU Affero General Public License v3.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.
trufflehog
-
Seeking help to identify vulnerabilities and secrets in a website backup file
Trufflehog
-
1 in 10 developers leaked an API-key in 2022
Frankly, I think it will take years to replace API-keys (if it will ever happen). Developers are much better-off using CLI tools that prevent leaking secrets by blocking commits to git (e.g., https://github.com/Infisical/infisical or https://github.com/trufflesecurity/trufflehog)
-
My boss keeps committing his creds into git
Trufflehog also offers pre-commit hooks. You can have it report on PRs too.
- Introducing DeepSecrets: a better appsec tool for secrets scanning
-
Nosey Parker: a new scanner to find misplaced secrets in textual data and Git history
Is this not just a another https://github.com/trufflesecurity/trufflehog?
-
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.
-
Thinking Like a Hacker: AWS Keys in Private Repos
It’s easy to think that it’s only important to scan for secrets in your public-facing repositories, but this real-world data breach proves that you need to treat all code the same from a security perspective. Malicious hackers can use open-source tools like Gitleaks and TruffleHog to quickly detect secrets in massive amounts of code*, without leaving a trace. As a defender, **it’s extremely important to have secret scans tightly integrated into your SDLC* (software development lifecycle) to reduce the risks of exposing them. GitGuardian offers secret scanning for private repositories in their Free, Business, and Enterprise plans.
-
Toyota Accidently Exposed a Secret Key Publicly on GitHub for Five Years
There are software like Trufflehog ( https://github.com/trufflesecurity/trufflehog ), that finds secrets. We are using it at organizational level, but there's always some delay from finding something and getting it reported. I've been meaning to add it both to our CI so our team can notice right away, and even to Git push hooks, to catch these cases early.
-
What are the best tools for Advanced Security Scans similar to GitHub Enterprise
https://github.com/trufflesecurity/trufflehog And https://github.com/Yelp/detect-secrets
-
Searching GITHUB
Have you tried trufflehog or gitrob? gitrob trufflehog
talisman
-
Detecting Secrets in Git Repositories
It's been a while since I looked, but pre-commit hooks (like talisman) would be the only way to prevent secrets from being committed/pushed. Server-side hooks are generally not supported on hosted repos (e.g. github, azure devops) since it's basically arbitrary code execution from the host's perspective.
-
Where have you had secrets leaked?
Isn't scanning for commits that contain secrets the better way? Best on server so secrets can't be pushed. Something like https://github.com/thoughtworks/talisman
- git push
-
GitHub Access Token Exposure
https://thoughtworks.github.io/talisman/
- 关于所谓密钥泄露,是否可以使用“先审后发”的方式避免?
What are some alternatives?
gitleaks - Protect and discover secrets using Gitleaks 🔑
husky - git hooks made easy
git-secrets - Prevents you from committing secrets and credentials into git repositories
detect-secrets - An enterprise friendly way of detecting and preventing secrets in code.
Husky.Net - Git hooks made easy with Husky.Net internal task runner! 🐶 It brings the dev-dependency concept to the .NET world!
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
ggshield - Find and fix 360+ types of hardcoded secrets and 70+ types of infrastructure-as-code misconfigurations.
roadmap - GitHub public roadmap
git-filter-repo - Quickly rewrite git repository history (filter-branch replacement)
simple-git-hooks - A simple git hooks manager for small projects