Summary
- MAS Notice No. FSM-N05 obliges a bank to notify the Authority "as soon as possible, but not later than 1 hour, upon the discovery of a relevant incident"; the insurer and finance-company notices print the same sentence, and the banks' predecessor Notice 644 printed it in 2013.
- MAS's own guidance treats discovery as the point at which the firm has ascertained that the incident meets the criteria, so the hour is a deadline on talking rather than on noticing — while the published enforcement record names institutions for recovery failures and carries no comparable named outcome for late notice.
MAS explains its own rule with a subtraction. In the FAQ it updated in February 2024, the supervisor works an example: an incident occurs at T, the firm discovers it at T+1, and the notification is due by T+2. The recovery clock, meanwhile, runs from T, and the system has to be back by T+4 (FAQ on the Notice on Technology Risk Management, February 2024).
Read that example twice and a small asymmetry appears. The recovery deadline is measured from something that happened. The notification deadline is measured from something the firm concluded. One is an event; the other is a judgement.
The sentence itself is plain. MAS Notice No. FSM-N05, issued on 9 May 2024 and effective the next day under section 29(1) of the Financial Services and Markets Act 2022, says at paragraph 7 that "A Bank must notify the Authority as soon as possible, but not later than 1 hour, upon the discovery of a relevant incident." (MAS Notice No. FSM-N05)
This is not a banks-only instinct. The licensed-insurer notice, FSM-N03, prints the same paragraph with "An insurer" where "A Bank" stood, and the finance-company notice, FSM-N09, does the same with "A finance company" (MAS Notice No. FSM-N03; MAS Notice No. FSM-N09). The banks' predecessor carried the identical obligation: Notice 644, issued on 21 June 2013 and cancelled with effect from 10 May 2024, required notification "as soon as possible, but not later than 1 hour, upon the discovery of a relevant incident" (MAS Notice 644). More than a decade of drafting continuity is not an accident of house style.
What counts as a relevant incident is decided by thresholds, and the thresholds assume a firm already knows a great deal. Paragraph 2 defines it as a system malfunction or IT security incident with severe and widespread impact on operations or material impact on service to customers (FSM-N05). Severe and widespread, or material. Whether a given outage clears those adjectives is a determination the firm makes with its own telemetry, on its own timeline, before anyone at the Authority hears a word about it.
The same notice carries two other numbers that behave quite differently. Paragraph 5 caps unscheduled downtime at four hours per critical system in any twelve-month period; paragraph 6 sets a recovery time objective of not more than four hours (FSM-N05). Those clocks do not wait for a judgement. Downtime accrues whether or not anybody has decided it is serious, which is exactly why the supervisor can reconstruct them from logs afterwards — and why they appear in the enforcement record while the notification hour does not.
The interpretive guidance is where the anchor softens. In the same FAQ, the answer on what "upon discovery" means describes a firm notifying promptly after it "has ascertained that the nature and magnitude" of the incident meets the criteria in the Notice (FAQ, February 2024). The operative text says discovery. The gloss says ascertainment. Those are different tests, and the distance between them is precisely a firm's deliberation time. A bank that argues it could not have known the severity at T+0 has, on the gloss's own logic, not yet started the hour — while MAS states elsewhere in the same document that the one-hour duty applies regardless of when the incident occurs (FAQ). Both sentences are the supervisor's. Only one of them can govern a disputed file, and which one governs is settled in a conversation no outsider observes.
Paragraph 8 adds a longer clock from the same anchor: a root cause and impact analysis report within 14 days, or such longer period as the Authority may allow, from discovery (FSM-N05). Its contents are fixed — executive summary, root cause, impact on compliance, operations and customer service, remedial measures (FSM-N09).
The December 2025 circular layers two more artefacts on top: an Initial Incident Report no later than 24 hours from discovery, and a Final Incident Report within 14 days, with filings moving to MAS-Tx from 1 February 2026 (Circular No. MAS/TCRS/2025/08). The circular sets no hour of its own; paragraph 4 defers to "the timeline prescribed in the applicable act(s), regulation(s), notice(s), circular(s) or guideline(s)" (Circular). There is a naming drift worth noticing: the notice calls its 14-day document a root cause and impact analysis report, the circular calls its 14-day document a Final Incident Report. Same interval, two labels, closer to a template change than a conflict of substance.
What the notice does not print is a price. That comes from the statute it hangs on. Section 29(2) of the Financial Services and Markets Act 2022 makes it an offence to fail to comply with a direction issued under subsection (1), or to contravene regulations mentioned in that subsection, punishable "on conviction to a fine not exceeding $1 million and, in the case of a continuing offence, to a further fine of $100,000 for every day or part of a day during which the offence continues after conviction" (Financial Services and Markets Act 2022, section 29). Read closely: the subsection names directions and regulations. It does not name notices. The bridge from "FSM-N05 says one hour" to "S$1 million" is an interpretive step, and the step is taken by practice rather than by the section's own words — taken outright by a Rajah & Tann commentary of 14 May 2024, which states that the maximum penalty for breaches of regulations and notices issued under the Act is S$1 million, with a composition framework keyed to severity (Rajah & Tann Asia, 14 May 2024).
Composition is the practical route. The Financial Services and Markets (Composition of Offences) Regulations 2023, in force from 14 July 2023, make any fine-only offence under the Act compoundable in accordance with section 177 (Composition of Offences Regulations 2023). Section 177(1) then caps a composition at not more than one half of the maximum fine prescribed for the offence, on the reading of a reproduced Part 11 rather than the primary page (Financial Services and Markets Act 2022, Part 11, reproduced). Half of S$1 million is S$500,000. That is arithmetic on a ceiling, not a tariff, and MAS describes the instrument the same way: its July 2025 monograph calls a composition essentially a financial penalty, fixed with reference to the prescribed fine and offered in lieu of prosecution where misconduct is of low or moderate seriousness (MAS Enforcement Monograph, July 2025).
So what does the public record show when the hour runs out? In the material read for this briefing, not a name. The enforcement-actions register extract returned composition, prohibition order and reprimand rows — a 19 September 2025 composition against Singlife Financial Advisers Pte Ltd with regulatory action against eight individuals, a 7 May 2024 Swiss-Asia matter — and no technology-risk notification-breach entry was visible in it (MAS enforcement actions). Sections 6 and 7 of the monograph describe the toolkit without producing a notification case (Monograph). The register extract was partial and the monograph was not read end to end, so this is a bounded negative about the material read, not proof that no such case exists.
What the record does show is recovery. In June 2015 MAS reprimanded SGX for lapses including a failure to recover some critical systems within the four-hour recovery time objective, alongside a S$1 million contribution to its Investor Education Fund and a fee moratorium until remediation was verified (MAS, 25 June 2015). In May 2023 it raised DBS Bank's operational-risk multiplier to 1.8 times — about S$1.6 billion in additional regulatory capital once the February 2022 requirement is counted — after the March and May 2023 disruptions, and that release states no finding about notification timing (MAS, 5 May 2023).
The pattern deserves a precise description. The supervisor can price what leaves a trace. Downtime beyond four hours is measurable after the fact from logs nobody had to volunteer. A late hour is measurable only if somebody kept the detection record and is willing to hand it over.
Aggregate disclosure does not fill the gap, because there is no series to fill. MAS's parliamentary answers give two counts that look alike and are not. On 5 July 2022 it said four major retail banks had reported eight digital-banking interruptions since July 2021, mostly resolved within three hours, affecting on average about 12,000 customers (MAS, 5 July 2022). On 21 April 2023 it said seven domestic systemically important banks had reported 17 digital-banking disruptions lasting more than one hour since 2018 (MAS, 21 April 2023). Different populations, different thresholds, no case identifiers: two point-in-time answers, not a running tally, and neither one tells a reader anything about a notification that arrived at T+3 instead of T+2.
MAS has named this limit itself. Its staff paper on cyber risk surveillance records that "[l]imited data availability is a key challenge" to assessing cyber risk and that "[f]ew datasets are publicly available, given the confidentiality of cybersecurity incidents" (MAS Staff Paper No. 57, February 2020). A supervisor that cannot see the population cannot publish its distribution.
None of this has been written at this desk before. An archive search for "Monetary Authority of Singapore" on 18 November 2026 returned nothing at all; a broader search for "Singapore" returned twenty published pieces — data-centre openings, subsea cables, telecom and cloud profiles, an enforcement directive against a social platform — not one of which reads a supervisory notification duty. The nearest comparison is this desk's briefing of the same day on the European Union's DORA regime, where the first report is anchored to the firm's own classification of an incident as major. The delta is the anchor itself.
Europe's clock starts at a defined classification event; Singapore's starts at a discovery the firm is trusted to recognise.
Which leaves the judgement. Placing the start of the clock in the operator's hands is the right allocation of a fact only the operator holds: nobody at the Authority has the telemetry that would let it declare an incident severe and widespread minutes before the firm does. What is not right is the asymmetry that follows. The number, the criteria and the penalty all sit with the supervisor. The evidence of when the hour began sits with the party the hour times, and the supervisor publishes nothing per incident that would let a reader test one case.
A one-hour deadline whose trigger is unobservable from outside is a strong instrument for getting a telephone call made and a weak one for proving the call was made on time.
What would change that classification is specific. A named composition or reprimand for a late notification, carrying a date, would move the question from design to enforcement. So would any published count of filings received through MAS-Tx that carried a case identifier, or a distribution of notification intervals. Until one of those exists, the hour remains a control whose only witness is the firm being timed.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






