MAS Outsourcing Due Diligence: IT Provider Evidence Checklist

Home / MAS Outsourcing Due Diligence: IT Provider Evidence Checklist
By GlobalITN

Before appointing an IT provider, a Singapore financial institution should understand what the provider will do, what information and systems it can access, and how the arrangement will be overseen. The right evidence depends on the service’s risk and the financial institution’s regulatory category; a supplier questionnaire is only one part of due diligence.

Get a quote / talk to an engineer

GlobalITN has supported Singapore businesses since 2013, with our own engineers across Singapore, Hong Kong, Australia and Vietnam.

Start with the applicable outsourcing regime

MAS publishes different outsourcing instruments for different financial institution categories. The MAS Third-Party Risk Management page points non-bank financial institutions to the Guidelines on Outsourcing (Financial Institutions other than Banks), and banks and merchant banks to their relevant instruments.

The non-bank guidelines took effect on 11 December 2024. Do not assume that the same document applies to every firm or every service.

First classify the provider relationship. Decide whether the proposed work is an outsourcing arrangement, another third-party service, or both. Record the service, business owner, data handled, system access, location, subcontractors and likely effect if the provider fails. Your compliance or legal owner should confirm the applicable instruments and whether any additional requirements apply.

MAS’s guidelines frame outsourcing as a risk-management responsibility for the financial institution. A contract, provider certificate or security questionnaire does not eliminate the need for the firm to assess and oversee the arrangement. The operational resilience guidance also places third-party risk alongside technology, cyber and business continuity considerations.

Ask for evidence that matches the service

Due diligence should begin with the service description rather than a long list of generic questions. A provider administering user accounts may need to show how access is authorised and removed. A provider with remote access to financial systems may require closer scrutiny of privileged access, monitoring, incident handling and subcontractors.

A provider storing or processing data raises questions about location, confidentiality, retention and secure return or deletion.

Request evidence in a form the business can review. A policy may explain the provider’s intended process; operating records can help show how the process works in practice. Ask what the evidence covers, which period it represents, which locations and entities are included, and whether exceptions were found. Where evidence cannot be shared, ask for an alternative method of review and record the limitation.

IT provider evidence checklist

Evidence area Examples to request Questions for the provider
Service and responsibility Service description, responsibility matrix, service boundaries and named escalation roles. Which tasks are included, excluded or dependent on the customer?
Governance and financial continuity Ownership, governance contacts, relevant business continuity information and change notification process. How will material operational changes be communicated and managed?
Security and access Access-control process, privileged account handling, authentication approach and access review records. Who can access our environment, how is access approved, and how is it removed?
Data handling Data-flow description, storage and processing locations, retention terms and deletion or return process. What information is handled, where, by whom, and for how long?
Incident management Incident process, escalation route, customer notification terms and example of an appropriately redacted incident record. How are suspected incidents reported, investigated and closed?
Resilience and recovery Relevant continuity and recovery procedures, test summaries and corrective actions. Which parts of the service have been tested, and what remains dependent on us?
Subcontracting Subcontractor list or categories, approval process and flow-down of relevant obligations. Can subcontractors access our systems or data, and how are they overseen?
Audit, assurance and exit Assurance reports where available, audit arrangements, service records, data return and transition terms. How can the firm assess the service and exit without losing necessary records or access?

Score risks and record decisions

Use a consistent assessment that considers both impact and likelihood. A small provider with limited system access may present a different risk from a provider with privileged access to a critical platform. Consider confidentiality, integrity, availability, dependency concentration, location, regulatory access, and the difficulty of replacing the service.

For each material risk, record the evidence reviewed, gaps, compensating controls, owner and decision. If a provider cannot supply a particular report, distinguish between “not provided” and “control does not exist”. Agree what alternative evidence or contractual protection will address the uncertainty. Escalate risks that exceed the firm’s tolerance rather than letting a procurement deadline decide them by default.

Due diligence is not a one-off onboarding form. Set a review trigger based on the service’s risk and reassess after material changes such as a new subcontractor, system migration, security incident, change in data location or shift in service scope. Keep an up-to-date provider inventory so management can see dependencies and overlapping suppliers.

Make the contract and operating model usable

The agreement should describe the service clearly enough that operations can tell whether it is being delivered. Address access, confidentiality, data handling, incident notification, service reporting, change control, subcontracting, records, audit or assurance, continuity and exit arrangements as relevant to the risk.

The contract should align with the actual way the provider works; boilerplate that does not match the delivery model can create blind spots.

After onboarding, name a service owner and define how issues, changes and performance will be reviewed. Decide which evidence will be retained by the provider and which must be held by the financial institution. A useful control file lets a reviewer trace the decision from the service description to due diligence, approval, contract terms and ongoing monitoring.

Related guidance and services

How GlobalITN helps

GlobalITN has supported Singapore businesses since 2013, supplying and renewing Cisco Meraki and Fortinet licences and hardware, with our own engineers across Singapore, Hong Kong, Australia and Vietnam for survey, deployment and on-the-ground support.

Get a quote / talk to an engineer

Frequently asked questions

Does MAS require the same checklist for every IT provider?

No. The institution should apply the relevant MAS instruments and tailor due diligence to the service, data, access, dependency and risk.

Is a supplier security certificate enough?

Not by itself. It may be useful evidence, but the firm should understand its scope, period, exclusions and relevance to the service being purchased.

Should due diligence include subcontractors?

Where subcontractors support the service or can access systems or data, the firm should understand their role and how relevant risks are managed.

How often should an IT provider be reviewed?

Set a risk-based review cycle and reassess after material service, security, ownership or subcontracting changes.