Connector guide
Connect SQLite safely
Governed analysis of a small, encrypted database artifact
1. Prepare a safe copy
Export a separate SQLite copy containing only the tables and columns Maya may analyze. Never upload a live application database or a file containing credentials.
2. Restrict network and authentication
- SQLite is uploaded as an encrypted artifact; it does not open a network listener.
- Maya opens a temporary copy in immutable read-only mode.
- The temporary file is permission-restricted and deleted after each query.
3. Expose only approved data
- The current artifact limit is 8 MB.
- Use views or a sanitized copy to remove sensitive fields.
- Only the main namespace and explicitly approved attached namespaces may be queried.
4. Verify before connecting
- Run PRAGMA integrity_check before export.
- Confirm no secrets, tokens, or regulated data remain.
- Reconnect whenever the source copy changes.
5. Rotate and revoke
Rotate secrets or keys on a defined schedule and immediately after suspected exposure. Disconnect the integration in Maya before disabling the external identity, and retain only non-sensitive audit metadata.