Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Secretscanner | 2,627 | 2 days ago | 30 | April 26, 2022 | 18 | mit | Go | |||
:unlock: :unlock: Find secrets and passwords in container images and file systems :unlock: :unlock: | ||||||||||
Google Authenticator Libpam | 1,520 | 23 days ago | 1 | March 03, 2021 | 58 | apache-2.0 | C | |||
Yopass | 1,264 | 2 days ago | 62 | April 23, 2021 | 27 | apache-2.0 | TypeScript | |||
Secure sharing of secrets, passwords and files | ||||||||||
Whaler | 942 | a year ago | gpl-3.0 | Go | ||||||
Program to reverse Docker images into Dockerfiles | ||||||||||
Arc | 735 | 2 years ago | 34 | March 12, 2021 | 4 | gpl-3.0 | Go | |||
A manager for your secrets. | ||||||||||
Chrome_password_grabber | 656 | 3 months ago | 14 | gpl-3.0 | Python | |||||
Get unencrypted 'Saved Password' from Google Chrome | ||||||||||
Encpass.sh | 570 | 4 months ago | 3 | mit | Shell | |||||
Lightweight solution for using encrypted passwords in shell scripts | ||||||||||
Hemmelig.app | 453 | 19 days ago | 22 | mit | JavaScript | |||||
Keep your sensitive information out of chat logs, emails, and more with encrypted secrets. | ||||||||||
Cryptr | 429 | 3 months ago | 8 | apache-2.0 | HTML | |||||
Cryptr: a GUI for Hashicorp's Vault | ||||||||||
Whispers | 421 | 2 months ago | 8 | apache-2.0 | Python | |||||
Identify hardcoded secrets in static structured text |
SecretScanner has been integrated into ThreatMapper 1.3.0, and also remains as this standalone project.
Deepfence SecretScanner can find unprotected secrets in container images or file systems.
Secrets are any kind of sensitive or private data which gives authorized users permission to access critical IT infrastructure (such as accounts, devices, network, cloud based services), applications, storage, databases and other kinds of critical data for an organization. For example, passwords, AWS access IDs, AWS secret access keys, Google OAuth Key etc. are secrets. Secrets should be strictly kept private. However, sometimes attackers can easily access secrets due to flawed security policies or inadvertent mistakes by developers. Sometimes developers use default secrets or leave hard-coded secrets such as passwords, API keys, encryption keys, SSH keys, tokens etc. in container images, especially during rapid development and deployment cycles in CI/CD pipeline. Also, sometimes users store passwords in plain text. Leakage of secrets to unauthorized entities can put your organization and infrastructure at serious security risk.
Deepfence SecretScanner helps users scan their container images or local directories on hosts and outputs a JSON file with details of all the secrets found.
Check out our blog for more details.
Use SecretScanner if you need a lightweight, efficient method to scan container images and filesystems for possible secrets (keys, tokens, passwords). You can then review these possible 'secrets' to determine if any of them should be removed from production deployments.
For full instructions, refer to the SecretScanner Documentation.
Install docker and run SecretScanner on a container image using the following instructions:
./bootstrap.sh
docker build --rm=true --tag=deepfenceio/deepfence_secret_scanner:latest -f Dockerfile .
docker pull deepfenceio/deepfence_secret_scanner:latest
docker pull node:8.11
docker run -it --rm --name=deepfence-secretscanner -v $(pwd):/home/deepfence/output -v /var/run/docker.sock:/var/run/docker.sock deepfenceio/deepfence_secret_scanner:latest -image-name node:8.11
We have built upon the configuration file from shhgit project.
Thank you for using SecretScanner.
For any security-related issues in the SecretScanner project, contact productsecurity at deepfence dot io.
Please file GitHub issues as needed, and join the Deepfence Community Slack channel.
This tool is not meant to be used for hacking. Please use it only for legitimate purposes like detecting secrets on the infrastructure you own, not on others' infrastructure. DEEPFENCE shall not be liable for loss of profit, loss of business, other financial loss, or any other loss or damage which may be caused, directly or indirectly, by the inadequacy of SecretScanner for any purpose or use thereof or by any defect or deficiency therein.