Scattered trails
Every database platform writes its audit log in its own format, with its own fields.
Data Evidence, Verified
Who changed this data, and can you prove it?
Evidatix turns the native audit logs from every database you run into one verified evidence trail of data, schema and access changes. Built for banking, financial services and insurance in India.
Data stays in India · SaaS or on-prem · Priced per database
Evidence record · sampleVerified
- Time (IST)
- 14 Nov 2026, 11:42:07
- Class
- DML · UPDATE
- Database user
- app_lms_rw
- Client host
- 10.20.4.31 · lms-batch
- Object
- loans.disbursal_limits
- UPDATE disbursal_limits SET max_amount = 2500000 WHERE branch_id = 118;
Block 0x7f3a…c21e · chain intactExport checksum matches
Jul 2026RBI DirectionsAudit trails for NBFCs and co-operative banks
In forceSEBI CSCRFDatabase and audit-trail logs for regulated entities
180 daysCERT-InLog retention within India
~May 2027DPDP RulesOne-year logs of personal-data access
The audit problem
The answer exists. It just takes weeks to assemble.
Weeks of preparation
Teams hand-write queries, take screenshots and reconcile counts before every inspection.
Counts that don't hold
Unreconciled totals and missing sources turn into audit observations.
“Who changed this data, schema or access, when, from where, and can you prove it?”
How it works
From native audit logs to evidence your auditor accepts
No proprietary agents on your databases. Evidatix uses each platform's own audit and lightweight collectors.
Collect
Native audit from every database, through lightweight collectors.
Buffer
Every event is kept and can be replayed, so nothing is lost.
Normalise
One model for data (DML), schema (DDL) and access (DCL) changes.
Seal
Receipts are hash-chained and anchored daily in India.
Prove
Dashboards, reports and exports all read the same evidence.
Why Evidatix
Six reasons it wins the audit
One model, every platform
All leading database platforms in one view of who changed what.
One set of numbers
Dashboards, reports and exports read one published evidence set, so the answer never changes.
Verifiable exports
CSV with a manifest, record counts and checksums your auditor can check independently.
Proof of coverage
Every enabled source is listed, so a quiet database shows as quiet, not missing.
Built for compliance teams
Search pages and saved reports. No SOC team or query language needed.
Priced per database
Unlimited events and 180-day retention in India. Never charged per gigabyte.
Trust by design
Tamper-proof ready, verifiable by your auditor
Changes are prevented by insert-only writes and locked roles. Anything that gets past them is detected by the hash chain and the daily anchors.
Sealed
Hash-chained receipts, sealed in blocks at ingestion.
Anchored
Daily anchors in India-region WORM storage.
Locked down
Insert-only writes, locked admin roles, admin activity audited.
Verifiable
Exports carry checksums your auditor can verify without access to Evidatix.
Integrity starts at ingestion. Upstream, transport is encrypted and per-source gap detection flags missing events.
Evidatix and your SIEM
Keep your SIEM for threats. Use Evidatix for the audit.
| Question | Typical SIEM | Evidatix |
|---|---|---|
| Built for | Threat detection across the estate | Proving database activity to auditors |
| Pricing | Data volume, devices or users | Per database, unlimited events |
| Database parsing | Generic, custom work per platform | Native readers per platform, maintained |
| Event counts | Multi-stage events can double-count | Stages merged; failed parses quarantined |
| Coverage proof | Shows sources that sent logs | Lists every source, even quiet ones |
| Evidence output | Search results and ad hoc exports | CSV with manifest and checksums |
| Real-time alerting | Strong and mature | On the roadmap; keep your SIEM for this |
Who it's for
Built for India's regulated finance
NBFCs
RBIOne trail across core, lending and LOS databases for the IS auditor.
Co-operative banks
RBIAudit-log and database-integrity evidence without a SOC team.
Asset managers
SEBIDatabase and audit-trail logs ready for the CSCRF cyber audit.
Wealth managers and PMS
SEBIAudit-ready from day one, sized for a small team.
Insurers and brokers
DPDPVerified logs of who accessed and changed policy and claims data.
BFSI startups
ALLEvidence in place before your first inspection or investor review.
Deployment and pricing
Simple to run, simple to budget
- Priced per database instance, in annual tiers. Never per gigabyte or per event.
- Included in every tier: unlimited events, 180-day retention in India, verified exports and read-only auditor seats.
- Fair instance counting: a database with its replicas counts once; DR copies are free.
- Partner pricing for core-banking vendors serving co-operative banks.
India-region SaaS
Fastest start for startups, wealth firms, smaller NBFCs and co-operative banks.
On-prem or private cloud
For larger NBFCs and AMCs whose data policies keep everything in-house.
Start with a 30-day paid pilot
One or two databases, your own audit questions, and the fee credited to your first year.
- Connect native audit on your chosen databases
- Collect every data, schema and access change
- Prove it with an export your auditor verifies
Questions
What buyers ask us
Will Evidatix make us RBI or SEBI compliant?
No product can; compliance is the regulated entity's responsibility. Evidatix provides the database audit evidence those frameworks ask for and that auditors test.
We already have a SIEM. Why do we need this?
Keep your SIEM for threat detection. Evidatix answers a different question: proving database activity to an auditor, with reconciled counts, coverage proof and verified exports.
Which databases do you support?
All leading database platforms. Ask us for the current supported list for your estate.
Where is our data stored?
In India. SaaS runs in an India region; on-prem keeps everything in your own data centre.
Will auditing slow down our databases?
Native auditing adds some load, mainly with full DML auditing. We size it during the pilot so you see the real impact on your own systems.
How long does it take to get started?
A pilot connects one or two databases within about 10 working days, depending on your team's availability to enable native audit.