--- title: PostgreSQL Security Hardening | daily.dev description: A comprehensive guide to hardening PostgreSQL databases across three layers: network-level security (firewalls, iptables, reverse tunneling, listen_addresses),... canonical: https://daily.dev/posts/postgresql-security-hardening-cae8sghk0 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: PostgreSQL Security Hardening | daily.dev og:description: A comprehensive guide to hardening PostgreSQL databases across three layers: network-level security (firewalls, iptables, reverse tunneling, listen_addresses),... og:url: https://daily.dev/posts/postgresql-security-hardening-cae8sghk0 og:image: https://api.daily.dev/og/posts/cae8SGHK0.png og:image:alt: PostgreSQL Security Hardening og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # PostgreSQL Security Hardening **[Teleport](https://daily.dev/sources/teleport)** · 14 min read · 0 upvotes · 0 comments ## Summary A comprehensive guide to hardening PostgreSQL databases across three layers: network-level security (firewalls, iptables, reverse tunneling, listen_addresses), transport-level security (TLS/SSL certificates for server and client authentication, pg_hba.conf configuration), and database-level security (roles, permissions, row-level security policies, and auditing via logging or pgAudit). Concludes with a promotion of Teleport for Database Access as a tool implementing these practices with certificate-based access, SSO/LDAP integration, and audit logging. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I set up row-level security in PostgreSQL to let users only update their own rows? Enable row-level security on the table with ALTER TABLE server_inventory ENABLE ROW LEVEL SECURITY, then define policies using CREATE POLICY. A SELECT policy can use USING (true) to allow viewing all rows, while an UPDATE policy can use USING (current_user = owner) WITH CHECK (current_user = owner) to restrict updates to rows owned by the connecting user. _daily.dev surfaces practical database access-control patterns like this for teams locking down production data._ ### How do I require client certificate authentication for PostgreSQL connections instead of passwords? Configure postgresql.conf with ssl = on, ssl_cert_file, ssl_key_file, and ssl_ca_file pointing to a client certificate authority, then set pg_hba.conf entries to hostssl with the cert method for all addresses. Clients must present an X.509 certificate whose CommonName field matches the database role name, and connect with sslmode=verify-full for full server validation. _developers hardening database connections can track TLS and auth configuration guides on daily.dev._ ### How can I hide sensitive columns from certain PostgreSQL roles while still letting them query a table? Grant column-level SELECT privileges instead of table-wide access, for example GRANT SELECT(id, description) ON server_inventory TO intern excludes the ip_address column from that role's visibility. Assign a login role to the group role afterward, for example GRANT intern TO charlie, so the user inherits only the permitted columns. _engineers designing least-privilege access schemes can find more PostgreSQL role patterns on daily.dev._ ## Similar posts on daily.dev - [PostgreSQL Explained: A Complete Beginner-to-Advanced Guide](https://daily.dev/posts/postgresql-explained-a-complete-beginner-to-advanced-guide-euthfe3bb) · DigitalOcean Community · 0 upvotes · 0 comments - [PostgreSQL Disaster Recovery with pgBackRest TLS Transport](https://daily.dev/posts/postgresql-disaster-recovery-with-pgbackrest-tls-transport-iltuvmsnz) · Planet PostgreSQL · 0 upvotes · 0 comments - [Amazon RDS for PostgreSQL now supports post-quantum TLS key exchange](https://daily.dev/posts/amazon-rds-for-postgresql-now-supports-post-quantum-tls-key-exchange-ymuendp7r) · AWS · 1 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/postgresql-security-hardening-cae8sghk0) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"PostgreSQL Security Hardening","url":"https://daily.dev/posts/postgresql-security-hardening-cae8sghk0","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/postgresql-security-hardening-cae8sghk0"},"datePublished":"2026-08-23T12:19:09.745Z","dateModified":"2026-08-23T12:35:38.471Z","description":"A comprehensive guide to hardening PostgreSQL databases across three layers: network-level security (firewalls, iptables, reverse tunneling, listen_addresses),...","image":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","thumbnailUrl":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/postgresql-security-hardening-cae8sghk0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,postgresql","timeRequired":"PT14M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"PostgreSQL Security Hardening"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/postgresql-security-hardening-cae8sghk0#faq","mainEntity":[{"@type":"Question","name":"How do I set up row-level security in PostgreSQL to let users only update their own rows?","acceptedAnswer":{"@type":"Answer","text":"Enable row-level security on the table with ALTER TABLE server_inventory ENABLE ROW LEVEL SECURITY, then define policies using CREATE POLICY. A SELECT policy can use USING (true) to allow viewing all rows, while an UPDATE policy can use USING (current_user = owner) WITH CHECK (current_user = owner) to restrict updates to rows owned by the connecting user. daily.dev surfaces practical database access-control patterns like this for teams locking down production data."}},{"@type":"Question","name":"How do I require client certificate authentication for PostgreSQL connections instead of passwords?","acceptedAnswer":{"@type":"Answer","text":"Configure postgresql.conf with ssl = on, ssl_cert_file, ssl_key_file, and ssl_ca_file pointing to a client certificate authority, then set pg_hba.conf entries to hostssl with the cert method for all addresses. Clients must present an X.509 certificate whose CommonName field matches the database role name, and connect with sslmode=verify-full for full server validation. developers hardening database connections can track TLS and auth configuration guides on daily.dev."}},{"@type":"Question","name":"How can I hide sensitive columns from certain PostgreSQL roles while still letting them query a table?","acceptedAnswer":{"@type":"Answer","text":"Grant column-level SELECT privileges instead of table-wide access, for example GRANT SELECT(id, description) ON server_inventory TO intern excludes the ip_address column from that role's visibility. Assign a login role to the group role afterward, for example GRANT intern TO charlie, so the user inherits only the permitted columns. engineers designing least-privilege access schemes can find more PostgreSQL role patterns on daily.dev."}}]} ```