SINGAPORE · MAS TECHNOLOGY RISK MANAGEMENT GUIDELINES
The MAS TRM Guidelines set expectations for technology risk governance, third-party and vendor management, secure software delivery, and IT business continuity for financial institutions in Singapore. This guide explains the requirement, scope, timeline and evidence mapping for software escrow and Software Recoverability.
REGULATORY EVIDENCE MAP
MAS TRM
PERIMETER
Singapore
REQUIREMENT
Sound governance of technology and third-party / vendor risk
CASTLER EVIDENCE
Vendor-developed software is independently rebuilt and verified — beyond a code-escrow deposit
OUTPUT
Signed Proof of Recovery
MAS Technology Risk Management Guidelines — third-party and continuity controls
In force as supervisory guidanceWho it applies to
Institutions are expected to align controls with the current Guidelines and address material gaps through their technology-risk management programme.
What the regulation requires
The Castler artefact that evidences it
Sound governance of technology and third-party / vendor risk
Vendor-developed software is independently rebuilt and verified — beyond a code-escrow deposit
Assurance over outsourced and vendor-developed software
Recovery capability is demonstrated and sealed, not just documented
IT business continuity and recovery capability
Proof of Recovery strengthens IT business continuity assurance
Controls across the software delivery lifecycle
Continuous re-verification keeps vendor-risk assurance current
THE GLOBAL REGULATORY MANDATE
Across financial regulation, cyber-resilience rules and global assurance standards, the direction is converging: critical third-party software must remain current, testable and recoverable when its provider fails.
17
MANDATES
9
JURISDICTIONS
1 · WHAT THE REGULATION IS
The Monetary Authority of Singapore Technology Risk Management Guidelines set expectations for financial institutions’ governance, software delivery, third-party technology and IT continuity.
The MAS TRM Guidelines set expectations for technology risk governance, third-party and vendor management, secure software delivery, and IT business continuity for financial institutions in Singapore. For a CIO, CISO or compliance officer, the practical issue is whether a critical third-party application can remain available when the provider fails, exits, is acquired or can no longer support the product.
Software escrow addresses custody: who holds the source code, build materials and documentation. Software Recoverability addresses the next question: whether those materials have been independently rebuilt, deployed and tested. The distinction matters because an agreement and a deposit do not prove that recovery can be completed within the institution’s operational tolerance.
Castler therefore treats the requirement as part of vendor onboarding. The agreement and first deposit are established when the relationship begins, every release is captured, and the verification evidence is renewed before an auditor, insurer or supervisor asks for it.
2 · EXACT REQUIREMENT
In summary
Financial institutions should maintain effective controls over third-party technology services and ensure that recovery and continuity capabilities are documented, tested and capable of supporting critical services during disruption.
Reference: Monetary Authority of Singapore — Technology Risk Management Guidelines. For legal interpretation and exact operative wording, use the current official text and advice applicable to your supervisory perimeter.
In practical terms, compliance requires more than a clause in the vendor contract. The institution must identify which applications are critical, establish custody or source-code access, ensure the deposited materials remain current, document release conditions and maintain evidence that continuity or exit can be executed.
Where the framework requires tested recovery, resilience or credible exit, a stored deposit is only the starting control. Independent build evidence, deployment instructions, architecture replication and a signed engineer review show that the recovery path has been exercised rather than assumed.
Banks and merchant banks
Insurers
Capital-markets intermediaries
Payment-service providers
Other financial institutions supervised by MAS
The accountable group normally includes technology, information security, outsourcing, procurement, compliance, business continuity and the business owner of the supported service. Scope should be based on criticality, not only contract value.
In force as supervisory guidance
Institutions are expected to align controls with the current Guidelines and address material gaps through their technology-risk management programme.
Institutions should work backwards from the operative date. Vendor identification, agreement execution, repository integration, initial deposit, reconciliation and first verification all require lead time. Onboarding-first implementation avoids a deadline-driven retrofit.
5 · CONSEQUENCES
Gaps may lead to supervisory observations, remediation requirements, increased technology-risk scrutiny and questions about whether the institution can maintain critical services during provider failure.
The operational consequence can be more severe than the supervisory consequence. If a critical provider fails and the deposited software cannot be built or deployed, the institution may breach customer commitments, impact tolerances, market obligations and board-approved continuity objectives while the technical team reconstructs undocumented knowledge under incident conditions.
A current custody record and signed Proof of Recovery reduce that uncertainty. They do not replace legal analysis, incident planning or the institution’s own controls; they create tested technical evidence that those controls rely on.
6 · CASTLER EVIDENCE MAPPING
The mapping is specific: each obligation is paired with the Castler artefact or operating control that provides relevant evidence. It is not a claim that software alone guarantees compliance.
| Regulatory requirement | Castler evidence |
|---|---|
| Sound governance of technology and third-party / vendor risk | Vendor-developed software is independently rebuilt and verified — beyond a code-escrow deposit |
| Assurance over outsourced and vendor-developed software | Recovery capability is demonstrated and sealed, not just documented |
| IT business continuity and recovery capability | Proof of Recovery strengthens IT business continuity assurance |
| Controls across the software delivery lifecycle | Continuous re-verification keeps vendor-risk assurance current |
Cloud Custody
Establish the software escrow agreement, current deposit, release history and audit trail required as the custody foundation.
Explore custody →Software Recoverability
Add independent rebuild, deployment, replication, confidence scoring and an engineer-sealed Proof of Recovery.
Explore Proof of Recovery →7 · FREQUENTLY ASKED QUESTIONS
An agreement can satisfy the contractual custody element, but MAS TRM also expects the institution to manage continuity, third-party risk or recovery evidence. The exact answer depends on the clause and supervisory perimeter.
The deposit should track the production release. Automated repository capture, version history and release identifiers make it possible to show that updates and fixes are included rather than relying on the original filing.
The vendor participates in onboarding, deposit setup and structured reconciliation where documentation is missing. Verification is then designed to run independently so the vendor does not need to be present every time.
Present the executed escrow arrangement, deposit and release history, build report, deployment runbook, replication report, SBOM, confidence score, exception record and signed Proof of Recovery for the release in scope.
Yes. Cloud Custody establishes the current deposit and agreement. The same record can be upgraded to Standard or Premium Software Recoverability without creating a new custody foundation.
Re-test when the vendor releases a material version and according to the institution’s criticality, regulatory and board-approved assurance cycle. Per-release verification avoids stale annual evidence.
8 · RELATED REGULATIONS
European Union
EU DORA
DORA requires financial entities to keep ICT third-party risk under control across the full lifecycle of a contract — including a documented exit strategy and assurance that a critical or important function can continue if a provider fails (Article 28).
Read the mappingIndia
RBI §12(f)
RBI's directions on outsourcing of IT services require regulated entities to maintain robust exit strategies and business-continuity arrangements so critical operations survive a service provider's exit or failure.
Read the mappingThis guide is for regulatory orientation and does not constitute legal advice. Verify obligations against current official texts and professional advice for your entity.
MAS TRM
Bring your MAS TRM perimeter. We’ll map the critical systems, current custody and Proof of Recovery evidence required for a defensible procedure.
Book a 15-min briefing