Configuring a scanner

configuring a scanner before a scanner can find secrets, it needs to know where to look trufflehog enterprise supports two deployment options, and the configuration approach differs slightly between them hosted scanner runs in truffle security's infrastructure, in an isolated environment dedicated to your tenant configure it entirely from the web ui connect sources and route notifications without managing any infrastructure every tenant starts with a default hosted scanner group, so you can be scanning within minutes best for getting started quickly self hosted scanner runs on hardware you operate (kubernetes, vm, etc) configure it through a local configuration file, and place it in its own scanner group you manage the compute; truffle security manages the detection logic and updates best for sources that aren't reachable from the public internet, or when data residency or network isolation requires scanning inside your environment note deployment support scan for secrets docid 91jgobvg nkxphml0ko7k many sources can be scanned by either a hosted or self hosted scanner, but a few are limited to one option check the individual source documentation for the deployment options supported by each