# DeepSecrets - a better tool for secret scanning
## Yet another tool - why?
Existing tools don't really "understand" code. Instead, they mostly parse texts.
DeepSecrets expands classic regex-search approaches with semantic analysis, dangerous variable detection, and more efficient usage of entropy analysis. Code understanding supports 500+ languages and formats and is achieved by lexing and parsing - techniques commonly used in SAST tools.
DeepSecrets also introduces a new way to find secrets: just use hashed values of your known secrets and get them found plain in your code.
Under the hood story is in articles here: https://hackernoon.com/modernizing-secrets-scanning-part-1-the-problem
## Mini-FAQ after release :)
> Pff, is it still regex-based?
Yes and no. Of course, it uses regexes and finds typed secrets like any other tool. But language understanding (the lexing stage) and variable detection also use regexes under the hood. So regexes is an instrument, not a problem.
> Why don't you build true abstract syntax trees? It's academically more correct!
DeepSecrets tries to keep a balance between complexity and effectiveness. Building a true AST is a pretty complex thing and simply an overkill for our specific task. So the tool still follows the generic SAST-way of code analysis but optimizes the AST part using a different approach.
> I'd like to build my own semantic rules. How do I do that?
Only through the code by the moment. Formalizing the rules and moving them into a flexible and user-controlled ruleset is in the plans.
> I still have a question
Feel free to communicate with the [maintainer](https://github.com/avito-tech/deepsecrets/blob/main/pyproject.toml#L6-L8)
## Installation
From Github via pip
`$ pip install git+https://github.com/avito-tech/deepsecrets.git`
From PyPi
`$ pip install deepsecrets`
## Scanning
The easiest way:
`$ deepsecrets --target-dir /path/to/your/code --outfile report.json`
This will run a scan against `/path/to/your/code` using the default configuration:
- Regex checks by the built-in ruleset
- Semantic checks (variable detection, entropy checks)
Report will be saved to `report.json`
### Fine-tuning
Run `deepsecrets --help` for details.
Basically, you can use your own ruleset by specifying `--regex-rules`. Paths to be excluded from scanning can be set via `--excluded-paths`.
## Building rulesets
### Regex
The built-in ruleset for regex checks is located in `/deepsecrets/rules/regexes.json`. You're free to follow the format and create a custom ruleset.
### HashedSecret
Example ruleset for regex checks is located in `/deepsecrets/rules/regexes.json`. You're free to follow the format and create a custom ruleset.
## Contributing
### Under the hood
There are several core concepts:
- `File`
- `Tokenizer`
- `Token`
- `Engine`
- `Finding`
- `ScanMode`
### File
Just a pythonic representation of a file with all needed methods for management.
### Tokenizer
A component able to break the content of a file into pieces - Tokens - by its logic. There are four types of tokenizers available:
- `FullContentTokenizer`: treats all content as a single token. Useful for regex-based search.
- `PerWordTokenizer`: breaks given content by words and line breaks.
- `LexerTokenizer`: uses language-specific smarts to break code into semantically correct pieces with additional context for each token.
### Token
A string with additional information about its semantic role, corresponding file, and location inside it.
### Engine
A component performing secrets search for a single token by its own logic. Returns a set of Findings. There are three engines available:
- `RegexEngine`: checks tokens' values through a special ruleset
- `SemanticEngine`: checks tokens produced by the LexerTokenizer using additional context - variable names and values
- `HashedSecretEngine`: checks tokens' values by hashing them and trying to find coinciding hashes inside a special ruleset
### Finding
This is a data structure representing a problem detected inside code. Features information about the precise location inside a file and a rule that found it.
### ScanMode
This component is responsible for the scan process.
- Defines the scope of analysis for a given work directory respecting exceptions
- Allows declaring a `PerFileAnalyzer` - the method called against each file, returning a list of findings. The primary usage is to initialize necessary engines, tokenizers, and rulesets.
- Runs the scan: a multiprocessing pool analyzes every file in parallel.
- Prepares results for output and outputs them.
The current implementation has a `CliScanMode` built by the user-provided config through the cli args.
### Local development
The project is supposed to be developed using VSCode and 'Remote containers' feature.
Steps:
1. Clone the repository
2. Open the cloned folder with VSCode
3. Agree with 'Reopen in container'
4. Wait until the container is built and necessary extensions are installed
5. You're ready
Raw data
{
"_id": null,
"home_page": "",
"name": "deepsecrets",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.9,<3.12",
"maintainer_email": "",
"keywords": "security,secrets,credentials,scanning,appsec",
"author": "Nikolai Khechumov",
"author_email": "khechumov@gmail.com",
"download_url": "https://files.pythonhosted.org/packages/f5/32/d6835d9b973ca8e297e9b01d4c1293fc55c613c4f624bbb77c7e8bef3a0f/deepsecrets-1.1.3.tar.gz",
"platform": null,
"description": "# DeepSecrets - a better tool for secret scanning\n\n## Yet another tool - why?\nExisting tools don't really \"understand\" code. Instead, they mostly parse texts.\n\nDeepSecrets expands classic regex-search approaches with semantic analysis, dangerous variable detection, and more efficient usage of entropy analysis. Code understanding supports 500+ languages and formats and is achieved by lexing and parsing - techniques commonly used in SAST tools.\n\nDeepSecrets also introduces a new way to find secrets: just use hashed values of your known secrets and get them found plain in your code.\n\nUnder the hood story is in articles here: https://hackernoon.com/modernizing-secrets-scanning-part-1-the-problem \n\n## Mini-FAQ after release :)\n> Pff, is it still regex-based?\n\nYes and no. Of course, it uses regexes and finds typed secrets like any other tool. But language understanding (the lexing stage) and variable detection also use regexes under the hood. So regexes is an instrument, not a problem.\n\n> Why don't you build true abstract syntax trees? It's academically more correct!\n\nDeepSecrets tries to keep a balance between complexity and effectiveness. Building a true AST is a pretty complex thing and simply an overkill for our specific task. So the tool still follows the generic SAST-way of code analysis but optimizes the AST part using a different approach.\n\n> I'd like to build my own semantic rules. How do I do that?\n\nOnly through the code by the moment. Formalizing the rules and moving them into a flexible and user-controlled ruleset is in the plans.\n\n> I still have a question\n\nFeel free to communicate with the [maintainer](https://github.com/avito-tech/deepsecrets/blob/main/pyproject.toml#L6-L8)\n\n## Installation\n\nFrom Github via pip\n\n`$ pip install git+https://github.com/avito-tech/deepsecrets.git`\n\nFrom PyPi\n\n`$ pip install deepsecrets`\n\n\n## Scanning\nThe easiest way:\n\n`$ deepsecrets --target-dir /path/to/your/code --outfile report.json`\n\nThis will run a scan against `/path/to/your/code` using the default configuration:\n- Regex checks by the built-in ruleset\n- Semantic checks (variable detection, entropy checks)\n\nReport will be saved to `report.json`\n\n### Fine-tuning\nRun `deepsecrets --help` for details.\n\nBasically, you can use your own ruleset by specifying `--regex-rules`. Paths to be excluded from scanning can be set via `--excluded-paths`.\n\n## Building rulesets\n\n### Regex\n\nThe built-in ruleset for regex checks is located in `/deepsecrets/rules/regexes.json`. You're free to follow the format and create a custom ruleset.\n\n### HashedSecret\n\nExample ruleset for regex checks is located in `/deepsecrets/rules/regexes.json`. You're free to follow the format and create a custom ruleset.\n\n\n## Contributing\n\n### Under the hood\nThere are several core concepts:\n\n- `File`\n- `Tokenizer`\n- `Token`\n- `Engine`\n- `Finding`\n- `ScanMode`\n\n### File\nJust a pythonic representation of a file with all needed methods for management.\n\n### Tokenizer\nA component able to break the content of a file into pieces - Tokens - by its logic. There are four types of tokenizers available:\n\n- `FullContentTokenizer`: treats all content as a single token. Useful for regex-based search.\n- `PerWordTokenizer`: breaks given content by words and line breaks.\n- `LexerTokenizer`: uses language-specific smarts to break code into semantically correct pieces with additional context for each token.\n\n### Token\nA string with additional information about its semantic role, corresponding file, and location inside it.\n\n### Engine\nA component performing secrets search for a single token by its own logic. Returns a set of Findings. There are three engines available:\n\n- `RegexEngine`: checks tokens' values through a special ruleset\n- `SemanticEngine`: checks tokens produced by the LexerTokenizer using additional context - variable names and values\n- `HashedSecretEngine`: checks tokens' values by hashing them and trying to find coinciding hashes inside a special ruleset\n\n### Finding\nThis is a data structure representing a problem detected inside code. Features information about the precise location inside a file and a rule that found it.\n\n### ScanMode\nThis component is responsible for the scan process.\n\n- Defines the scope of analysis for a given work directory respecting exceptions\n- Allows declaring a `PerFileAnalyzer` - the method called against each file, returning a list of findings. The primary usage is to initialize necessary engines, tokenizers, and rulesets.\n- Runs the scan: a multiprocessing pool analyzes every file in parallel.\n- Prepares results for output and outputs them.\n\nThe current implementation has a `CliScanMode` built by the user-provided config through the cli args.\n\n### Local development\n\nThe project is supposed to be developed using VSCode and 'Remote containers' feature.\n\nSteps:\n1. Clone the repository\n2. Open the cloned folder with VSCode\n3. Agree with 'Reopen in container'\n4. Wait until the container is built and necessary extensions are installed\n5. You're ready\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "A better tool for secrets search",
"version": "1.1.3",
"project_urls": {
"Bug Tracker": "https://github.com/avito-tech/deepsecrets/issues",
"Homepage": "https://github.com/avito-tech/deepsecrets"
},
"split_keywords": [
"security",
"secrets",
"credentials",
"scanning",
"appsec"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "0781d9fbeeb576558e3838b5c586fd8a437a092f4f2a92292af61ed51a0e0677",
"md5": "57c27dcc3afa5da387e104d775016950",
"sha256": "9cd42bbef497f7d7d30fce04978efc8840d1e5ac410b664d3fcf53e2e66360c6"
},
"downloads": -1,
"filename": "deepsecrets-1.1.3-py3-none-any.whl",
"has_sig": false,
"md5_digest": "57c27dcc3afa5da387e104d775016950",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9,<3.12",
"size": 49169,
"upload_time": "2023-08-29T06:32:04",
"upload_time_iso_8601": "2023-08-29T06:32:04.349852Z",
"url": "https://files.pythonhosted.org/packages/07/81/d9fbeeb576558e3838b5c586fd8a437a092f4f2a92292af61ed51a0e0677/deepsecrets-1.1.3-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "f532d6835d9b973ca8e297e9b01d4c1293fc55c613c4f624bbb77c7e8bef3a0f",
"md5": "baaaf51a811cfe1378e041d604d4323f",
"sha256": "ab3145ed9a483cf1943d00aeb1ae75247354c2523f09cdc1214b0d0096d8b772"
},
"downloads": -1,
"filename": "deepsecrets-1.1.3.tar.gz",
"has_sig": false,
"md5_digest": "baaaf51a811cfe1378e041d604d4323f",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9,<3.12",
"size": 122798,
"upload_time": "2023-08-29T06:32:06",
"upload_time_iso_8601": "2023-08-29T06:32:06.147861Z",
"url": "https://files.pythonhosted.org/packages/f5/32/d6835d9b973ca8e297e9b01d4c1293fc55c613c4f624bbb77c7e8bef3a0f/deepsecrets-1.1.3.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-08-29 06:32:06",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "avito-tech",
"github_project": "deepsecrets",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "deepsecrets"
}
JSON
