PostgreSQL and DevSecOps: Ensuring database security
summary
Argues that database security must be embedded continuously into CI/CD and gives concrete tooling and controls: Jenkins automation deploys agents, runs PSQL scripts and scheduled tests to “fail fast” and cut remedial work; use CIS/DISA baselines, configuration management to avoid snowflake servers, and automated compliance checks at every pipeline stage. Recommends Postgres features: PGcrypto column encryption, SSL/TLS, AES‑256 transparent encryption for tablespaces and WALs, data masking, and explicit key management (Court Vaughn Nitro key ubhsm). Claims this programmatic approach works to reduce surprises and meet PCI/PII controls.
AI-written summary · about
chapters (15)
- 0:00PostgreSQL and DevSecOps intro
- 2:50DevSecOps adoption challenges
- 6:40Jenkins in PostgreSQL
- 11:55PostgreSQL security baseline
- 15:29Security patching and compliance
- 17:14Encryption for PostgreSQL data
- 20:30Data masking and regulations
- 23:44Internal security partnerships
- 26:14Monitoring and compliance checks
- 28:20Access control and management
- 30:47CI/CD pipeline automation
- 32:12Key management best practices
- 34:42Programmatic security
- 35:46PostgreSQL security tools
- 36:30Security as continuous process
related talks
40mPostgreSQL and DevSecOps Ensuring database security in DevSecOps
50mPostgreSQL Security. How Do We Think?
50mSecuring PostgreSQL
07mAll about Postgres security
28mFrom Dev to Prod: Securing Postgres the Right Way
36mUnlocking the Benefits of Database DevOps and Automation
40mPostgreSQL Security for Application Developers
35mSecuring PostgreSQL From External Attack