Work through this list before people and integrations depend on an installation, and again after each major change. Each item links to where it's configured.
1. Secrets and keys
- CONFIG_ENCRYPTION_KEY is long and random, the same on every server, kept in a secret store, and backed up separately from the database backups it unlocks. Losing it makes every stored credential and every backup unreadable. See Environment variables.
- The setup key is no longer delivered to running servers (no SETUP_TOKEN), and the setup file was deleted.
- RECOVERY_TOKEN is kept in your secret store; the recovery page shows diagnostics only to its holder.
- Encrypt backups with public keys (age), and keep the private key offline.
- PAGINATION_CURSOR_SECRET is set, the same on every server.
2. Network and TLS
- Only the reverse proxy is reachable from users; the web app's port (3002) and the server's port (8080) are not.
- TLS everywhere: at the proxy, to PostgreSQL (sslmode=verify-full), to Redis (rediss://), to object storage.
- TRUSTED_PROXIES lists exactly your proxies, and FRONTEND_BEHIND_PROXY=true is set only with a proxy that overwrites the forwarded headers. See Behind a proxy.
- /api/ws routes to the server, so the system check has no Live updates warning.
- METRICS_ADDR is bound to a private interface, or metrics use METRICS_TOKEN. See Monitoring.
- Restrict the server's outbound network access to what it needs (your identity provider, mail service, storage and the sites plugins call).
- Automation webhooks to private addresses stay off (AUTOMATION_WEBHOOK_ALLOW_PRIVATE=false).
3. Browser security
- Leave the web app's Content-Security-Policy enforced (the default): don't set CSP_ENFORCE=false in production, and look into any [csp] line in its log.
- Give users:security (other people's sign-in history and addresses) only to the people who investigate sign-ins; organization admins hold it by default.
4. Identity and access
- People sign in through your identity provider: single sign-on (Enterprise) with Require single sign-on, or a synchronized directory. Multi-factor authentication is enforced there.
- Keep at least two super admins, and a documented break-glass procedure (SSO_ENFORCEMENT_OVERRIDE on one server) for when the identity provider is down.
- Anonymous access is off unless you mean to publish spaces to people who don't sign in (Settings → Security → Anonymous access; see Anonymous access).
- Sessions: lifetimes and the number of sessions per person fit your policy (Settings → Security → Sessions); AUTH_PASSWORD_MIN_LENGTH is 12 or more.
- CAPTCHA after failed sign-ins is on if the Wiki is reachable from the internet.
- Pipelines and integrations use workload identity or service accounts with narrowly scoped, expiring tokens; API tokens have IP allowlists where possible (Pro).
- Token lifetime and blocked permissions are enforced by policies (Maximum API token lifetime and Keep permissions out of API tokens templates).
- Space roles follow least privilege: Viewer to read, Commenter to comment, Editor to write and publish, Admin only for the people who manage a space's members and settings. See Spaces.
5. Plugins
- PLUGIN_SIGNING_REQUIRED=true; only plugins you trust are installed, with only the permissions they need. See Plugins.
6. Resilience
- Backups run daily to a target separate from the installation's storage, and a test restore has succeeded (Enterprise runs one weekly).
- The file storage (page attachments) has its own protection: versioning or replication on S3, snapshots on disk.
- PostgreSQL has point-in-time recovery from your platform.
- For a cluster: three or more servers, replicated PostgreSQL and Redis, pod disruption budgets on.
- The disaster recovery steps were rehearsed on a scratch installation.
7. Monitoring and audit
- The system check runs (Pro), and its alerts reach on-call through automation (webhook or email).
- Prometheus scrapes every server; alert on rate-limit refusals and Redis health. See Monitoring.
- Audit log retention (AUDIT_LOG_RETENTION_DAYS) meets your compliance needs; export to your SIEM if you keep it longer.
- Log files are collected centrally, with redaction on (LOG_REDACT_ENABLED=true).
8. Licensing and updates
- The license banner is on (LICENSE_BANNER_DAYS), and renewal is in someone's calendar.
- Someone follows the Wiki's security advisories, and upgrades follow Upgrades & maintenance.