Harden a PostgreSQL deployment whether managed or self-hosted. Covers pg_hba network and authentication rules, role separation (read-only, read-write, migration), row-level security for multi-tenant data, TLS configuration, backup encryption, and pg_audit logging. Invoke when provisioning a new Postgres, before opening it to a new app, or when reviewing a multi-tenant schema for isolation gaps.
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Drop this on your repo README
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/postgres-hardening?utm_source=badge&utm_medium=readme&utm_campaign=badge)
One short email with only the new Segurança skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
PostgreSQL Hardening
A practical baseline for a single Postgres instance (self-hosted or managed) that backs a web app. Skews toward small-team realities — not a regulated-environment DBA's playbook.
When to invoke
New Postgres provisioned (Docker, package, RDS, Supabase, Neon — same threat model)
Inheriting an existing Postgres with no documented hardening
Adding a new application or service that connects to an existing Postgres
After a Postgres security advisory
Reviewing a m
[Description truncada. Veja o README completo no GitHub.]
