Singapore MAS technology risk
Map supervisory guidance and entity-specific notices to recovery, security and reporting work.
Prudential Standard CPS 230 Operational Risk Management
Identify critical operations, define acceptable disruption and test reliance on material service providers.
Entities covered by the Australian prudential operational-risk standard, with application and any specific transitions governed by the applicable determination.
Operational risk controls, continuity tolerances and tests, and a maintained material service-provider program.
A tolerance has to work in a real disruption. Test how business teams meet it when key technology, people or suppliers are unavailable at the same time.
Track critical operations without verified recovery, material provider arrangements with unresolved gaps and reportable disruptions with approaching deadlines.
Fill this in with your sponsor and send it to the people who own the work.
APRA CPS 230 kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Define critical operations and impact tolerances · Board + operational risk lead [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Pick a regulated critical operation and trace the people, premises, data, technology and providers needed for minimum service. 2. Ask its owner to show the recovery tolerance, actual restoration results and critical provider obligations. Identify what is based on an untested assumption. 3. Schedule a recovery exercise and agree how the response team decides whether and when to notify APRA.
An Australian bank tests a payments outage that also affects its usual support provider. The continuity team measures actual downtime and workarounds against documented tolerances, then sends missed thresholds to the owner of the remediation plan.
Assign security obligations and test information asset controls.
Use a management system to structure business continuity work.
Checklist, instructions and 10 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Define critical operations and impact tolerances | Board + operational risk lead | Before continuity planning | Set a start date | Business impact analysis; Critical-function inventory | Open |
| Build and test recovery options | Continuity lead + operations | Before relying on the arrangements and on the required schedule | Set a start date | Continuity plan; Exercise report; Corrective-action register | Open |
| Manage material provider arrangements | Supplier risk + procurement | Before contracting and on the applicable review cycle | Set a start date | Vendor review; Contract gap analysis; Exit plans | Open |
| Report incidents and material disruptions | Incident lead + compliance | When applicable thresholds are met | Set a start date | Incident classification; Notification record | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Map operations, customers and dependencies. Set tolerances and record the assumptions, approval and measurement methods.
Service and entity inventory, dependency maps, board-approved risk settings and regulatory scope.
A payments operation has approved time, data-loss and minimum-service tolerances and a dependency map checked by Operations.
Raise an operation classified as critical with no owner or tolerance decision.
Fictional details. Use the same fields with evidence from your work.
Each target links to an observable impact and to the actual resources needed for recovery.
Give the approved priorities to the people planning recovery and testing suppliers.
Fictional details. Use the same fields with evidence from your work.
Each item has one accountable owner. The source and as-of date let a reviewer trace it back.
Share the reviewed inventory with the people building the control, privacy or testing scope.
Prepare continuity plans. Test a severe but plausible scenario, measure actual performance and have owners address weaknesses.
Approved tolerances, continuity plans, exercises and actual failover and restore evidence.
An exercise records start time, first restored service, recovered records, minimum service output and what needs correction.
Escalate a test that breaches tolerance or depends on an unverified provider promise.
Fictional details. Use the same fields with evidence from your work.
Someone covering the primary owner can activate the plan and verify recovery with the written instructions.
Give controlled copies to responders and suppliers and update the record after each exercise.
Fictional details. Use the same fields with evidence from your work.
An absent participant can see what was tested, what happened and why an action was assigned.
Send approved findings to action owners and file the record for governance or assessment.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Identify and maintain the required register, check contract and monitoring requirements, and plan how to leave or replace a provider.
Contract register, dependency maps, service descriptions, provider evidence and renewal dates.
The provider record links a critical operation to the contract, continuity terms, current due diligence and tested or scheduled exit work.
Raise material services without workable continuity or cooperation terms before signing or renewal.
Fictional details. Use the same fields with evidence from your work.
Each provider and contract record links to an actual function and all required identifiers are present.
Use the verified register in supplier reviews and put required submissions in the authority’s prescribed format.
Fictional details. Use the same fields with evidence from your work.
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
Fictional details. Use the same fields with evidence from your work.
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
Evaluate incident materiality and disruption outside tolerance as separate triggers. Retain awareness, duration, impact and the submitted notices.
Alert timeline, approved tolerances, impact measurements, reporting criteria and APRA contact procedure.
The record shows when the team identified the trigger, how it calculated the deadline and when the notice was sent.
Escalate a possible reportable event promptly and assign someone to track the regulatory clock during recovery.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.