Skip to content
Scout 0.3.0: new checks for reachable Go CVEs, IDOR, version disclosure, directory listing, SRI and mixed content.See the catalog

Dashboard & scheduled scans

scout serve starts a local web server with an embedded React dashboard: scan history, findings over time, and scheduled scans that run while it is up.

Terminal window
scout serve

Then open the URL it prints. The dashboard is compiled into the binary — there is nothing else to install or host.

The dashboard is protected by a username and password. In dev the defaults (admin / scout) are allowed; outside dev Scout refuses to serve with the defaults — set your own in the config:

username: admin
password: "a-strong-password"
jwt_secret: "a-long-random-string"

Define schedules in the config so scout serve runs them automatically:

targets:
- name: staging
url: https://staging.example.com
environment: staging
schedules:
- name: nightly
target: staging
cron: "0 2 * * *"

Each run is saved to history, so you can diff scans and the dashboard can chart findings over time.

Scout can notify you about new or regressed findings after each saved scan (see Configuration for the alerts block).

Restrict when scans may run (for example, off business hours) with a window in the config, so a scheduled or triggered scan never fires at a bad time.