SecureDB for Financial Services
Protect every account. Secure every transaction.
SecureDB keeps account numbers, card data and customer PII encrypted at the field level across core banking, payments, fraud and analytics systems, without slowing the business. Keys are protected with ML-KEM, NIST's post-quantum standard, so customer data copied today stays sealed after quantum computers arrive.
- No application changes
- Banks, credit unions & insurers
- Built for PCI DSS & GLBA data
Click Fraud team / Warehouse ETL to switch views
Cardholder data access logged Audit event #F-73360
Works with the databases behind your core, payments and analytics
- PostgreSQL
- MongoDB
- SQL Server
- Snowflake
- MySQL
- Oracle
- Azure SQL
- MariaDB
- Cosmos DB
- Db2
The gap
Customer data doesn't stay in the core.
Encrypted storage and secure connections protect account data where it starts. But once an authorized system reads it, card numbers and customer PII are in the clear, and they get copied into fraud tools, data lakes, warehouses, regulatory reports and test environments.
SecureDB keeps that data encrypted in every one of those places.
-
Usually covered
Data at rest
Volume and database encryption on core and card systems.
-
Usually covered
Data in transit
TLS between channels, payment apps and databases.
-
Exposed
In use & downstream
Queries, fraud analytics, ETL, regulatory reports and test copies.
-
Quantum-safe end-to-end
SecureDB runtime encryption
Field-level protection that follows account data, with role-based decryption.
Where account data travels
One customer record. Six places it ends up.
The same card number moves from the core into payments, fraud analytics, the warehouse, regulatory reporting and test systems. SecureDB protects it at every stop and decides who sees what.
-
Core banking
Accounts, balances and customers
Tellers: customer record -
Cards & payments
Authorization and settlement
Processing: PAN when required -
Fraud & AML
Monitoring and investigations
Fraud: by case, with approval -
Data warehouse
Analytics, risk and marketing
Analysts: tokenized values -
Regulatory reporting
Exams, filings and audits
Reporting: required fields only -
QA & test
Core upgrades and app testing
QA: no real customer data
Need-to-know, enforced
Same customer record. Four roles, four views.
Policies decide field by field what each role can decrypt. Consistent tokens still join across tables, so analysts can correlate activity without ever seeing a card number.
| Field | Branch teller Customer service | Fraud investigator Open case | Data analyst Risk & reporting | QA engineer Test environment |
|---|---|---|---|---|
| customer_name | Clear: Ana Ruiz | Clear: Ana Ruiz | Encrypted or tokenized: CUST_8841 | Encrypted or tokenized: Pz3!Hd8nT0 |
| tin | Partially masked: ***-**-7745 | Clear: 512-55-7745 | Encrypted or tokenized: Restricted | Encrypted or tokenized: e3Ns·Jh7w |
| card_number | Partially masked: •••• 1111 | Partially masked: 411111••••••1111 | Encrypted or tokenized: TKN_5e2a91 | Encrypted or tokenized: 9x3e·7Yc1 |
| balance | Clear: $8,214.03 | Clear: $8,214.03 | Clear: $8,214.03 | Encrypted or tokenized: 8x9q·2Kd7 |
| transactions | Partially masked: Last 90 days | Clear: Full history | Encrypted or tokenized: Tokenized | Encrypted or tokenized: Synthetic |
- Clear
- Partially masked
- Encrypted or tokenized
TKN_5e2a91 is the same token everywhere this card appears, so joins and fraud patterns still work on protected data.
How it works
From cardholder data discovery to audit in six steps.
OnData sits at the data layer, intercepting requests and enforcing policy in real time, with no changes to core banking or payment applications.
-
Identify
Find fields holding account numbers, cardholder data and customer PII.
-
Classify
Apply rules by data type, line of business, role, PCI DSS and GLBA.
-
Encrypt
Runtime encryption protects data while transactions keep processing.
-
Enforce
Identity-based decryption for payments, fraud and approved teams.
-
Extend
Protected data flows to fraud analytics, reporting, warehouses and test.
-
Audit
Access logged for investigations, exams and regulatory reporting.
Compliance alignment
Regulatory controls, built into the data.
SecureDB helps banks, credit unions, insurers and payment providers put cardholder and customer data requirements into practice at the field level.
PCI DSS references are to v4.0 requirements. CFR and NYCRR references are to federal and New York regulations. SecureDB supports compliance programs. It does not by itself make an institution compliant, and PCI DSS scope decisions rest with your QSA.
-
Render PAN unreadable
Card numbers encrypted wherever they're stored, including downstream copies.
PCI DSS Req. 3.5.1 -
Mask PAN when displayed
Only roles with a business need see more than the last four digits.
PCI DSS Req. 3.4.1 -
Need-to-know access
Access to cardholder data limited by role and job function.
PCI DSS Req. 7.2 -
Audit logs
Every access to cardholder data recorded and reviewable.
PCI DSS Req. 10.2 -
Encrypt customer information
Customer data encrypted at rest and in transit, and in use with SecureDB.
16 CFR §314.4(c)(3) -
Encrypt nonpublic information
Field-level encryption for NYDFS-regulated entities.
23 NYCRR §500.15
FAQ
Questions from financial services teams.
Have another question? Talk to our team →
Do we have to change core banking or payment applications?
No. SecureDB works at the data layer, so authorized applications keep working while sensitive fields stay protected.
Can fraud teams correlate activity without seeing card numbers?
Yes. Consistent tokens join across tables and systems, so analysts can follow patterns while card numbers stay protected. Investigators can decrypt by case, with approval.
Can SecureDB help reduce PCI DSS scope?
It can help. Systems that only ever see protected card data may fall outside parts of your cardholder data environment. Your QSA makes the final scope decision.
Can QA test with realistic data instead of production copies?
Yes. Test roles see encrypted or synthetic values in place of real customer data, so teams can test with realistic records without exposing real accounts.
Does it work for credit unions, insurers and payment providers?
Yes. The same field-level policies protect account, policyholder and cardholder data across core, claims and payment systems.
Is customer data protected against future quantum attacks?
Yes. SecureDB protects its encryption keys with ML-KEM, the NIST post-quantum standard (FIPS 203). Account and card data harvested today stays encrypted even after quantum computers can break today's public-key cryptography.
More for financial services
Protect customer data beyond the database.
-
SecureFile
Encrypt and track KYC documents, statements and loan packages.
Explore SecureFile -
SecureAI
Train fraud and service models without exposing raw customer data.
Explore SecureAI