Trust & Security
DBX inspects production databases, so how we handle access and evidence matters as much as what we find. This page states precisely what the scanner requires and what it does not.
Restricted scanner permissions
DBX is designed to run as a dedicated database role with the least privilege required to read security metadata. The scanner reads catalog and information-schema objects; it is not designed to read application rows.
- — Required: CONNECT, USAGE on inspected schemas, and SELECT on catalog views
- — Not required: application user passwords, service-role keys where avoidable, write or DDL privileges, application secrets
Credential handling
Database credentials are submitted directly to server-side functions over TLS and stored through an encryption abstraction. They are never rendered back to the browser after submission, never written to logs or error messages, never attached to analytics events, and never placed into AI prompts.
Disconnecting a database removes stored credentials and disables future scans.
Tenant isolation
Every application table is scoped to an organization and protected by row-level security so one organization cannot read another organization's projects, scans, findings, or evidence.
Scanner methodology
Findings are produced by a deterministic rule engine evaluating introspected facts and a permission graph. Each finding records the machine-derived evidence that produced it, so any reviewer can re-derive the verdict from the same facts. A language model is used only to explain verified findings and draft remediation for human review; it never decides whether a finding exists.
Data retention
Scan facts and findings are retained for the period configured on your plan. Deleting a project deletes its scan history and evidence.
Responsible disclosure
If you believe you have found a security issue in DBX, contact security@schemaforge.example with reproduction steps. We will acknowledge receipt and keep you informed while we investigate.
Subprocessors
A current subprocessor list is maintained for customers on request. It is not yet published here.
Limitations
DBX analyzes database configuration. It does not test application code, network controls, or client authorization logic, and it cannot observe risks that are not expressed in database metadata. It does not certify a database as secure and holds no compliance certification. Absence of findings means only that no issue was detected by the current checks.