# Why Postgres needs better connection security defaults

DevFeed: [Why Postgres needs better connection security defaults](<https://devfeed.tech/articles/why-postgres-needs-better-connection-security-defaults-5736.md>)

Original publisher: [Read original article](<https://neon.com/blog/postgres-needs-better-connection-security-defaults>)

Author: George MacKerron

Published: 2025-06-25T14:44:21Z

Content type: article

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Databases](<https://devfeed.tech/topics/databases.md>), [client](<https://devfeed.tech/topics/client.md>)

Tags: [blog-post](<https://devfeed.tech/tags/blog-post.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [security](<https://devfeed.tech/tags/security.md>)

## AI overview

The article explains why Postgres connections using sslmode=require are insecure: they encrypt communication without authenticating the server, leaving connections vulnerable to man-in-the-middle attacks. It contrasts this with sslmode=verify-full and discusses the Postgres 16 parameter sslmode=verify-ca, which uses trusted PKI certificates to authenticate servers, including Neon databases.

## Source excerpt

In this post: why are Postgres connections with sslmode=require insecure? How does Neon ensure secure connections? And what needs to happen to make secure Postgres connections the norm? It's common to see sslmode=require on the end of a Postgres connection string. Maybe your own...