Skip to content
← Services

Service · Audit

A PostgreSQL security audit where every finding is proven in SQL.

We review your PostgreSQL the way someone with valid credentials and bad intentions would: roles, grants, row-level policies, extensions, access configuration, and what your applications and AI agents can do today. Every finding comes with the query that proves it and reproduces on your own database.

It is for you if…

  • You are about to connect an AI agent, an assistant or an analytics tool to your production database and want to know what it can touch before granting access.
  • You keep several customers in one database (multi-tenant) and the separation depends on nobody making a mistake.
  • You inherited a database nobody documented: roles no longer used, grants nobody remembers giving.
  • A customer, an auditor or a board asks you for evidence of how the data is protected.

What it includes

  • 01

    Roles and privileges

    Who can read, write and change the schema; superusers that should not be; LOGIN roles that should not have it; grants inherited through PUBLIC.

  • 02

    Row-level security (RLS)

    Whether tenant separation lives in the database or only in the application; RLS tables without FORCE; policies that can be moved with SET or set_config.

  • 03

    Extensions and functions

    Which extensions are installed and what they can do; SECURITY DEFINER functions; triggers, rules and cascades that amplify a write.

  • 04

    Access and configuration

    pg_hba.conf, encryption in transit, authentication methods, parameters that leak data into the log.

  • 05

    What your AI agents can do

    Which statements would actually run if the model gets it wrong; where a row limit, a DDL ban or a record of what it proposed is missing.

  • 06

    Backups and recovery

    That the backup exists, is tested, and can be restored within a time your business tolerates.

How we work

Tell us about your database.

Two lines are enough: where it runs, how many databases, what worries you. We answer in English and Spanish.

Request an audit
  1. 01

    Scope in one conversation

    Which databases, which environments, what worries you. We define the access we need (read-only on the catalog is usually enough) and how you hand it over without secrets travelling by email or chat.

  2. 02

    Review with evidence

    Every finding is proven with a query you can run yourself. No "we recommend reviewing": we show what happens.

  3. 03

    Report and remediation plan

    Findings ordered by real risk, with the concrete change to close each one and what it can break if applied carelessly.

  4. 04

    Closing session

    We go through it with your team. If you want, we accompany the changes and measure again.

What you get

  • Report with every finding, its SQL evidence and its risk
  • Verification script to repeat the review on your database whenever you want
  • Prioritized remediation plan, with the exact change for each point
  • Closing session with your team, in English or Spanish

So there are no surprises

  • We do not need access to your data: the review works on the catalog and the configuration. Where data must be looked at, you run our query.
  • Price depends on the number of databases and the size of the schema: quoted after the scoping conversation. There is no public price.
  • If the database is healthy, the report says so. We do not inflate findings.

Who does it

Manuel Reyes Bravo, Chilean software engineer: author of the 7 PostgreSQL extensions on this site (Apache-2.0, published on PGXN) and credited on commits in the PostgreSQL core, verifiable on git.postgresql.org. Works in English and Spanish.

Frequently asked questions

PostgreSQL security audit

What access do you need?

For most of it, a read-only role on the catalog (pg_catalog, information_schema) and the configuration. Credentials never travel by email or chat: we agree on a channel and a temporary role you drop when we are done.

How long does it take?

It depends on the number of databases and the schema. A database with a few dozen tables is reviewed in days, not weeks. The exact timeline is set in the scoping conversation.

Is it useful if I do not use AI agents?

Yes. Roles, RLS, extensions, access and backups are the foundation of any PostgreSQL. The agents part is included only if you have them or are about to connect them.

Which PostgreSQL versions do you review?

Any community-supported version, managed ones included (RDS, Aurora, Cloud SQL, Supabase). If you run an unsupported version, the report flags it as a finding and proposes the upgrade path.

Can you apply the changes?

Yes, as part of the service or as separate consulting. We prefer your team applies them with us alongside, so the knowledge stays in-house.

Let’s talk

Tell us about your database.

Two lines are enough: where it runs, how many databases, what worries you. We answer in English and Spanish.

Request an audit
Try it Talk