Secure a QilbeeDB container deployment
Use a supported QilbeeDB image, persistent storage and credentials with only the permissions your application needs. A healthy process does not establish that an installation is secure or that its backups can be restored.
Choose and update an image#
Pin production deployments to an immutable image digest. Record the version and review its release notes before upgrading. Scan the exact image you intend to run, including its operating-system packages, and assess findings against your organization's security policy. Recheck images as vendor advisories change.
Do not treat passing API tests as proof that system libraries are patched. If a finding affects your deployment, apply an available supported update or mitigation and repeat your integration and recovery checks. Retain package metadata so your scanner can identify installed dependencies.
Limit runtime privileges#
Run the server as a non-root user. Keep the root filesystem read-only, drop
unneeded Linux capabilities and disable privilege escalation. Store persistent
data on the volume mounted at /data; use temporary storage for /tmp.
Expose the API only to intended clients. Network-facing deployments need TLS, authentication and scoped authorization. Keep operator keys outside images, source control and application logs. Separate global administration from routine application credentials, and revoke credentials that are no longer needed.
Understand the health check#
The native qilbeedb health-check command checks the local HTTP service at
127.0.0.1:7474. It requires a healthy response with the expected server version,
uses timeouts, bounds the response size and refuses redirects.
Use health checks for process availability. Verify authenticated operations and storage recovery separately; a successful probe does not prove that a particular credential can read or write its intended scope.
Verify recovery before upgrading#
Keep an application-consistent backup and test restoration to separate storage. Check the target release's storage compatibility before opening existing data with a new binary. Do not reopen an upgraded data directory with an older binary unless that downgrade is explicitly supported.
After writes resume, restoring an earlier backup can discard newer changes. Reconcile those writes before any rollback. See backup and recovery and the release notes for applicable limits.