PoastgreSQL Auditing, Authentication, and Security
summary
Describes a deployed system (JackDB) that centralizes authentication, rotates database credentials server‑side, and records immutable query logs across servers; it proxies libpq clients so psql and pg_dump work while enforcing ssl certificate validation and offering temporal permissions that grant one‑hour write access and immediately terminate connections when revoked. Role membership maps humans to data sources, audit entries include user/ip/sql, and search and full‑text indexing makes forensic queries practical — not vague examples but concrete features that run today.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:06Database Security
- 2:33What Is User Centered Security
- 3:51The Problems in Database Security
- 11:17Role Based Access Controls
- 13:52Audit Logging
- 16:25Demo
- 30:38Permissions
- 31:18Temporal Permissions
- 33:44I Think before Someone Was Saying Hey that Was a Long Pastor You Typed in Yeah It Is Long Your Password Should Be Long but You Shouldn't Have that Many Passwords You Know if You Have Less Pastors That You Only Have To Remember One Really Long Pastor Which Is Good since the Database Credentials Themselves for the Data Sources That Were Accessing or on the Server Side It's Really Easy To Rotate Them in this Case if I Want To Change like the Password for the Medicare Database for Example I Just Go In There and Change It in One Place and Everyone Accessing that Data Source Will Now Use the New Password I Don't Have To Tell People I Don't Have to You Know Write some Kind of Custom Script Updated in 10 Places
related talks
50mPostgreSQL Security. How Do We Think?
07mAll about Postgres security
50mSecuring PostgreSQL
44mWho's managing the credentials for your database?
38mPostgreSQL and DevSecOps: Ensuring database security
40mPostgreSQL Security for Application Developers
52mJackDB Database Development in your web browser
40mPostgreSQL and DevSecOps Ensuring database security in DevSecOps