Skip to content
Back

Incident Timelines, Notifications and Lessons Learned

Keep a reliable incident record, assess the difference between suspected and notifiable breaches, and turn events into stronger controls.

Xian Hui

Xian Hui

9 November 2026 · 5 min read

A team reviews an incident timeline on a whiteboard in a calm meeting

In brief

How should my practice record a cyber incident and decide who needs to be notified?

Keep a factual timeline of observations, affected systems or data, containment actions, approvals and communications. Preserve supporting evidence and distinguish confirmed facts from uncertainty. The responsible team should assess legal and client notification duties, coordinate external statements and review the incident afterwards, assigning an owner and due date to each corrective action.

What you'll learn

  • Record a factual incident timeline
  • Explain the PDPA notification assessment trigger
  • Identify corrective actions after the incident

Incident Timelines, Notifications and Lessons Learned

After a suspicious email is reported, different people may remember different times and actions. One colleague recalls a login alert, another identifies a changed supplier account, and a client asks whether any data was exposed. A reliable incident record helps the firm make decisions based on evidence rather than memory.

The incident lead should build a factual timeline while containment and investigation proceed. The timeline is not a public statement and should record uncertainty clearly.

For the first report and containment steps, see Reporting and Containing a Cyber Incident at Work.

What belongs in an incident timeline?

Use four fields to organise the record:

Timeline fieldWhat to record
TimeWhen the event was noticed, the earliest activity known so far and when stakeholders were contacted.
ObservationWhat data or systems may have been affected.
ActionWhich containment steps were taken.
OwnerWho approved the containment steps.

The entries should distinguish 'confirmed' from 'under investigation'. If new evidence changes the understanding of events, update the record without silently deleting the earlier observation.

Also preserve relevant supporting material such as original messages, authorised access logs, affected file names and transaction references. Limit access to incident evidence because it may contain sensitive personal or client information.

Is every security incident a notifiable data breach?

No. A malware warning does not automatically mean personal data was exposed. A data breach can also arise without malware, for example through an incorrect recipient or overly broad sharing permissions. The firm must establish whether personal data is involved and assess the applicable legal notification requirements.

Under Singapore's Personal Data Protection Act 2012, an organisation that determines a breach is notifiable must notify the Personal Data Protection Commission (PDPC) as soon as practicable, and no later than three calendar days after the day it makes that assessment. This is an important timing distinction. The law's conditions and exceptions must be reviewed in the specific case.

The assessment itself must be reasonable and expeditious. The PDPC's guidelines expect it to be done within 30 calendar days of first becoming aware of a possible breach. If the breach is notifiable, the affected individuals generally must also be told, on or after notifying the PDPC, unless an exception applies.

If your firm processes the personal data on a client's behalf, for example running the client's payroll or keeping its records, it is usually acting as the client's data intermediary. Under section 26C(3)(a) of the PDPA, a data intermediary that has reason to believe a data breach has occurred must notify the client without undue delay. The client then assesses the breach and decides whether to notify the PDPC. Where the firm holds the data for its own purposes, such as its own staff records, the firm itself must assess the breach. Obtain advice on which role applies to each engagement.

Staff should report possible exposures immediately rather than trying to decide whether the statutory threshold has been met. The organisation's appointed responsible team should assess the details, relevant harm and scale, and obtain appropriate advice.

How should the firm communicate?

Assign one owner for external statements. The initial message to affected stakeholders may need to explain what has been established, what is still being investigated and what actions are available. Avoid declaring that no data was accessed without evidence.

A client may have its own contractual notification requirements. The service provider relationship should be reviewed alongside any statutory duties. A Singapore accounting firm's obligations cannot be reduced to a single generic deadline or standard email template.

The CSA's response playbooks distinguish between incident categories, while NIST's small-business guidance describes response, recovery and organisational oversight as related activities.

What should happen after the immediate incident?

Hold a structured review after the urgent risk is controlled. Ask what the first sign was, which control worked, where the team was delayed and which changes are proportionate. Identify an owner and due date for each corrective action.

For example, if a supplier bank-detail change was accepted without independent confirmation, the corrective action should improve the vendor-change procedure, staff training and review evidence. If an old cloud link exposed client data, the correction may involve permission defaults and periodic link reviews.

Final practice scenario

A payroll assistant clicks a false portal link, enters a password and then notices that a client payroll folder was shared externally. In the first ten minutes, the team must report the observed facts, protect the account through its approved response process, restrict further sharing and identify the exposed information. The incident lead then assesses whether regulatory or client notifications are required. Do not claim the breach is notifiable solely because a phishing link was clicked.

Key takeaways

  • Preserve a reliable sequence of observations and actions.
  • Separate a suspected incident from a legally notifiable breach.
  • Do not confuse the PDPA assessment-based deadline with the first time someone notices a problem.
  • Assign owners to corrective actions so the lesson changes the practice's procedures.

Last source check: 9 November 2026.

Back to the start of the course: Why Accounting Firms Are Targets

Sources

Frequently asked questions

This information has been prepared for general informational purposes only and is not intended to be relied upon as accounting, tax, or other professional advice.

Related articles