SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01reconversion (server_version_num), data_directory, config_file and hba_file of the running cluster
2. 02reconcurrent pg_hba rules (trust? md5? 0.0.0.0/0?)
3. 03reconcurrent listen_addresses, ssl and password_encryption
4. 04reconroles whose password is still md5-hashed (blocks the move to scram)
5. 05reconactive remote connections not to cut
6. 06actBack up the configverify
7. 07actForce scram-sha-256 for new passwordsverify
8. 08actRestrict pg_hbadestructiveverify
9. 09actEnable SSLverify
10. 10actReloadverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyBack up the configVerified byls <hba_file>.bak.* | tail -1
2. 02verifyForce scram-sha-256 for new passwordsVerified bygrep password_encryption <data_directory>/postgresql.auto.conf
3. 03verifyRestrict pg_hbaVerified bysudo -u postgres psql -tAc "select count(*) from pg_hba_file_rules where error is not null or (type <> 'local' and auth_method = 'trust')"
4. 04verifyEnable SSLVerified byls <data_directory>/server.crt /etc/ssl/certs/ssl-cert-snakeoil.pem 2>/dev/null | head -1
5. 05verifyReloadVerified bysudo -u postgres psql -tAc 'show ssl'

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.05

Deploy on Servor button

Maintain Postgres Hardening or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.06

More database recipes

1. 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
2. 02MySQLMySQL Server, secured, bound to localhost, started and verified.
3. 03MariaDBMariaDB, secured, bound to localhost, started and verified.
4. 04MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
5. 05RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.