APRA CPS 234
Classify information assets, test their controls and prepare independent assurance and APRA notifications.
MAS technology risk management guidelines and applicable notices
Map supervisory guidance and entity-specific notices to recovery, security and reporting work.
Singapore financial institutions within the scope of applicable MAS guidance and notices. Binding obligations depend on entity type and governing instruments.
A technology risk register, tested controls and reconciliation to the notices applicable to the licensed entity.
Use the relevant notice for your licence. An incident requirement published for banks should not be assumed to apply in the same way across the regulated financial sector.
Monitor progress against the target, failed control tests and gaps that leave a critical service exposed.
Fill this in with your sponsor and send it to the people who own the work.
Singapore MAS technology risk 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 Map regulated entities and applicable notices · Local compliance + technology risk [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. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
A payments business maps outages at its authentication gateway to its licence and notice requirements. It tests whether the provider can supply incident facts early enough for the business to decide which authority notices to send.
Check the PDPC notification trigger and clock separately for a personal data breach.
Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Map regulated entities and applicable notices | Local compliance + technology risk | Before assigning controls | Set a start date | Applicability matrix; Critical-function inventory | Open |
| Convert guidance into control work | Technology risk + engineering | Ongoing | Set a start date | Control matrix; Monitoring plan; Test reports | Open |
| Set recovery targets and run a disruption exercise | Continuity lead + service owners | Before relying on recovery arrangements | Set a start date | Continuity plan; Exercise report; Recovery evidence | Open |
| Route incidents under the applicable notice | Incident lead + regulatory owner | On a reportable event | Set a start date | Incident classification; Reporting templates; 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.
List each licence, applicable notice, critical system and associated obligation. Identify board oversight and accountable technology leadership.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
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.
Map delivery, third-party arrangements, access, testing and resilience practices. Track specific obligations with evidence and periodic review.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
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.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Document dependencies and targets. Test a real recovery, record achieved service levels and assign any gaps.
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.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Identify the event classification and clock from the relevant notice. Record time of discovery and send the required details through the correct channel.
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.
Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.
Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.
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.