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.
El comando exacto puede variar según el repositorio. Consulta el README en GitHub.
Para el autor de la skill
Pega en el README de tu repo
Muestra que tu skill está catalogada en Skillteca, genera backlink y tráfico rastreable.
[](https://www.skillteca.com.br/skills/postgres-hardening?utm_source=badge&utm_medium=readme&utm_campaign=badge)
Un email corto con solo las skills nuevas de Segurança. 4 minutos de lectura, sin spam, te das de baja con un clic.
Confirmas tu email en el primer envío. Sin spam. Te das de baja con un clic.
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.]
