.%20TODO(brand):%20replace%20with%20the%20master%20vector%20from%20the%20brand%20files.%20--%3e%3cdefs%3e%3clinearGradient%20id='rudratic-mark'%20x1='0'%20y1='195'%20x2='0'%20y2='828'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20offset='0'%20stop-color='%235a0bd8'%20/%3e%3cstop%20offset='1'%20stop-color='%23a5157c'%20/%3e%3c/linearGradient%3e%3c/defs%3e%3cg%20fill='url(%23rudratic-mark)'%3e%3cpath%20d='M253%20448%20545%20195l60%2070-292%20252z'%20/%3e%3cpath%20d='M348%20558%20473%20450v200L348%20768z'%20/%3e%3cpath%20d='M523%20405%20640%20305l83%2097-141%20120%20153%20128-102%2087-110-97z'%20/%3e%3cpath%20d='m663%20763%2072-61v126z'%20/%3e%3c/g%3e%3c/svg%3e){kind=small}
Use caseDatabase security
Control who gets into the database, and see what they do there
Database security has two halves: governing privileged access in, and watching the activity inside. SWOT PAM controls the first; SWOT DAM covers the second, for every account, applications included.
Why databases are hard to secure
- 01
Shared database logins
DBAs and support staff often share powerful database accounts, so actions cannot be tied to a person.
- 02
Applications hold the keys
Service accounts with broad rights read sensitive tables every day; a change in their behaviour is easy to miss.
- 03
Nobody knows where the sensitive data is
Personal, financial and health data spreads across new tables and columns faster than anyone documents it.
See it work
One query, two views
Pick a query from a sample session and see what SWOT PAM does at the door 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
Access and activity, covered together
Govern the way in
Database access through the SWOT PAM proxy: each session gets a temporary database account that is removed on disconnect, and PAMGuard can drop a DROP TABLE before it arrives.
SWOT PAMRead the native audit
SWOT DAM collectors read Oracle, PostgreSQL, SQL Server and MySQL audit trails with read-only access, with no inline proxy.
SWOT DAMScore every identity
Each account is scored from 0 to 100 against its own 30-day baseline, and four alert rules catch schema changes, escalation, brute force and mass reads.
SWOT DAMFind the sensitive columns
The Sensitive Data Sentinel classifies new columns every 24 hours from the catalogue, never reading the data itself.
SWOT DAM
The products
What each product does here
What is the difference between PAM and DAM for databases?
PAM governs privileged access into the database: who may connect, when, and through a recorded, checked session. DAM monitors activity inside the database from its own audit trail, for every account including applications, and scores it for risk.
Which databases are covered?
SWOT PAM proxies PostgreSQL and Oracle, and offers browser SQL for PostgreSQL, Oracle, MySQL and SQL Server. SWOT DAM reads Oracle, PostgreSQL, SQL Server, MySQL and MariaDB, Amazon RDS and Aurora, Azure SQL and Google Cloud SQL.
Does monitoring slow the database down?
SWOT DAM does not sit inline: collectors poll each native audit trail with read-only credentials, so query paths do not change.
Is our data copied anywhere?
No. SWOT DAM reads catalogue metadata and audit and system views, never your business tables, and the Sentinel classifies column names and types, not values.
See it on your own systems
A walk-through of SWOT PAM and SWOT DAM with the team that builds them.