Digital forensics for SMEs: what matters after a cyberattack

After a cyberattack, management wants to get back to work as quickly as possible. But reinstalling everything straight away wipes out exactly the traces that show how the attackers got in and which data they took. Digital forensics answers these questions. This article explains why an SME needs it, what to do and what to avoid in the first hours, how forensic consulting works and how to recognise a reliable provider.

12 min read CyberTell
Key takeaways
  • Forensics establishes the cause, the scope and any data exfiltration. An SME needs these answers to notify the FDPIC, to file a criminal complaint and to deal with its insurer.
  • In the first hours: disconnect affected devices from the network, but do not switch them off or rebuild them, preserve the logs and record every step with the time and time zone.
  • Notifying the FDPIC does not wait for the forensic report. It happens as quickly as possible, and missing details are submitted later.
  • Without retained logs, even the best forensic work can reconstruct little. Log retention and a consistent system time belong in your preparation.

Why digital forensics after a cyberattack?

Digital forensics is the methodical examination of storage media, memory, logs and network data after a security incident. For an SME this is rarely about a court case. It is about three questions that remain open after every serious attack:

  • Cause: How did the attackers get in: through a phishing email, a remote access point or an unpatched vulnerability?
  • Scope: Which systems and accounts were affected, and since when?
  • Exfiltration: Was data copied, and if so, which data and how much?

The US National Institute of Standards and Technology (NIST) describes the aim of the analysis as determining the sequence of events and the systems involved and finding the underlying root cause (SP 800-61 Rev. 3, April 2025). Without these answers, the way in may stay open.

Who needs the answers

  • FDPIC: If a data security breach is likely to result in a high risk for the persons concerned, it must be notified to the Federal Data Protection and Information Commissioner (FDPIC) as quickly as possible (Art. 24 FADP). Where possible, the notification states the time and duration as well as the categories and approximate number of the data and persons concerned (Art. 15 DPO). This is exactly what forensics clarifies.
  • Prosecution: A criminal complaint needs preserved evidence. The Federal Office for Cybersecurity (BACS) advises deciding early whether a forensic investigation is needed, especially if you plan to press charges.
  • Insurance: A cyber insurer will ask about cause and damage. Check early whether it prescribes a service provider and which costs it covers.

The first hours: what to do and what to avoid

The first hours decide whether there will be anything left to investigate. Every action on an affected system changes traces, including well-meant tidying up. After a ransomware attack, the BACS recommends disconnecting infected systems from the network immediately, including Wi-Fi. A specialist should back up cache data and hard disks before anyone attempts repairs or restarts; afterwards, it says, a forensic investigation is almost impossible.

Switching off is not a good idea. Memory holds running processes and open connections, and it is empty after a shutdown. The guideline RFC 3227 therefore advises not to shut a system down until evidence collection is complete. NIST points out the trade-off: even disconnecting from the network can cost volatile data. It is best to define the criteria for this decision in advance.

  1. Disconnect, do not switch off

    Pull the network cable and disable Wi-Fi. The device stays on until memory has been captured or someone has consciously decided not to.

  2. Preserve the logs

    Firewall, email, sign-ins, remote access, backup system and cloud services: export the logs before they are overwritten or an attacker deletes them. Include a period before the incident.

  3. Do not reinstall anything

    No reinstallation, no reset and no virus scans that delete files until the traces are preserved. Keep encrypted data and backups.

  4. Note the time and time zone

    Record the time of every observation and whether it is Swiss time or UTC. Note any system clocks that are off, or the timeline will not add up later.

  5. Log every step

    Who did what, when and on which device? A running record is the basis for the notification, the complaint and the report.

  6. Get help

    Bring in a forensic specialist, your IT provider and your insurer early. File a criminal complaint with the cantonal police where your company is based.

Incident Management Sample data
Incident ticket with history: every step with time and person Incident ticket with history: every step with time and person
Incident ticket with history: every step with time and person

The chain of custody: every piece of evidence needs a history

A log extract is only worth as much as the proof that nobody has altered it. The chain of custody therefore records without gaps who had a piece of evidence when, and what was done with it. NIST describes the building blocks: log every person with access, record every action with its time, store the original securely, work only on copies and verify the integrity of original and copy with checksums (SP 800-86).

In its guideline on IT forensics, the German Federal Office for Information Security (BSI) sets out six requirements for an investigation: accepted methods, robust tools, repeatable results, demonstrable integrity of the traces, traceable links between events and traces, and documentation of every step.

Not every incident ends up in court. NIST notes that most malware incidents do not lead to prosecution, but the data collected is still evidence. If it is unclear whether evidence will be needed, it should be preserved by default. For an SME this means in practice:

  • compute a checksum (for example SHA-256) before a file is handed on
  • record every handover: from whom, to whom, when and why
  • keep originals unchanged and access-protected
  • also file photos of screens and ransom notes with the time they were taken

Plan log retention in advance

Forensics can only reconstruct what was recorded somewhere. If the logs are overwritten before anyone secures them, the most important question stays open: since when were the attackers in the network? Retention therefore belongs in preparation, not in the crisis.

  • What: sign-ins and failed sign-in attempts, remote access such as VPN and remote desktop, firewall, mail gateway, administrator activity and cloud services such as Microsoft 365.
  • How long: NIST recommends retention policies that allow a look back (SP 800-86). For certain processing, the Swiss Data Protection Ordinance requires logs to be kept for at least one year separately from the system: where sensitive personal data is processed by automated means on a large scale or high-risk profiling takes place, and preventive measures cannot guarantee data protection (Art. 4 DPO).
  • Where: separate from the monitored system, so that an attacker with administrator rights cannot delete their own traces.
  • Which time: all systems take their time from the same source (NTP). Only then can events from different logs be joined into one timeline.

Logs also help with the duty to notify. According to its guideline on Art. 24 FADP, in its practice the FDPIC was able to take immediate measures into account where a controller could use logs to rule out within hours, with sufficient probability, that data had been misused. Without logs, this proof is missing.

Also decide who may engage a forensic specialist in an emergency and who hands over the logs. An agreement with a provider made before anything happens saves the search during the crisis.

Notification, complaint and insurance run alongside forensics

Forensics takes time; the notification cannot wait. The FDPIC makes it clear in its guideline: anyone who recognises a likely high risk must not wait for lengthy investigations that confirm or rule it out beyond doubt. With ransomware, depending on the circumstances, a likely high risk must be assumed after an initial analysis.

  • FDPIC: mandatory notifications go through the DataBreach reporting portal. You submit missing details as quickly as possible (Art. 15 para. 2 DPO), and the portal allows follow-up notifications for this. A notification under Art. 24 FADP may only be used in criminal proceedings against the person required to notify with that person’s consent.
  • Documentation: data security breaches must be documented with the facts, their effects and the measures taken. The documentation must be kept for at least two years from the notification (Art. 15 para. 4 DPO).
  • Criminal complaint: with the cantonal police where your company is based. The BACS advises against paying a ransom. Anyone still considering it should discuss it with the cantonal police.
  • BACS: operators of critical infrastructure must report cyberattacks within 24 hours of discovery and have 14 days to complete the report.

This information is for orientation and does not replace legal advice.

How forensic consulting works

Forensic consulting usually starts with a conversation: what happened, which systems are affected, what has already been done, and which questions should the investigation answer? The clearer the questions, the more targeted the work. Then the actual investigation follows. NIST divides it into four phases (SP 800-86).

  1. Collection

    Identify data sources, prioritise them by volatility and value, secure the data and verify its integrity with checksums.

  2. Examination

    Extract the relevant traces from the secured data without changing the original.

  3. Analysis

    Join the traces into a timeline and answer the questions of cause, scope and exfiltration.

  4. Reporting

    Document results, approach and open points so that management, authorities and the insurer can work with them.

How to recognise a reliable provider

How good an investigation is only shows in the result. Some points can be checked beforehand, though:

  • Accepted methods: the provider explains which procedures it follows, and a third party would reach the same result from the same data. The BSI lists acceptance, credibility and repeatability as requirements.
  • Demonstrable integrity: every image has a checksum, every handover is logged.
  • Open-minded: a forensic investigation looks for traces that support an assumption and for traces that refute it (BSI). Anyone who knows the culprit before the analysis is not working forensically.
  • Honest limits: a sound report also says what the data cannot show. NIST explicitly names the outcome that no conclusion can be drawn yet.
  • Clear agreements: mandate, scope, cost range, availability and confidentiality are settled in writing before any data is handed over. Investigation records contain sensitive information and belong only in authorised hands (NIST SP 800-61 Rev. 3).
  • No guarantees: be wary of promises to recover all data or to name the culprits with certainty.

IT partners that list incident response among their services can be found in the partner directory. Whether your company’s addresses have already turned up in data leaks is shown by the free threat analysis.

Investigations and evidence in CyberTell

CyberTell does not replace a forensic specialist or the imaging of memory and hard disks. It does keep in one place what is produced during and after an incident, and gives your provider an organised starting point.

  • Ticket and history: in incident management, every report becomes a ticket with priority, owner and a message thread including edit history.
  • Investigation with a guide: for larger cases you open an investigation, optionally with a forensic template, for example for ransomware, data exfiltration or a compromised account. The template guides you through scope, evidence collection, chain of custody, reporting channels and recovery.
  • Evidence with checksums: files such as log extracts, emails, network captures or screenshots automatically receive a SHA-256 checksum on upload, together with the time and the person uploading. CyberTell parses PCAP, log and EML files automatically.
  • Timeline: you record events with time, source and severity and link them to evidence and indicators. The AI suggests entries based on indicators and evidence; only what you select is added. The timeline can be exported as CSV.
  • Report and evidence bundle: the investigation report is produced as a PDF. The evidence bundle contains the report, the original files and a manifest with all checksums. If a file differs from the checksum stored on upload, the manifest flags the mismatch.
Incident Management Sample data
Investigation of a security incident with IoC graph Investigation of a security incident with IoC graph
Investigation of a security incident with IoC graph

Coordination in the war room

During an investigation, management, IT, the external forensic specialist and often the insurer work at the same time. If coordination runs through private chats and long email chains, in the end nobody knows what was decided.

The war room brings this coordination together: a team chat with file attachments, linked to the incident tickets, with participant management and a chronological history. Anyone joining later reads up instead of asking around. The history later shows who decided what and when, and helps with documenting the data security breach.

How incident handling works as a whole, from the first report to lessons learned, is covered in the article Incident response for SMEs.

Incident Management Sample data
Active war room with team chat and running playbook Active war room with team chat and running playbook
Active war room with team chat and running playbook

Frequently asked questions

What is digital forensics?
Digital forensics is the methodical examination of storage media, memory, logs and network data to clarify an incident. It preserves traces so that their integrity can be proven, and it answers the questions of cause, scope and data exfiltration.
Should I switch off an infected computer?
No. Disconnect it from the network and leave it on, because the contents of memory are lost on shutdown. The BACS recommends having a specialist back up cache data and hard disks before any restart or repair attempt.
Do I have to wait for the forensic results before notifying the FDPIC?
No. The notification is made as quickly as possible once a likely high risk for the persons concerned is apparent. You submit missing details later; the FDPIC reporting portal allows follow-up notifications for this.
How long should an SME keep logs?
Swiss data protection law sets a minimum period only for certain cases: for large-scale automated processing of sensitive data or high-risk profiling, the Data Protection Ordinance requires at least one year. Choose a period that lets you look back far enough in an emergency, and bear in mind that logs themselves contain personal data.
Topics

Sources

  1. Bundesgesetz über den Datenschutz (DSG), SR 235.1, Art. 5 und 24
  2. Datenschutzverordnung (DSV), SR 235.11, Art. 4 und 15
  3. EDÖB: Leitfaden betreffend die Meldung von Datensicherheitsverletzungen und Information der Betroffenen nach Art. 24 DSG (Version 1.2, 23.4.2025)
  4. Bundesamt für Cybersicherheit BACS: Ransomware – Was nun?
  5. NIST SP 800-86: Guide to Integrating Forensic Techniques into Incident Response (2006)
  6. NIST SP 800-61 Rev. 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management (April 2025)
  7. RFC 3227: Guidelines for Evidence Collection and Archiving (2002)
  8. BSI: Leitfaden IT-Forensik (Version 1.0.1, März 2011)