Your EDR was tested. Your database wasn't.
RowTrust runs safe, real-world attack techniques against your SQL Server and PostgreSQL instances and tells you, technique by technique, whether your audit, SIEM and monitoring would have caught them.
| Technique | Action | Result |
|---|---|---|
| T1110 | Password spray on SQL loginssa, svc_*, app_* · 40 attempts | DETECTED |
| T1548 | EXECUTE AS LOGIN via IMPERSONATE grantapp_reader → dbo on CoreBanking | MISSED |
| T1562 | ALTER SERVER AUDIT … STATE = OFFaudit gap: 00:00:41 | DETECTED |
| T1213 | Bulk SELECT on dbo.Customers2.1M rows read, canary columns | MISSED |
| T1059 | xp_cmdshell re-enabled via sp_configureblocked by policy-based management | BLOCKED |
| T1490 | Delete backup history & .bak copiesmsdb.dbo.sp_delete_backuphistory | MISSED |
Security validation stops one layer too early
Breach and attack simulation tools test endpoints, networks, email and cloud. The database, where the customer records, ledgers and policies actually live, is usually covered by a handful of generic checks. Attackers go there last, and that is where most programmes stop testing.
Email & phishing
Endpoints & EDR
Network & firewall
Cloud & identity
Databases: logins, permissions, audit, backups
Agent in. Attacks run. Evidence out.
Built the way a DBA would want it: nothing installed on the database server itself, every action logged and reversible, and a scope you sign off before anything runs.
A lightweight agent inside your network
One container or Windows service that connects to the instances you choose, with the credentials you grant. Start on a pre-production copy, move to production in safe mode.
Run real attacker techniques, safely
Each technique uses canary objects and rollback steps. Privilege changes are reverted, test data is synthetic, and destructive scenarios run against copies only.
See what was blocked, detected or missed
Every result is mapped to MITRE ATT&CK, linked to the audit or SIEM event that should have fired, and paired with the T-SQL or configuration change that closes the gap.
Techniques written by DBAs, not generic scanners
A first look at the catalogue. Each technique has an engine-specific implementation, a safe mode, a cleanup routine and the detection it is meant to trigger.
| ATT&CK | Technique | What RowTrust does | Engines |
|---|---|---|---|
| T1078 | Valid accounts | Logs in with orphaned, shared or default SQL logins and weak pg_hba.conf entries. | SQL ServerPostgreSQL |
| T1110 | Brute force | Password spraying across SQL logins at rates that should trip lockout and alerting. | SQL ServerPostgreSQL |
| T1548 | Privilege escalation | IMPERSONATE grants, TRUSTWORTHY databases, db_owner to sysadmin paths, SECURITY DEFINER functions. | SQL ServerPostgreSQL |
| T1059 | Command execution | xp_cmdshell, CLR assemblies, Agent job steps, COPY … TO PROGRAM. | SQL ServerPostgreSQL |
| T1505.001 | Persistence via stored procedures | Startup procedures and hidden triggers that survive restarts. | SQL Server |
| TA0008 | Lateral movement | Hops through linked servers and dblink / postgres_fdw with stored credentials. | SQL ServerPostgreSQL |
| T1562 | Impair defenses | Disables or alters SQL Server Audit, Extended Events and pgaudit settings. | SQL ServerPostgreSQL |
| T1213 | Data collection | Bulk reads of sensitive tables using canary rows and columns. | SQL ServerPostgreSQL |
| T1048 | Exfiltration | BCP, OPENROWSET, COPY TO and outbound connections from the instance. | SQL ServerPostgreSQL |
| T1490 | Inhibit recovery | Backup history deletion, broken log chains, WAL archive tampering, replica and AG interference. | SQL ServerPostgreSQL |
Destructive techniques (T1490 and the ransomware scenarios) run only against restored copies.
Regulators now expect proof, not policy
European financial entities and critical operators have to show that their defences work under realistic conditions. RowTrust produces that evidence for the layer that holds the data.
Resilience testing
Applies to banks, insurers and investment firms since January 2025, with a programme of regular ICT resilience testing.
Effectiveness of measures
Asks essential and important entities to assess whether their cybersecurity risk-management measures actually work.
Evidence your auditors can read
Dated results per technique, the control expected to respond, and the fix, in a report you can hand to internal audit.
Start with an assessment. Keep testing with the platform.
Most teams begin with a fixed-scope assessment on a pre-production copy, then move to continuous runs once the first gaps are closed.
Community library
- Core techniques as T-SQL and SQL scripts
- Safe mode and cleanup for each one
- Run them yourself, by hand
Database Attack Assessment
- Scoping call and rules of engagement
- Full library run on up to 5 instances
- Findings mapped to MITRE ATT&CK
- Remediation scripts and a debrief with your DBAs and SOC
RowTrust Platform
- Agent and web console
- Scheduled runs and drift alerts
- Trend of your detection coverage over time
Built by a DBA who has spent twenty years on the receiving end of the 3 a.m. call.
RowTrust comes from more than two decades of running SQL Server and PostgreSQL estates for banks, insurers, telcos and commodity traders across Europe: replication, Availability Groups, backups, audit, and the gaps between them.
Find out what your database would miss
Tell us about your estate. We reply within two working days with a proposed scope.
Email: rowtrust@pacificit.solutions