Skip to main content

Protect your data

Keep originals independently recoverable​

Jiandu preserves durable originals, but the installation can still be lost through hardware failure, operator error, stolen credentials, or a broken storage service. Use at least one backup copy on a different failure domain and test it.

Separate everyday and recovery access​

Use named accounts for normal work. Keep the Owner recovery token offline, owner-readable, and accessible to the person responsible for recovery. Do not use it as an integration token.

Minimize exposure​

  • Publish only HTTPS through the reverse proxy.
  • Keep the backend port, database, and storage endpoints private.
  • Scope object-store, WebDAV, database, and connector credentials narrowly.
  • Expire personal access tokens and revoke unused sessions.
  • Enable outbound telemetry or plugins only after reviewing the new trust boundary.

Avoid secret sprawl​

Configuration examples should be safe to commit because they contain no live secrets. Inject secrets using your deployment platform or protected secret-reference files. If a secret appears in a shell transcript, issue, CI log, or Git history, treat it as compromised and rotate it.

Verify access using ordinary accounts​

Administrators often see more controls than Members. Maintain a non-sensitive test document and Member account to verify the public route, sign-in, search, original access, and restrictions after changes.

Last updated on