MAS TRM IT Requirements for Singapore Fund Managers
Home / MAS TRM IT Requirements for Singapore Fund Managers
By GlobalITN
For a Singapore fund manager, MAS technology risk obligations depend on the firm’s regulatory status and the notices and guidelines that apply to it. Start by confirming that scope, then map technology risks to practical controls, owners and evidence; a generic IT checklist cannot establish compliance by itself.
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.
Confirm which MAS instruments apply
“MAS TRM requirements” can refer to more than one instrument. The MAS Technology Risk Management Guidelines describe principles and good practices for managing technology risk. MAS also issues Notices on Technology Risk Management and Cyber Hygiene for specified categories of financial institution.
A capital markets services licence holder, for example, should check the applicable capital markets notices and the scope of its own licence rather than assume that requirements for a bank apply to it.
MAS’s Cyber Security page lists the notices by financial institution category. The operational resilience page brings technology and cyber risk together with operational risk, third-party risk and business continuity. MAS has also consulted on possible changes to technology-risk notices, so a compliance owner should check for final updates before relying on an older register.
Write down the firm’s legal and regulatory category, relevant licence conditions, applicable notices and guidelines, and the person responsible for confirming the mapping. If the firm has a related entity, outsourced function or overseas operation, record whether it falls within the same scope or needs a separate assessment.
Translate the requirements into operating controls
Fund managers often use a compact technology estate: cloud productivity tools, identity services, endpoints, portfolio or fund platforms, communications, file storage, network security and backup. The useful question is not simply whether each tool is installed. It is whether the firm understands its dependencies, controls access, responds to change and can show that the arrangements work.
Begin with an inventory of systems, information, service owners and external providers. Identify which systems could materially disrupt operations or affect customer information if they failed. Then consider how the firm would detect an incident, limit its effect, communicate internally, restore services and retain evidence.
MAS’s technology risk guidance and the notice applicable to the firm should be used to validate the control design.
Practical control map
| Control area | Buyer’s practical question | Evidence to maintain |
|---|---|---|
| Governance | Who owns technology risk and approves material changes? | Roles, policies, risk decisions, meeting records and action tracking. |
| Assets and dependencies | Do we know which systems, data and providers support key activities? | Asset and service inventory, system owners, data flows and dependency records. |
| Identity and access | Are access rights approved, reviewed and removed when no longer needed? | Joiner, mover and leaver records, privileged-access controls and review evidence. |
| Security operations | How are vulnerabilities, patches, alerts and incidents managed? | Patch status, security alerts, incident records, escalation and closure notes. |
| Change management | Can the firm trace a material technology change from request to approval and test? | Change records, risk review, test results, approvals and rollback plans where relevant. |
| Resilience | Can the firm recover systems and business data, and has it tested the process? | Backup scope, restoration results, recovery procedures, test outcomes and follow-up actions. |
| Third parties | Does the firm know what providers do, what they can access and how they are overseen? | Due-diligence records, service terms, access arrangements, reviews and exit considerations. |
Set a proportionate evidence routine
Evidence should be created as part of normal work, not assembled only when a questionnaire arrives. A monthly or quarterly review can check overdue patches, privileged accounts, backup outcomes, open incidents, changes, provider issues and actions assigned to named owners. The frequency should be set by the firm’s risk assessment and applicable requirements.
Keep records understandable to someone who did not perform the task. A screenshot without a date, system name or explanation may be hard to interpret later. For a control that relies on a third party, record what the provider performs, what the firm checks and what remains the firm’s responsibility.
Do not assume that a supplier’s general security statement proves that a specific control operated for your environment.
For incidents and changes, maintain a clear timeline: what happened, how it was identified, who was informed, which systems or information were affected, what decisions were made, and what was done to prevent recurrence. This helps management assess whether a control is effective and whether a larger risk response is required.
Review the model when the business changes
Fund launches, new service providers, acquisitions, remote-working changes, new investment platforms and AI-enabled tools can change the technology risk profile. Revisit the inventory, access model, data flows, backup arrangements and provider due diligence when such changes occur.
If technology supports an important business service, include the service owner in the review rather than leaving the analysis solely to IT.
A useful review ends with decisions: which gaps need correction, who owns each action, what evidence will show completion, and when management will review remaining risk. Avoid labelling a control “complete” because a policy exists; test whether staff follow it and whether the records support that conclusion.
Related guidance and services
- MAS TRM IT Requirements Singapore
- MAS TRM Compliance Assessment Singapore
- IT Support for Fund Managers & Asset Managers
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 every Singapore fund manager have the same MAS TRM requirements?
No. Applicability depends on the firm’s regulated category, licence and relevant MAS instruments. Confirm the current scope with the firm’s compliance or legal adviser.
Are the MAS Technology Risk Management Guidelines a certification standard?
No. They provide risk-management guidance. They do not certify a firm or replace applicable MAS notices, licence conditions or other obligations.
What IT evidence should a fund manager keep?
Useful records can include system and provider inventories, access reviews, patch status, change and incident records, backup and recovery results, and management decisions. The precise evidence set should follow the firm’s risk assessment and applicable requirements.
Does outsourcing IT transfer regulatory responsibility to the provider?
Outsourcing can change who performs work, but the firm should continue to oversee the arrangement and understand its risks and responsibilities.
