Database Migration Studio runs on your workstation or CI runner. It never transmits schema metadata, connection strings, credentials, or table rows to external servers.
ConnectionConfig.passwordis markedskip_serializingin Rust so exportedplan.jsonfiles,report.json,report.html, and localstate.dbjob records do not store database passwords.Debugformatting on connection configs prints[REDACTED]in place of secrets.- CLI execution reads passwords from
DBMIGRATE_SOURCE_PASSWORDandDBMIGRATE_TARGET_PASSWORDenvironment variables or OS credential storage. - SQL identifiers are quoted per dialect (
quote_ident_pg,quote_ident_mysql,quote_ident_sqlite), embedded quotes are doubled, and NUL bytes are rejected. Values are bound via parameterized queries.
If you discover a SQL injection path, secret leak in logs or reports, or data-loss edge case, open a private security advisory on GitHub at https://github.com/sql-devops/database-migration-tools/security/advisories/new.