Security techniques for cross database access
summary
Compares four concrete ways to allow cross-database queries and shows demos that work or fail: naive approach grants users in every target DB (works but scales terribly); ownership chaining (DB chaining) works without extra object permissions but requires identical database owners and per-database enabling; set TRUSTWORTHY off is recommended because turning it on lets module code escape the database (execute as owner becomes server‑privileged); certificate-signed stored procedures let a proc access remote objects without granting user rights, but the proc must be re‑signed after changes.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:01Security challenges
- 2:03Scenario setup
- 6:04Basic permission granting
- 11:47Ownership chaining
- 17:31Cross-database chaining
- 31:55Trustworthy property risks
- 48:52Signed procedures
related talks
22mComplete database security in 4 simple steps
25mEnsuring Authorized Updates in Multi-user Database-Backed Applications
54m10 Deadly Sins of SQL Server Configuration
21mWhat you can do to protect your SQL Server and why it matters
21mWhat you can do to protect your SQL Server and why it matters
40mPostgreSQL Security for Application Developers
01h 00mSecuring Multitenant Databases with Entity Framework Core
48mTackling the Recent Rise of Cross-Tenant Vulnerabilities
