Part 5, Coverage · Step 2: Deploy the scanners
Hosted or self-hosted: where the scanner runs
Two scanners: one hosted, one in the data center. In the TruffleHog web app, Nadia adds a hosted scanner for tools on the internet, like GitHub, Slack, and Jira Cloud. Kenji adds a self-hosted scanner for the internal build server and wiki, downloads its config file, and starts it on a company machine with Docker.
Why it matters. The scanner has to reach a place to read it. Hosted covers the cloud tools. Self-hosted covers what sits behind the firewall.
See it in the lesson Part 5 recap
Choosing hosted or self-hosted
- Tools on the internet, like GitHub.com, Slack, and Jira Cloud: a hosted scanner is the fastest path.
- Systems behind a firewall or VPN, like an internal build server or code server: run a self-hosted scanner.
- Rules about where data may be processed: self-hosted keeps the scanning on your machines.
- Many teams use both, each in its own scanner group.
- The self-hosted config file holds credentials. Keep it in a secret manager, not on a shared drive.
Sources
Keep going
- Try TruffleHog open source Scan a repository or a folder on your laptop.
- See TruffleHog Enterprise Continuous scanning, routing to owners, and re-checks.
- Talk to the team Ask how this would work in your environment.
More topics
- A key kept in a vault still gets copied out
- Deleted from the code, and it still works
- Bundled scanners and the noisy queue
- What sits behind a key: owner, reach, permissions, activity
- The owner chase: whose key is this?
- Which key to fix first
- Replace a key without breaking anything
- Proof it’s dead, time to fix, and what auditors ask for
- Keys in AI agents and AI training data
- Hooks, CI, history, chat, and builds: what each layer catches
- Keys outside the code: logs, vendors, and public files
- Live, dead, or unknown: triage the queue
- One key, three teams: rotate without an outage