Singapore · MAS

MAS TRM for SaaS vendors: the vendor questionnaire translated

MAS Technology Risk Management and Outsourcing Guidelines bind Singapore FIs, not SaaS vendors directly — but every FI pushes those expectations down the contract. Here is what to expect, what evidence to bring, and what the proposed 2026 TPRM Guidelines change.

2021
TRM Guidelines in force
Annex 5
SaaS = cloud outsourcing
2026
TPRM consultation
60-70%
SOC 2 covers questionnaire

LowerPlane serves startups in the United States, Singapore, India and worldwide.

What SaaS vendors feel from MAS

MAS doesn't contract with the vendor — the FI does. Here are the three fault lines where that shows up.

📑

Audit-rights clauses in every contract

MAS Outsourcing

FIs demand that the vendor, its auditors and MAS can audit the service — contractually, with specific procedures.

⚠️ Legal review every renewal
⏱️

Incident-notification SLAs tighter than SOC 2

24–72 hr typical

Banks push for 24–72 hour notification clauses on security incidents — more aggressive than public SOC 2 report commitments.

⚠️ Requires a 24/7 pager rotation
🌐

Named-subprocessor disclosure

All geographies

FIs want to know every subprocessor by name and the region it operates in. Changes require advance notice; new regions trigger re-review.

⚠️ Vendor-register discipline every quarter

Which MAS clauses actually get cited

📜

TRM s3.4

Assess third-party technology risk before contracting and on an ongoing basis.

🔐

TRM s5.3

Assess the vendor's secure software development and QA.

☁️

Outsourcing Annex 5

SaaS treated as cloud outsourcing — full outsourcing framework applies.

🔎

Cloud advisory

Accepts reputable independent audit reports (SOC 2 Type 2 / ISO 27001).

The questionnaire → control map

A good SOC 2 Type 2 report answers roughly 60–70% of a MAS-driven FI vendor questionnaire out of the box. An ISO 27001 certificate plus the Statement of Applicability covers a similar share. The non-overlapping items are usually:

📋

Audit-rights clauses

Explicit audit-rights clauses in the master agreement.

⚡

Incident-notification SLAs

Faster than SOC 2 reports commit to — usually 24–72 hours.

🏷️

Named subcontractor disclosure

Every sub-processor named, with geographic location.

🚪

Exit and transition plans

Defined exit assistance period on termination.

🗺️

Data residency

Singapore / APAC data boundary commitments.

🔄

Continuous monitoring

Direction of travel for the proposed 2026 TPRM Guidelines.

📅

The proposed 2026 TPRM Guidelines

In 2026 MAS consulted on Guidelines on Third-Party Risk Management that would supersede the Outsourcing Guidelines and extend them to all third-party arrangements, not only outsourcing. The direction of travel is more rigorous categorisation of third parties by risk, documented exit plans, and continuous monitoring. The Guidelines are proposed, not final. Reconfirm the current status at mas.gov.sg before relying on it in contracts.

Frequently asked questions

Does MAS regulate SaaS vendors directly?

No. MAS regulates financial institutions. The MAS TRM Guidelines and Outsourcing Guidelines bind FIs to assess, monitor and contract for technology risk with their service providers — including SaaS vendors — so vendors feel MAS indirectly through the FI's procurement and vendor-management process.

Is SOC 2 accepted by Singapore banks?

Often, yes. The MAS cloud advisory recognises reputable independent audit reports (SOC 2 Type 2 and ISO 27001 certificates are the common ones) as part of a bank's due-diligence package. Each FI makes its own acceptance call based on scope, period and auditor.

What changes with the proposed 2026 TPRM Guidelines?

The proposed Guidelines on Third-Party Risk Management, under consultation in 2026, would supersede the Outsourcing Guidelines and extend them to all third-party service arrangements (not only outsourcing). Status: proposed, not final. Reconfirm the current status at mas.gov.sg before relying on it.

What incident-notification SLA do Singapore FIs usually demand?

24 to 72 hours is typical in bank vendor contracts for security incidents affecting the FI's data or service. Material incidents often carry a 24-hour clock; less severe events may stretch to 72. This is tighter than public SOC 2 reports commit to, so expect to override the SLA in the master agreement.

Do I need Singapore or APAC data residency to sell to MAS-regulated buyers?

Not by default. MAS does not mandate data residency, but individual FIs sometimes contract SG or APAC data boundaries into vendor terms, especially for primary production data. Clarify data-location commitments early in sales — retrofitting residency after signing is expensive.

Will my SOC 2 report scope be accepted?

Depends on the scope. The FI's due-diligence team maps your SOC 2 scope to the services they are buying. A report that covers the specific product and infrastructure sold is accepted; a report that excludes the sold service, or is dated more than 12 months ago, usually triggers follow-up questions.

How do I prepare for a MAS-driven vendor questionnaire?

Three artefacts answer most of it: a current SOC 2 Type 2 report (or ISO 27001 certificate + SoA) covering the service sold; a subprocessor register listing every vendor and its geography; and a pre-signed MSA addendum carrying audit-rights, incident-notification SLA, and exit-assistance clauses. Publish on your trust centre so FI procurement finds them without a sales call.

Selling SaaS to a Singapore bank?

LowerPlane runs SOC 2 + ISO 27001 together with the controls MAS-driven questionnaires expect.

60-70%
Covered by SOC 2
2021
TRM in force
2026
TPRM proposed
24-72 hr
FI notification SLA