[INDIA] RBI, SEBI and IRDAI · Source-code escrow and continuity obligations for critical applications[EU DORA] ICT third-party risk testing required · In force Jan 2025[PRA] SS2/21 UK · Vendor recovery evidence required[MAS] Singapore TRM · Independent vendor recoverability expected[APRA] CPS 230 Australia · Third-party continuity obligations in force[FFIEC] United States · Source-code access and software escrow addressed in third-party contracts[ENTERPRISE] Mission-critical software procurement increasingly requires continuity evidence before contract
[INDIA] RBI, SEBI and IRDAI · Source-code escrow and continuity obligations for critical applications[EU DORA] ICT third-party risk testing required · In force Jan 2025[PRA] SS2/21 UK · Vendor recovery evidence required[MAS] Singapore TRM · Independent vendor recoverability expected[APRA] CPS 230 Australia · Third-party continuity obligations in force[FFIEC] United States · Source-code access and software escrow addressed in third-party contracts[ENTERPRISE] Mission-critical software procurement increasingly requires continuity evidence before contract

DATA ESCROW

When a vendor holds your operational data, their failure is your data loss

Software can be rebuilt from an escrow deposit. Data cannot be recreated from code. If a vendor holds your transactions, customer records, risk models, or operational dataset, Castler provides independent custody and a verified export path.

Escrow scope
DatasetLayer 1
SchemaLayer 2
IntegrityLayer 3
Load testVerified
Custody mapped to signed evidence

WHAT IT IS

Data escrow, precisely defined.

Data escrow is an independent custody arrangement in which a vendor deposits operational data, or the pipelines and schemas required to produce a full export, with a neutral third party.

Data escrow is different from backup. Backup protects against corruption or infrastructure failure. Escrow protects the beneficiary against vendor failure, including scenarios where the vendor cannot or will not cooperate with extraction.

Verification confirms that every export is complete, structurally valid, readable, and loadable into a clean environment.

THE PROBLEM

Three data continuity failures that software escrow alone cannot prevent.

01

The software runs but the data is gone

A rebuilt application cannot resume operations if transaction history, customer records, and risk data remain on inaccessible vendor systems.

02

The data exists but cannot be loaded

Proprietary formats, missing keys, unsupported database versions, or undocumented schemas can make a delivered export unusable.

03

The data is stale by months

Quarterly or annual exports can create an unacceptable operational gap for institutions processing continuous transactions.

THE CASTLER APPROACH

Continuous data custody with integrity verification on every deposit.

Castler validates the structure and usability of each data deposit, records the evidence, and aligns deposit frequency to the institution's recovery tolerance.

What Castler custodies

Open-format database exports

Schema definitions and version history

Data dictionary

Referential integrity maps

Export pipeline code

Transformation and ETL logic

Record counts and checksums

Partition and operational metadata

Verification pipeline

Agents validate record counts, referential integrity, schema alignment, and checksums. A sample load runs in a clean database environment on every deposit, with full load tests on an agreed schedule.

Signed output

Signed integrity evidence for each deposit, with structural validation, load-test result, timestamp, version, and chain of custody. Deposits can run daily, weekly, or through incremental streaming custody.

REGULATORY MANDATE

Data escrow requirements across active mandates.

EU DORA

Critical functions require data availability and recoverability controls for third-party ICT services.

Evidence map

EU NIS2

Essential and important entities must manage data integrity and availability risks involving third parties.

Evidence map

SEBI CSCRF

Market institutions must protect data availability and recovery for critical third-party systems.

Evidence map

ISO 22301

Business continuity systems must identify and protect critical information assets held by third parties.

Evidence map
See all 17 mandates

FREQUENTLY ASKED

Questions about this escrow type

What data formats are accepted?

Supported open formats include PostgreSQL, MySQL, and MSSQL dumps, Parquet, Avro, ORC, CSV with schema, JSON with schema, and XML. Proprietary formats require a documented conversion pipeline.

Can Castler handle large datasets?

Yes. Incremental and delta deposits are available when daily full exports are impractical, while maintaining a reconstructable dataset in custody.

Does data escrow replace backup?

No. Backup is an internal operational control. Data escrow is an independent continuity right protecting against vendor failure. Both are required for different risks.

Is escrowed data encrypted?

Yes. Data is encrypted in transit and at rest. Key custody and release controls are defined in the agreement and access is restricted to valid release conditions.

GET STARTED

Find out which vendor-held datasets need independent custody.

A 15-minute briefing. We identify critical vendor-held data outside current escrow scope and map the recovery requirements that apply to your sector.

Book a 15-min briefing
ISO 27001SOC 2 Type IIPCI DSS

No spam · Reply within one business day