Operations
Security
Hardening checklist for a private or public instance.
Before opening network access
- Use a unique administrator password and unique passwords for any reader accounts used for sign-in; manage them in Settings.
- Preserve persisted keys and the existing
NASDASH_JWT_SECRETconfiguration. - Keep secrets out of version-controlled files.
- Enable HTTPS or private VPN access.
- Keep Docker APIs private and limit integration read permissions.
- Verify access with a reader account.
- Back up all of
/app/data, test restoration and update regularly.
The official container runs the application with the UID/GID 1001. When using a bind mount, grant this user access to the directory without making it globally writable.
Sensitive data
Integration tokens are masked in standard responses and encrypted in persistent configuration. Encryption continuity depends on the keys stored in /app/data and your stable secrets: back up the entire directory, not just config.json.
Reporting a vulnerability
Do not open a public ticket containing an unpatched vulnerability, a private IP address, or a secret. Follow the security policy for contributors.