Production checklist
Work through this checklist before Sentinel serves production traffic. Each item says what to check, why it matters, and where the details are.
License
- An active license is set in
[license]. Without one,GET /v2/challenge,POST /v2/verify, and the detection endpoints answer403 LICENSE_NOT_ACTIVE. See Licensing. - Staging uses a non-production license. Its responses carry
X-Sentinel-License: non-production, so test traffic is easy to tell apart. See Non-production licenses. - License expiry is alerted on. Alert on
altcha_sentinel_license_expiry_timestamp_seconds - time()and watch thelicense_expiredandlicense_refresh_failingalerts. See Alerts and metrics.
Configuration & secrets
jwt_secret,altcha_hmac_secret, andencryption_keyare set explicitly with${file:…}or${VAR}. Sentinel generates them only on embedded SQLite and refuses to start without them on any other database. See Server secrets.- Every replica uses the same secret values. A mismatch causes
401sessions and undecryptable API keys behind a load balancer. See Share them across replicas. - Secrets are backed up with the database. A database restored without its
encryption_keyhas unreadable API key and TOTP secrets. See Generated secrets on embedded SQLite. altcha-sentinel doctorpasses on every replica. It validates the configuration and checks connectivity and security warnings. Seedoctor.
Exposure
- The admin UI isn't public. Keep
[server.admin_ui]behind a VPN or restrict it withallowed_ips. See Choose what to expose. - The widget is served from the public listener.
[server.public_api]exposes only the widget endpoints, so the main API can stay on your private network. See Public widget API. allowed_hostsis set on every exposed listener. Requests for other hosts get421, which blocks DNS rebinding. See Allowed hosts./.healthand the Prometheus listener are private. Keephealth_allowed_ipsto private networks and probers, and protect metrics withallowed_ipsorbearer_token. See Health endpoint and[prometheus].- Every exposed listener uses HTTPS. Set listener
tlsor terminate TLS at a proxy; the admin session cookie needs HTTPS outsidelocalhost. See HTTPS.
Reverse proxy
trusted_proxieslists your proxies. Otherwiseclient_ip_headerand forwarded hosts are accepted from any peer, and clients can choose their own IP. See Client IP.client_ip_headermatches your CDN, if you use one. For exampleCF-Connecting-IP; rate limits, penalties, and IP rules depend on the right client IP. See Client IP.base_urlis the public URL of each widget listener. It prefixes the URLs handed to the widget and is the OAuth and passkey URL. See Public URL.[server] idle_timeoutis above the proxy's keep-alive timeout. Otherwise reused connections can return502. See Connection timeouts.
Credentials
- Widget keys are
public. Onlypublickeys work on the widget endpoints, and their id is visible in the page. See Credential matrix. - Backend keys are
restricted. They call the detection endpoints with Basicid:secretand can't manage Sentinel. See Restricted vs full. fullkeys are used only by automation that manages Sentinel. Their security group's role sets what they can change. See Restricted vs full.- Key secrets are rotated by replacing the key, and the old key gets an expiry. Secrets can't be regenerated in place; an
expiresAton the old key stops it even if nobody deletes it. See Rotate a secret. - Your backend verifies every submission. Check the widget's payload with
POST /v2/verify/signatureor a server library before trusting the form. See Verify with Sentinel and TheverificationDatafields.
Rules
- Widget security groups start from the Recommended preset. See Recommended.
- New rules and presets run in monitor mode first. Monitored rules are evaluated and logged but have no effect. See Monitor mode.
- Rules are checked with a
GET /v2/inspectrule trace, then the trace is turned off.[inspect] security_rulesshows callers which conditions they trip, so use it for debugging only. See Inspect with a rule trace.
Availability
- Multiple replicas share Redis or Valkey. The built-in KV store works for a single instance only. See Redis and Clustering.
- Redis runs with
maxmemory-policy noeviction. Evicting a replay claim lets a solution be accepted again. See Redis or Valkey. - Each replica has a unique
HOSTNAME. Sentinel uses it to claim license instance slots. See Before you go live. - Database TLS verifies the server. PostgreSQL, MySQL, and MariaDB don't verify certificates by default; set
sslmode=verify-fullorssl-mode=VERIFY_IDENTITY. See Database TLS. pool_max× replicas stays below the database's connection limit. Leave room for rolling deploys. See Connection pool.
Data & backups
- Snapshots are scheduled to storage. Set
[snapshots] identity,schedule, and a[storage]provider, and add an offline age key torecipients. See Snapshots and[snapshots]. - A restore has been tested. Restore a snapshot into a staging deployment before you need it. See Snapshots.
Monitoring
- Prometheus scrapes every replica. See Monitoring.
- Alerts have a delivery channel. Configure webhooks, email, or push so alerts reach someone. See Alerts and
[alerts]. - High-volume request logs go to ClickHouse. With
[clickhouse] urlset, request logs leave the main database. See ClickHouse.
Admin access
- The bootstrap root password has been changed. A generated password stays in your logs. See The bootstrap root password.
- Root and admin users use two-factor authentication or passkeys.
doctorwarns about root users without it. See Sign-in. - SSO is configured if you use one, and
[auth] password_login = falseif you require it. See Sign-in and[auth].
Privacy
[privacy] anonymize_ipmatches your privacy policy. It truncates client IPs in request logs, audit logs, alerts, and log lines. See Privacy.- Each API key's
requestLoggingis no higher than you need.none,verification, oralldecides which requests are stored. See Request logging and Request logs.