Skip to content
Back

Reporting and Containing a Cyber Incident at Work

Learn the first safe steps when a suspicious attachment, compromised account, missing device or misdirected payment is discovered.

Xian Hui

Xian Hui

9 November 2026 · 4 min read

An accountant unplugs a laptop's network cable while a colleague raises a hand to alert the team leader

In brief

What should I do if I suspect a cyber incident at my accounting practice?

Report the concern promptly to your practice's designated incident lead through a trusted channel. Describe what you observed, when it happened, the device or account involved and any client records or payments that may be affected. Follow the agreed containment instructions, record actions already taken and avoid improvising repairs.

What you'll learn

  • Identify common incident triggers
  • Report the facts needed for triage
  • Avoid unsafe attempts to conceal or repair an incident

Reporting and Containing a Cyber Incident at Work

An accountant clicks an attachment and the computer begins behaving unexpectedly. The employee is tempted to restart it several times, delete the email and continue with another task. A more useful action is to contact the firm's designated incident lead and describe exactly what happened.

Early reporting is a control. It allows the right people to decide whether an event is harmless, a suspected compromise or a confirmed incident. Staff do not need to diagnose malware or prove wrongdoing before raising a concern.

What events should be reported?

An unusual email alone may be a suspicious event. An unexpected sign-in alert, a missing company laptop, confidential information sent to the wrong recipient, or bank details changed without approval may require urgent assessment. A blocked file or unfamiliar security warning also warrants attention if it appears during normal accounting work.

For attachment-related concerns, see Handling Suspicious Attachments and Malicious Downloads.

Tell staff what route to use when the ordinary messaging system or email may be affected. The response contact should be available without searching through the potentially compromised account.

What information does the response lead need?

Use a concise first report:

Report detailWhat to include
ObservationWhat you observed, without guessing at the cause.
Timing and accessWhen it happened and which device or account was involved.
Potential impactWhich client records, payments or applications might be affected.
Actions takenWhat you clicked, downloaded, entered, sent or changed.
Current activityWhether the suspicious activity is still happening.
Trusted contactHow to reach you through a trusted channel.

The report is most useful when it distinguishes direct observations from assumptions. 'I entered my password on a page opened from the email' is more actionable than 'Someone may have hacked us'.

Should the employee disconnect the device?

The right containment step depends on the suspected threat. For a likely ransomware infection, the Singapore Police Force's ransomware guidance discusses isolating affected devices. The default rule for staff is to disconnect the device from the network, unless the firm's response plan or response lead says otherwise. Do not power it off, restart it or delete anything, and report at once. An uncoordinated shutdown or deletion may affect evidence or recovery.

For a suspected compromised online account, the response team may revoke sessions, reset credentials, review mailbox forwarding rules and check related integrations. For a misdirected payment, the urgent action may instead be contacting the bank and relevant authorities. A single generic incident script cannot cover every scenario.

For related payment controls, see Designing Payment Approvals That Resist Impersonation.

Outside the firm, the incident lead can report cybercrime to the Singapore Police Force and report incidents to CSA's SingCERT. The CSA's incident response playbooks provide separate guidance for malware, ransomware, business email compromise and cloud incidents.

What should staff avoid?

Do not conceal the action that led to the issue. Do not share suspicious files widely as 'proof', investigate by entering more passwords into questionable sites, or tell clients that everything is safe before the facts are checked. If someone else is affected, avoid informal assurances and let the authorised contact manage communications.

Record what has already been done. If a device was disconnected, a password reset or a recipient contacted, say so. This avoids contradictory actions and helps responders reconstruct the timeline.

How can the team practise?

Use a fictional scenario: an employee uploads a client's payroll file to a cloud folder accessible by the wrong external contact. Ask who reports, who restricts access, who identifies the records and who decides whether the client or regulator must be notified.

A tabletop exercise is not about assigning blame to the employee. It tests whether the firm has a workable chain of responsibility. The NIST small-business guide treats response and recovery as part of continuing risk management.

Key takeaways

  • Report unusual security events promptly, even when the cause is uncertain.
  • Give factual detail about actions, accounts, devices and possibly affected records.
  • Follow the relevant incident playbook rather than improvising repairs.
  • Let designated staff coordinate containment, evidence and communications.

Last source check: 9 November 2026.

Next in the course: Incident Timelines, Notifications and Lessons Learned

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