Use casePostgreSQL database firewall
Stop risky SQL before it reaches PostgreSQL
SWOT DAM includes a database firewall, its SQL Gateway. It sits between your applications and PostgreSQL 16 or 17 and decides every statement against policy before it runs, with nothing installed on the database. A blocked statement returns the database’s own policy error; the session stays open.
PostgreSQL limits to know before a pilot
- 01
No client-certificate pass-through
Certificate logins fail through the gateway. Use SCRAM passwords.
- 02
Channel binding with TLS on both legs
The default listener needs channel_binding=disable. Use the SCRAM terminate listener instead.
- 03
Statements prepared inside functions
Statements prepared inside functions or procedures and run by name are refused in protect mode. Prepare them through the driver.
See it work
One query, two views
Pick a query from a sample PostgreSQL session and see what is stopped before it reaches the database, and what SWOT DAM sees inside.
Sample session by db_support on Billing PostgreSQL.
SWOT PAM · at the door
Connected as
pam_tmp_db_support_8c1 temporary, removed on disconnect
Verdict
SWOT DAM · inside
Audit record
Sensitive columns
Identity risk
How it works
How the PostgreSQL gateway works
Point clients at the gateway
Applications and tools connect to the SQL Gateway instead of the database. Verified on PostgreSQL 16 and 17: psycopg 3, pgjdbc 42.7 with HikariCP, psql and pgbench. For drivers or versions not listed, pilot first.
Decide every statement
Every statement is decided against policy before it runs. Rules match on user, source IP, sensitive tables, statement type and risk score.
SWOT DAMBlock the statement, keep the session
A blocked statement returns the database’s own policy error and the session stays open, so applications keep working. Traffic the gateway cannot read is refused, never passed on.
Monitor through pgAudit
SWOT DAM collectors read pgAudit, the database’s own audit trail, and score each identity against its own 30-day baseline.
SWOT DAM
The products
What each product does here
Does SWOT DAM work as a PostgreSQL database firewall with JDBC?
Yes. pgjdbc 42.7 with HikariCP is verified through the SQL Gateway on PostgreSQL 16 and 17, as are psycopg 3, psql and pgbench. For drivers or versions not listed, pilot first.
What does an application see when a statement is blocked?
The database’s own policy error. The session stays open, so the application keeps working; only the risky statement is stopped.
Can we log in with client certificates through the gateway?
No. The gateway has no client-certificate pass-through, so certificate logins fail; use SCRAM passwords. Every other limit is on the SWOT DAM gateway limits page.
See it on your own systems
A walk-through of SWOT DAM with the team that builds them.

