Incident response
Cyber incident response in Singapore: the first 72 hours
- Contain first, investigate second. Isolate affected systems without destroying evidence.
- Engage counsel at hour zero so forensic work can attract privilege and notification decisions are made correctly.
- PDPC: notify within 3 calendar days of assessing a breach as notifiable (likely significant harm, or 500+ individuals).
- MAS (financial institutions): relevant incidents must be reported within 1 hour of discovery under the technology risk management notices, with a root cause report within 14 days.
- Notify your cyber insurer within the policy timeline. Late notice can put cover at risk.
Every cyber incident looks different from the inside: a ransomware note, an exchange account drained overnight, a vendor's email saying a database has been exposed. The first 72 hours, though, follow a familiar pattern, and the decisions made in that window largely decide the regulatory, financial and litigation outcome. This is the sequence I recommend.
Hours 0 to 4: lock it down
- Isolate compromised systems, but don't wipe or rebuild them. You'll need the evidence.
- Revoke and reset compromised credentials, API keys and session tokens immediately.
- Turn on enhanced monitoring across the systems that are still running.
- Preserve logs and forensic evidence before retention windows roll over.
- For trading platforms, consider halting fresh trades and new positions on affected accounts, not only withdrawals. Attackers with access to several accounts can keep moving value through "contra trading" while withdrawals are frozen.
Hours 4 to 24: assess and assemble the team
Work out what data or assets were accessed or taken, how many users are affected, and whether the incident is notifiable. Then stand up a response team with clear roles:
- Technical: forensics, containment and evidence preservation.
- Legal counsel: privilege, regulatory assessment, preserving recovery options.
- Board and senior management: scope, exposure, decisions and stakeholder management.
Why counsel should come in at hour zero: forensic reports commissioned by or for lawyers in contemplation of litigation stand a much better chance of being privileged. Reports commissioned directly by IT or management may later be disclosable to regulators, counterparties and claimants.
The regulatory clocks
PDPC (Personal Data Protection Act)
A data breach is notifiable if it results in, or is likely to result in, significant harm to affected individuals, or if it affects 500 or more individuals. Once you assess that a breach is notifiable, you must notify the PDPC as soon as practicable and no later than 3 calendar days afterwards, and notify affected individuals where significant harm is likely.
The clock runs from your assessment, but the assessment itself has to be done expeditiously. Delaying it to buy time is not an option. For platforms, consider whether "affected individuals" includes downstream users whose accounts could be compromised using the leaked data.
MAS (financial institutions)
Financial institutions must notify MAS as soon as possible after discovering a reportable incident, and no later than the timeline in the applicable notice. Under the MAS technology risk management notices, a relevant incident must be reported within 1 hour of discovery, followed by a root cause and impact analysis report within 14 days. Since 1 February 2026, reports go through MAS's updated incident reporting template (MAS circular).
Cybersecurity Act and other regimes
Owners of critical information infrastructure have separate, short reporting deadlines to the Cyber Security Agency. If you have users or operations in other jurisdictions, check their regimes in parallel. Under the EU GDPR, for example, a notifiable breach must generally be reported to the supervisory authority within 72 hours of becoming aware of it.
Insurers: notify early
Cyber policies often require notice within a short window, and they may require you to use the insurer's panel of forensic, legal and PR vendors. Read the notification clause on day one. Late notice, or appointing your own vendors without consent, can put cover at risk. Also make sure that what you tell the insurer is consistent with the security declarations you made when buying the policy.
Days 2 to 3 and beyond: stakeholders and recovery
- Affected users: transparent notice, clear remediation steps and support channels.
- Regulators: keep them updated and prepare for root cause analysis.
- Vendors and partners: assess their role and preserve claims against them. Many breaches start with a third-party API integration.
- Media: controlled, factual messaging if the incident becomes public.
Where funds or digital assets have been stolen, speed decides whether recovery is possible. Trace on-chain and through the banking system, engage exchanges and off-ramps quickly, and consider urgent interim relief: freezing injunctions, proprietary injunctions, and Bankers Trust or Norwich Pharmacal disclosure orders. For tokenised assets, consider token-level remedies such as burn, freeze and remint where the issuer's terms allow them. See Burn, freeze and remint.
Before the next incident: a readiness checklist
- An incident response plan with named roles, including who is authorised to notify regulators out of hours
- An established relationship with external counsel
- A shortlist of forensic vendors
- A cyber insurance policy you have read and understood, including triggers, exclusions and panel vendors
- Pre-mapped stakeholder contact lists
- Terms of service that support security measures such as freezes, forced resets and re-verification
- Vendor and API contracts with breach notification duties and rights to information
- Tabletop exercises at least once a year
Get the full Cyber Incident Response Playbook. The complete version covers ransom demands and sanctions risk, insurer strategy, communications templates and asset recovery steps.
Download the playbookFrequently asked questions
- How quickly must a data breach be reported to the PDPC?
- As soon as practicable, and no later than 3 calendar days after assessing that the breach is notifiable, that is, likely to cause significant harm or affecting 500 or more individuals.
- When must a financial institution notify MAS of a cyber incident?
- Under the MAS technology risk management notices, within 1 hour of discovering a relevant incident, followed by a root cause and impact analysis report within 14 days.
- Should we pay a ransom?
- It's a legal, commercial and ethical decision that needs specific advice, including on sanctions exposure, insurance coverage and law enforcement engagement. Don't decide it without counsel.
This article is general information as at the date above and is not legal advice. Regulatory timelines change and depend on your sector and circumstances. Take specific advice on any incident.
