whispers v1.3.6 releases: Identify hardcoded secrets and dangerous behaviours
Whispers is a static code analysis tool designed for parsing various common data formats in search of hardcoded credentials and dangerous functions. Whispers can run in the CLI or you can integrate it into your CI/CD pipeline.
- API tokens
- AWS keys
- Private keys
- Hashed credentials
- Authentication tokens
- Dangerous functions
- Sensitive files
- conf / ini
- Shell scripts
- AWS credentials files
- JDBC connection strings
- Jenkins config files
- Spring Framework Beans config files
- Java Properties files
Merge pull request #28 from Skyscanner/dependabot/pip/lazy-object-proxy-1.5.1
Bump lazy-object-proxy from 1.4.3 to 1.5.1
git clone https://github.com/Skyscanner/whispers
There are several configuration options available in Whispers. It’s possible to include/exclude results based on file path, key, or value. File path specifications are interpreted as globs. Keys and values accept regular expressions and several other parameters. There is a default configuration file built-in that will be used if you don’t provide a custom one.
config.yml should have the following structure:
The fastest way to tweak detection (ie: remove false positives and unwanted results) is to copy the default config.yml into a new file, adapt it, and pass it as an argument to Whispers.
Rules specify the actual things that should be pulled out from key-value pairs. There are several common ones that come built-in, such as AWS keys and passwords, but the tool is made to be easily expandable with new rules.
- Custom rules can be defined in the main config file under rules:
- Custom rules can be added to whispers/rules
All parsing functionality is implemented via plugins. Each plugin implements a class with the pairs() method that runs through files and returns the key-value pairs to be checked with rules.
Copyright 2020 Skyscanner Ltd