KB Kookmin took 68 hours to detect its intrusion, against 15 at Shinhan
Singapore's cyber chief Gwenda Fong urged continuous monitoring a day after Korea's FSC found weaknesses at 130 of 555 inspected firms. Singapore's two-hour reporting clock starts only once an incident is known, so the hours before discovery are where monitoring works.
The Investor · Invest desk

Three figures: Singapore requires specified incidents to be reported within 2 hours of becoming known; KB Kookmin took 68 hours to detect an intrusion; Hana took 42 hours, per incident reports obtained by Korean lawmakers.
| Figure | Value | Note | Claim |
|---|---|---|---|
| Singapore deadline to report, once an incident is known | 2 hours | 9 | |
| KB Kookmin time to detect | 68 hours | 7 | |
| Hana time to detect | 42 hours | 7 |
What happened
- Korea's FSC separately disclosed cyber intrusions at 16 financial companies the day before Fong spoke.
- The weaknesses found in the FSC inspection included outdated software, inadequate access controls and insufficient monitoring.
- At Shinhan, KB Kookmin and Hana banks, hackers got to customer data through apps that staff and loan brokers use.
Why it matters
- constraint A reporting deadline that starts at discovery cannot shorten the interval before discovery, so a Korean version of Singapore's rule would leave KB Kookmin's 68 hours untouched.
- decision Banks must decide whether new monitoring spend goes to core systems or first to an inventory of contractor-built and loan-broker apps that may sit outside any monitoring.
- exposure Until FIRST is expanded, what one firm detects on its own protects only that firm, leaving the other financial companies blind to it.
Detection time is the figure a periodic security check cannot move. According to incident reports obtained by Korean lawmakers, Shinhan took about 15 hours to detect its intrusion, Hana 42 hours and KB Kookmin 68 [7]. The mean is about 42 hours [13], and KB Kookmin waited 4.5 times as long as Shinhan [14]. An inspection samples a system on one date. It cannot say how long an intruder sat inside between dates, and that is the gap Fong was pointing at when she said organizations must move beyond a "compliance-based mindset" centered on periodic checks [1].
Singapore's reporting rule shows where its clock starts. Under amendments implemented in October 2025, specified incidents at designated critical infrastructure operators must be reported within two hours of becoming known [9]. If Korea set a similar rule, KB Kookmin's regulator would hear at hour 70 at the latest [16]. Faster reporting trims the last two of those hours and leaves the first 68 alone.
The thesis can fail in a few places. Monitoring limits damage, and Singapore's own case shows it does not guarantee entry is blocked: hackers linked to UNC3886 got into the four leading telecom operators [10], the response ran more than 11 months, attackers penetrated some systems and took limited technical information, and authorities reported no service disruption [11]. The exposure may also sit outside anything a bank would think to monitor. Microsoft's Mike Yeh told The Korea Herald that large organizations often rely on contractor-built software, sometimes through "independent projects that may not be supported anymore" [12], and the Korean intrusions ran through apps used by employees and loan brokers [6]. And one firm's monitoring helps its peers only if the findings travel. The FSC acknowledged that threats individual firms detect on their own have not been shared through FIRST [8].
We think the continuous-monitoring argument fits these banks on the evidence of the clock, with a limit. The FSC's inspection found weaknesses at 130 of 555 firms, or 23.4% [15], and insufficient monitoring is one of three named categories [5]; The Korea Herald does not break the 130 down by category. The view is wrong if the slow detections trace to unsupported contractor software that no monitoring covered, in which case an inventory of those apps comes before any new monitoring contract. Either way, budget spent preparing for the next inspection is not spent watching the loan-broker apps.
What to watch
- Whether Korean regulators set a reporting deadline measured from detection, as Singapore's two-hour rule is.
- Whether the FIRST expansion lets firms push self-detected threats to the whole sector, and when it goes live.
- Whether further incident reports place the slow detections in contractor-built or unsupported applications.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence55
- Adoption
- Insufficient
- Hype gap−10
- Incentives40
- Confidence60
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Gwenda Fong, chief executive of Singapore's Cyber Security Agency, said organizations must move beyond a "compliance-based mindset" centered on periodic security checks, particularly as AI enables hackers to exploit vulnerabilities faster and at greater scale.
- [2]
Fong called for continuous monitoring and closer government-business cooperation at a media roundtable during Singapore International Cyber Week 2026, a day after South Korea's FSC disclosed cyber intrusions at 16 financial companies.
- [3]
South Korea's Financial Services Commission disclosed cyber intrusions at 16 financial companies.
- [4]
A separate FSC inspection of 555 firms found security weaknesses at 130.
- [5]
The weaknesses found included outdated software, inadequate access controls and insufficient monitoring.
- [6]
Hackers accessed customer information through applications used by employees and loan brokers at Shinhan, KB Kookmin and Hana banks.
- [7]
According to incident reports obtained by Korean lawmakers, Shinhan took approximately 15 hours to detect an intrusion, compared with 68 hours at KB Kookmin and 42 hours at Hana.
- [8]
The FSC acknowledged a gap in its threat-sharing platform FIRST: threats detected independently by individual financial companies have not been shared through it. The commission plans to expand the platform to enable industry-wide sharing.
- [9]
Amendments to Singapore's cybersecurity legislation, implemented in October 2025, expanded reporting obligations for designated critical infrastructure operators to cover certain suspected advanced persistent threat attacks and disruptions involving noncore systems; specified incidents must be reported within two hours of becoming known.
- [10]
Last year hackers linked to advanced threat group UNC3886 infiltrated Singapore's four leading telecommunications operators, and CSA coordinated a response involving more than 100 government cybersecurity specialists alongside the companies.
- [11]
The operation lasted more than 11 months; attackers penetrated some systems and stole limited technical information, but authorities reported no disruption to telecommunications services or evidence of sensitive customer records being stolen.
- [12]
Mike Yeh, Microsoft's vice president and deputy general counsel for customer security and trust, told The Korea Herald that large organizations often rely on customized software developed by outside contractors, sometimes through "independent projects that may not be supported anymore."
- [13]
Mean detection time across the three banks is about 41.7 hours.
- [14]
KB Kookmin's detection time was 4.5 times Shinhan's.
- [15]
Weaknesses were found at 23.4% of the 555 inspected firms.
- [16]
Under a two-hour reporting rule that starts at detection, an intrusion detected after 68 hours would be reported by hour 70 at the latest.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- koreaherald.comBeyond firewalls: Singapore's cyber playbook for Korean banks
1 article · October 14, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- Incident detection and reportingFollow
- Threat Intelligence SharingFollow
- Financial Sector CybersecurityFollow