
sg-mas-trm
Singapore MAS TRM reference plugin with scope, evidence checklist, and SCF-backed gap assessment.
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install sg-mas-trm@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
Singapore MAS TRM Expert
Reference-depth expertise for the Monetary Authority of Singapore (MAS)
Technology Risk Management Guidelines, represented in SCF as
apac-sgp-mas-trm-2021. This plugin bundles the SCF crosswalk (214 SCF controls
to 280 framework controls) with MAS TRM-specific assessment context.
Framework Identity
- SCF framework ID:
apac-sgp-mas-trm-2021 - Region: APAC
- Country: SG
- Regulator: Monetary Authority of Singapore (MAS)
- Common shorthand: MAS TRM / Singapore TRM
- Current assessment baseline: MAS Technology Risk Management Guidelines, revised January 18, 2021
Framework In Plain Language
MAS TRM is Singapore's supervisory guidance for managing technology and cyber risk in financial institutions. It focuses on board and senior management oversight, technology risk governance, system resilience, cyber security, software development, third-party and cloud risk, incident response, and data protection controls. Treat it as a financial-services technology risk framework: the assessor needs to see accountable governance, repeatable operational controls, and evidence that critical systems are resilient and monitored.
Territorial Scope And Applicability
MAS TRM applies to financial institutions regulated by MAS, including banks, insurers, capital markets intermediaries, payment service providers, and other regulated entities that depend on technology to deliver financial services. Scope analysis should identify Singapore-regulated entities, critical systems, outsourced service providers, cloud-hosted workloads, customer-facing digital channels, and regional shared-service platforms supporting Singapore operations. Do not treat MAS TRM as a generic ISO 27001 checklist; the Singapore regulatory perimeter and criticality of financial services matter.
Mandatory Artifacts
Evidence usually centers on board-approved technology risk policies, technology risk registers, critical system inventories, risk assessments, cyber resilience plans, secure SDLC records, vulnerability and penetration test results, privileged access reviews, incident response procedures, outsourcing due diligence, cloud risk assessments, business continuity and disaster recovery test records, and independent assurance reports. MAS TRM is guidance rather than a standalone certification package, so map artifacts to supervisory expectations instead of inventing a formal certificate deliverable.
Cadence And Timelines
There is no annual MAS TRM certificate cycle. Assess recurring operating evidence on a risk-based cadence, with stronger scrutiny for critical systems: access reviews, vulnerability management, penetration testing, resilience tests, third-party reviews, and incident exercises should run often enough to support board and senior management oversight. MAS-regulated entities should also align incident escalation and notification evidence with applicable MAS notices, outsourcing requirements, and internal materiality thresholds.
Regulator And Enforcement
The Monetary Authority of Singapore supervises regulated financial institutions and can use inspections, supervisory findings, directions, penalties, and other regulatory measures when technology risk management is weak. In assessment output, separate MAS TRM control evidence from legal advice about notices, licensing, or penalty exposure.
Interaction With Other Frameworks
MAS TRM commonly overlaps with ISO 27001/27002, SOC 2 security and availability criteria, NIST CSF, PCI DSS for payment environments, Singapore PDPA for personal data, and outsourcing/cloud risk requirements. Use the SCF crosswalk for control mechanics, but keep MAS TRM reporting focused on financial institution governance, critical system resilience, cyber operations, secure development, outsourcing, and technology incident readiness.
Common Misinterpretations
- "MAS TRM only applies to Singapore-hosted systems." Offshore platforms, shared services, and outsourced providers can be in scope when they support Singapore-regulated financial services.
- "ISO 27001 certification is enough." ISO 27001 helps, but MAS TRM expects Singapore financial-sector governance, critical-system resilience, outsourcing, and supervisory evidence.
- "Cloud is out of scope if the provider is certified." MAS-regulated institutions still need due diligence, risk assessment, monitoring, exit planning, and accountability for outsourced or cloud services.
- "TRM is only an IT operations checklist." Board and senior management accountability, risk acceptance, and independent assurance are central.
Command Routing
/sg-mas-trm:scope- determine applicability/sg-mas-trm:assess- run a gap assessment/sg-mas-trm:evidence-checklist- enumerate evidence requirements
All three delegate to /grc-engineer:gap-assessment with SCF framework ID
apac-sgp-mas-trm-2021 for the control-by-control mechanics, and wrap the
results in MAS TRM-specific terminology.
Levelling Up To Full
Full-depth plugins add framework-specific workflow commands tied to the audit ritual. Candidates for this framework:
/sg-mas-trm:critical-system-register- build or review the inventory of critical systems, owners, dependencies, RTO/RPO, and resilience evidence./sg-mas-trm:outsourcing-cloud-review- assess cloud and outsourced service providers against due diligence, monitoring, exit, and concentration-risk expectations./sg-mas-trm:cyber-resilience-check- review monitoring, vulnerability, penetration testing, incident response, and recovery exercise evidence./sg-mas-trm:board-pack- summarize technology risk posture and open issues for board or senior management oversight.
References
Commands 3
Singapore MAS TRM Assessment
Runs a compliance gap assessment against the Monetary Authority of Singapore
(MAS) Technology Risk Management Guidelines by delegating to
/grc-engineer:gap-assessment with the framework's SCF identifier, then
overlays MAS TRM-specific context and evidence requirements.
Usage
/sg-mas-trm:assess [--scope=<scope>] [--sources=<connector-list>]
Arguments
--scope=<scope>(optional) - narrow the assessment to a MAS TRM workstream such asgovernance,critical-systems,cyber-security,secure-development,outsourcing-cloud,incident-response, orbusiness-continuity.--sources=<connector-list>(optional) - comma-separated connector plugins.
What the assessment produces
- Compliance score - overall MAS TRM readiness percentage, weighted by mapped SCF controls.
- Applicable-requirements summary - which MAS TRM expectations apply to the organization.
- Control-by-control gap - all 280 mapped controls, with pass/fail/inconclusive status from connector findings.
- Evidence gaps - controls where no evidence source is configured.
- Remediation roadmap - prioritized by severity and effort.
Delegation
Under the hood:
/grc-engineer:gap-assessment "apac-sgp-mas-trm-2021" [--sources=<connector-list>]
The SCF crosswalk expands 214 SCF controls into the 280 MAS TRM mapped controls.
Framework-specific notes
- Start with
/sg-mas-trm:scopeto identify whether the entity is MAS-regulated and which technology services support Singapore financial services. - Common assessment scopes are board and senior management governance, critical system resilience, cyber operations, secure SDLC, outsourcing, cloud, and incident response.
- For ISO 27001 or SOC 2 programs, verify that generic security evidence is translated into MAS TRM governance, critical-system, and financial-sector risk language.
- Treat cloud and outsourced technology as in scope when they support regulated financial services; vendor certifications do not replace the institution's accountability.
Singapore MAS TRM Evidence Checklist
Baseline evidence checklist for a Singapore MAS TRM assessment. The SCF crosswalk maps 214 SCF controls to the 280 MAS TRM controls; this command enumerates what evidence tends to be expected for each SCF family in scope.
Usage
/sg-mas-trm:evidence-checklist [--family=<SCF_family_code>]
Arguments
--family=<SCF_family_code>(optional) - restrict to a single SCF family such asIAC,CRY,AST, orBCD. Defaults to all families mapped for this framework.
Output
Markdown checklist grouped by SCF family with:
- SCF control ID to framework-native control ID(s) from the crosswalk.
- Evidence types typically expected.
- Which connector plugins can collect each type automatically.
- Which items require manual upload or narrative.
Framework-specific evidence
Collect MAS TRM evidence around the actual technology risk lifecycle:
- Governance and accountability: board and senior management reporting, technology risk appetite, risk acceptance records, policies, committee minutes, and independent assurance reports.
- Critical system inventory: system criticality ratings, owners, dependencies, data classifications, RTO/RPO targets, architecture diagrams, and resilience requirements.
- Cyber security operations: logging, monitoring, alert triage, threat intelligence, vulnerability management, penetration testing, red-team or exercise reports, and remediation tracking.
- Identity and privileged access: joiner/mover/leaver evidence, MFA, privileged account approvals, periodic access reviews, session logging, and emergency access records.
- Secure development and change: SDLC standards, threat models, code review, dependency scanning, release approvals, segregation of duties, rollback plans, and production change records.
- Outsourcing and cloud: due diligence, risk assessments, contractual controls, concentration-risk analysis, monitoring reports, exit plans, and evidence from material service providers.
- Business continuity and disaster recovery: BCP/DR plans, test results, lessons learned, backup and restore evidence, failover exercises, and recovery gap remediation.
- Incident response: incident procedures, severity criteria, escalation logs, post-incident reports, customer and regulator notification analysis, and corrective-action tracking.
Prefer structured exports from identity, ticketing, cloud, CI/CD, vulnerability management, SIEM, and vendor-risk systems over screenshots. Where evidence is narrative, capture the owner, approval date, scope, affected systems, and link to the underlying operating record.
Singapore MAS TRM Scope
Determines whether and how the Monetary Authority of Singapore (MAS) Technology Risk Management Guidelines apply to the organization. Reference-depth scope is a decision-tree prompt; Full-depth plugins extend this with jurisdiction-aware logic.
Usage
/sg-mas-trm:scope
What this produces
- Applicability verdict: in-scope, out-of-scope, or partially in-scope.
- In-scope entity types: MAS-regulated financial institution, Singapore branch, licensed payment service provider, capital markets intermediary, insurer, bank, outsourced service provider, or shared-service operator.
- In-scope systems: critical systems, customer-facing digital channels, cloud workloads, outsourced technology services, security monitoring, and recovery environments.
- Jurisdiction reach: Singapore-regulated operations and supporting offshore or outsourced technology services.
- Next steps: whether to proceed with
/sg-mas-trm:assessor/sg-mas-trm:evidence-checklist.
Framework-specific scope triggers
Ask the minimum questions needed to classify MAS TRM applicability:
- Is the organization regulated or licensed by MAS?
- Does it operate a Singapore branch, subsidiary, or service supporting a Singapore-regulated financial institution?
- Which systems are critical to financial services, customer access, transaction processing, risk management, or regulatory reporting?
- Are technology services outsourced, cloud-hosted, or delivered through a regional shared-service model?
- Are there customer-facing digital channels, APIs, payment systems, trading systems, or high-availability platforms?
- Does the organization rely on third parties for security monitoring, incident response, disaster recovery, software development, or infrastructure operations?
Return an applicability verdict, in-scope systems, responsible owners, and the follow-up command that should run next. Do not ask users to search the MAS guidelines; translate their answers into practical MAS TRM scoping outcomes.
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/frameworks/sg-mas-trm
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- singapore-pdpav0.1.0
- slack-inspectorv0.1.0
- snowflake-inspectorv0.1.0
- soc2v0.1.0
- splunk-inspectorv0.1.0
- staterampv0.1.0
- teach-mev0.1.0
- tenable-inspectorv0.1.0
- testssl-inspectorv0.1.0
- trust-centerv0.1.0
- us-ccpav0.1.0
- us-exportv0.1.0
- us-finrav0.1.0
- us-hipaa-securityv0.1.0
- us-nerc-cipv0.1.0
- us-soxv0.1.0
- vault-kvv0.1.0
- wiz-inspectorv0.1.0
- academic-research-companionv0.1.0
- au-apra-cps-234v0.1.0
- aws-inspectorv0.1.0
- aws-secrets-inspectorv0.1.0
- azure-inspectorv0.1.0
- ch-fadpv0.1.0