Skip to main content

Cybersecurity Incident Response Plan (Singapore)

Cybersecurity Incident Response Plan (Singapore)

CYBERSECURITY INCIDENT RESPONSE PLAN

Organisation: [Org Name] (UEN: [Org UEN])

Effective Date: [Plan Date]

Plan Owner: [Plan Owner]

1. PURPOSE AND LEGAL BASIS

This Cybersecurity Incident Response Plan ("Plan") establishes the procedures for [Org Name] to detect, respond to, contain, recover from, and learn from cybersecurity incidents. It is prepared in compliance with:

(a) Cybersecurity Act 2018 (No. 9 of 2018) — mandatory incident reporting for CII owners (Section 14);

(b) Personal Data Protection Act 2012 (PDPA) — mandatory breach notification to PDPC within 3 calendar days for notifiable data breaches affecting 500 or more individuals or causing significant harm (Sections 26C–26D);

2. INCIDENT RESPONSE TEAM

Incident Commander: [Incident Commander]

Technical Lead: [Technical Lead]

Legal / Compliance Contact: [Legal Contact]

External IR Firm: [External IR Firm]

The Incident Commander is responsible for activating this Plan, coordinating the IRT, and making decisions on escalation and external notification. The Technical Lead is responsible for technical analysis, containment, and recovery. The Legal Contact is responsible for regulatory notifications and legal privilege assessments.

3. INCIDENT SEVERITY CLASSIFICATION

[Severity Levels]

P1 and P2 incidents require immediate activation of this Plan and notification of the Incident Commander. P3 incidents are handled by the Technical Lead with daily reporting. P4 incidents are logged and reviewed monthly.

4. PHASE 1: DETECTION AND IDENTIFICATION

Detection Procedures: [Detection Procedures]

Upon detection of a potential incident, the first responder shall: (a) record the date, time, and nature of the detected activity; (b) immediately notify the Incident Commander and Technical Lead; (c) preserve all relevant logs and evidence; and (d) classify the incident severity according to the classification matrix.

5. PHASE 2: CONTAINMENT AND ERADICATION

Containment Procedures: [Containment Procedures]

Recovery Procedures: [Recovery Procedures]

6. NOTIFICATION OBLIGATIONS

Regulatory Notification Contacts: [Notification Contacts]

PDPA Breach Notification: If the incident involves a notifiable data breach under the PDPA (affecting 500+ individuals or causing significant harm), the PDPC must be notified within 3 calendar days of the organisation's assessment that the breach is notifiable. Affected individuals must be notified as soon as practicable. The Legal Contact is responsible for PDPA notifications.

Customer and Stakeholder Notification: The Communications team shall prepare customer and media communications under the Legal Contact's supervision. No external communications shall be made without approval from the Incident Commander and Legal Contact.

7. POST-INCIDENT REVIEW

Within 14 days of resolving any P1 or P2 incident, the IRT shall conduct a post-incident review to: (a) document the full timeline and root cause; (b) assess the adequacy of the response; (c) identify remediation actions and responsible owners; (d) update this Plan and associated security controls; and (e) report findings to senior management and, where required, to regulators.

8. PLAN REVIEW

This Plan shall be reviewed and updated at least annually, after any major incident, or when there is a significant change in the organisation's IT environment or applicable regulations. Tabletop exercises simulating a cybersecurity incident shall be conducted at least once per year.

PLAN APPROVAL

This Cybersecurity Incident Response Plan has been reviewed and approved by the Plan Owner: [Plan Owner], on behalf of [Org Name].

Plan Owner (CISO / IT Head)

________________

Signature

Date: ________________

Chief Executive Officer

________________

Signature

Date: ________________

Maintained by Vladislav Sergienko, Founder·Template last modified: ·Report an error

What Is a Cybersecurity Incident Response Plan (Singapore)?

A Cybersecurity Incident Response Plan in Singapore records the items, steps, or particulars it organises for the purpose at hand.

Section 14 of the Cybersecurity Act 2018 requires CII owners to notify CSA of prescribed cybersecurity incidents within the timeframe specified by the Commissioner of Cybersecurity — currently two hours for incidents that have a significant impact on the continuous delivery of the essential service, and 14 calendar days for other reportable incidents affecting the CII. Non-compliance with reporting obligations is an offence under section 14(4), punishable by a fine of up to S$100,000 or imprisonment of up to two years.

Beyond the Cybersecurity Act, the Personal Data Protection Act 2012 (PDPA) mandates data breach notification to the Personal Data Protection Commission (PDPC) within three calendar days of assessing a breach as notifiable under section 26D. A breach is notifiable if it affects 500 or more individuals or is likely to result in significant harm to affected individuals. The PDPA's mandatory breach notification provisions (effective 1 February 2021) overlap with cybersecurity incident response when a cyber attack results in unauthorised access to or disclosure of personal data.

The Monetary Authority of Singapore (MAS) imposes additional incident reporting requirements on financial institutions through MAS Notice on Technology Risk Management (TRM) and the MAS Cyber Hygiene Notice. Financial institutions must report material cyber incidents to MAS within one hour of discovery, maintain detailed incident response plans tested through regular exercises, and conduct post-incident reviews. MAS Technology Risk Management Guidelines (2021) prescribe specific incident response controls, including threat intelligence integration, forensic investigation capabilities, and coordinated response with law enforcement.

SingaporeCERT (SingCERT) — the national computer emergency response team operated by CSA — provides incident response coordination, threat intelligence sharing, and technical assistance to organisations experiencing cyber incidents. Organisations can report incidents to SingCERT through the CSA website or the SingCERT hotline.

The Government Technology Agency (GovTech) and the Smart Nation and Digital Government Office (SNDGO) administer the Whole-of-Government (WOG) incident response framework for government agencies, aligning with the Government Instruction Manual on ICT and Smart Systems Management (IM8). The IM8 framework prescribes mandatory security controls and incident response requirements for all government systems and data.

CSA's annual Singapore Cyber Landscape report documents the evolving threat environment — including ransomware trends, phishing campaign statistics, and sector-specific attack patterns — providing data that organisations should incorporate into their CIRP risk assessments and threat-specific playbooks. The report, published on CSA's website (www.csa.gov.sg), is a primary reference for Singapore cybersecurity practitioners updating their incident response procedures. CSA also coordinates with international partners including the ASEAN CERT and the Asia Pacific CERT (APCERT) for cross-border incident response.

CSA's annual Singapore Cyber Landscape report documents the evolving threat environment — including ransomware trends, phishing campaign statistics, and sector-specific attack patterns — providing data that organisations should incorporate into their CIRP risk assessments and threat-specific playbooks. The report, published on CSA's website (www.csa.gov.sg), is a primary reference for Singapore cybersecurity practitioners updating their incident response procedures.

When Do You Need a Cybersecurity Incident Response Plan (Singapore)?

A Cybersecurity Incident Response Plan is needed by every Singapore organisation that handles personal data, operates information technology systems, or provides services through digital channels — covering virtually all businesses, government agencies, and non-profit organisations in Singapore's highly connected economy.

Critical Information Infrastructure owners designated by the Commissioner of Cybersecurity under section 7 of the Cybersecurity Act 2018 are legally required to maintain a cybersecurity incident response plan as part of their CII security obligations under section 11. The plan must be tested through regular exercises (at least annually), updated when organisational or threat changes occur, and made available for audit by CSA-appointed auditors.

PDPA-regulated organisations — which under the Personal Data Protection Act 2012 includes virtually all organisations collecting, using, or disclosing personal data in Singapore — need a CIRP to meet the mandatory breach notification requirements under section 26D. The three-calendar-day notification deadline to the PDPC requires organisations to have pre-established detection, assessment, and notification procedures. Organisations without a tested CIRP frequently miss the notification deadline, resulting in PDPC enforcement action.

MAS-regulated financial institutions — banks, insurers, capital markets intermediaries, payment institutions, and licensed DPT service providers — must maintain cybersecurity incident response plans complying with MAS Technology Risk Management Guidelines and the MAS Cyber Hygiene Notice. MAS conducts thematic inspections of financial institutions' cyber incident response capabilities and expects plans to include threat-specific playbooks (ransomware, data exfiltration, distributed denial of service, insider threats), escalation matrices, and communication protocols with MAS and law enforcement.

Government agencies and statutory boards in Singapore maintain CIRPs aligned with the Government Instruction Manual on ICT and Smart Systems Management (IM8), administered by GovTech and SNDGO. The Whole-of-Government (WOG) incident response framework coordinates response across agencies.

SMEs and startups in Singapore need CIRPs proportionate to their risk profile. CSA's Cyber Essentials and Cyber Trust marks provide tiered cybersecurity certification frameworks, and both require organisations to demonstrate incident response capabilities as part of the certification process.

Organisations undergoing digital transformation — migrating to cloud infrastructure, deploying IoT devices, adopting AI and machine learning systems — face expanded attack surfaces that demand updated incident response procedures. CSA's cybersecurity advisories and SingCERT alerts highlight emerging threats specific to new technology deployments in Singapore.

What to Include in Your Cybersecurity Incident Response Plan (Singapore)

A Singapore Cybersecurity Incident Response Plan must contain the following elements to satisfy the requirements of the Cybersecurity Act 2018 (for CII owners), the PDPA (for all organisations handling personal data), MAS TRM Guidelines (for financial institutions), and industry standard practices aligned with CSA's Cyber Essentials framework.

**Incident Response Team (IRT) Structure** defines the team members responsible for managing cyber incidents, including: the Incident Response Lead (typically the CISO or Head of IT Security); the Data Protection Officer (DPO) responsible for PDPC notification under the PDPA; the Legal Counsel for regulatory reporting and liability assessment; the Communications Lead for internal and external communications; and technical specialists (network security, forensics, application security). Contact details, alternates, and escalation chains must be documented.

**Incident Classification Matrix** categorises incidents by severity and type. The CSA's Cybersecurity Act reporting framework distinguishes between incidents that have a significant impact on CII continuous service delivery (two-hour reporting deadline) and other reportable incidents (14-day deadline). A typical classification matrix includes: Level 1 (Critical) — service disruption, ransomware, large-scale data exfiltration; Level 2 (High) — targeted attack, partial service degradation, suspected data breach; Level 3 (Medium) — malware infection, phishing compromise, policy violation; Level 4 (Low) — vulnerability discovery, failed attack attempt, security alert.

**Detection and Identification Procedures** describe the tools, processes, and data sources used to detect cybersecurity incidents: Security Information and Event Management (SIEM) systems, Intrusion Detection/Prevention Systems (IDS/IPS), endpoint detection and response (EDR) tools, network traffic analysis, and user behaviour analytics. The plan should reference the organisation's monitoring coverage (24/7 SOC, managed security service provider, or business-hours monitoring) and the initial triage process for security alerts.

**Containment and Eradication Procedures** set out the immediate actions taken once an incident is confirmed: network isolation of affected systems, disabling compromised user accounts, blocking malicious IP addresses and domains, preserving forensic evidence (disk images, memory dumps, log files), eradicating the threat (malware removal, patching exploited vulnerabilities), and validating system integrity before restoration.

**Notification Requirements** document the regulatory reporting obligations with specific timelines: CSA notification within two hours (for CII-impacting incidents under the Cybersecurity Act section 14); PDPC notification within three calendar days (for notifiable data breaches under PDPA section 26D); MAS notification within one hour (for material cyber incidents at financial institutions); notification to affected individuals (required under PDPA section 26D where significant harm is likely); and notification to law enforcement (Singapore Police Force Cybercrime Command) for criminal incidents.

**Recovery and Restoration Procedures** describe the process for restoring affected systems and services to normal operation: validating backup integrity, restoring from clean backups, implementing additional security controls, conducting vulnerability assessments, and confirming that the threat has been fully eradicated before reconnecting systems to the network.

**Post-Incident Review** requires a formal review within 14 days of incident closure, documenting: the root cause; the timeline of detection, containment, and recovery; the effectiveness of the response; lessons learned; and corrective actions to prevent recurrence. CSA, PDPC, and MAS may request post-incident review reports as part of their regulatory follow-up.

**Communication Plan** defines how the organisation communicates during and after an incident: internal notifications to management and affected departments; external communications to customers, business partners, and the media; regulatory notifications to CSA, PDPC, and MAS; and law enforcement coordination with the Singapore Police Force Cybercrime Command. The communication plan should include pre-approved templates for breach notification letters and media statements, reviewed by legal counsel.

The forms-legal.com Cybersecurity Incident Response Plan template is structured to meet the requirements of Singapore's multi-regulator cybersecurity framework, with modular sections for CSA, PDPC, and MAS reporting obligations. Under Singapore law, the Cybersecurity Act 2018 and the Personal Data Protection Act 2012 (PDPA) govern the core requirements for this type of document.

Cite this page

Reference this free template in an article, syllabus, or research note:

APA

Forms Legal. (2026). Cybersecurity Incident Response Plan (Singapore) (Singapore) [Legal document template]. Forms Legal. https://forms-legal.com/singapore/business/policies/cybersecurity-incident-response-plan-singapore

MLA

"Cybersecurity Incident Response Plan (Singapore) (Singapore)." Forms Legal, 2026, https://forms-legal.com/singapore/business/policies/cybersecurity-incident-response-plan-singapore.

BibTeX
@misc{formslegal-cybersecurity-incident-response-plan-singapore,
  author       = {{Forms Legal}},
  title        = {Cybersecurity Incident Response Plan (Singapore) (Singapore)},
  year         = {2026},
  howpublished = {\url{https://forms-legal.com/singapore/business/policies/cybersecurity-incident-response-plan-singapore}},
  note         = {Free legal document template. Based on Companies Act 1967 (Cap. 50)}
}

Also available for these jurisdictions:

Frequently Asked Questions

Based on Companies Act 1967 (Cap. 50) — Template last modified June 2026Verify the source →

This template is provided for informational purposes only and does not constitute legal advice. Laws vary by jurisdiction and change over time. Consult a qualified attorney for advice specific to your situation.Full disclaimer

Found an error? Let us know

Related Documents

You may also find these documents useful: