A pattern that has become hard to ignore in 2026: the data collected during a cyber incident response very often turns into evidence in something else - a regulatory notification, an insurance dispute, a civil claim, or an employment matter arising from how the breach happened. The handover between the IR team and the eDiscovery team has become a routine part of serious incidents.
Where Magnet Axiom Cyber sits
Magnet Forensics' Axiom Cyber is one of the tools driving this convergence. Built on the same engine as the long-established Axiom forensic suite, it is aimed squarely at remote acquisitions from corporate endpoints, cloud sources (Microsoft 365, Google Workspace, AWS) and mobile devices, with a workflow geared to incident timelines and corporate investigations rather than law-enforcement casework.
For an eDiscovery team picking up the work later, two features matter most: full forensic preservation of the source data, and case files that another examiner can open and re-run without going back to the live system.
What good handover looks like
The cases that go smoothly tend to share a few characteristics:
- Preservation happens once, defensibly. Axiom Cyber acquisitions are treated as the master copy, with hashes recorded. Subsequent eDiscovery processing works from those preserved images rather than re-collecting from systems that may have changed.
- Scope is written down. The IR team records which custodians, devices and date ranges were acquired and why. That record feeds straight into the disclosure narrative if litigation follows.
- Indicators of compromise are kept with the evidence. Where the IR team identified specific accounts, files or timestamps as relevant to the incident, those are passed across so the eDiscovery review can prioritise them.
Why this matters now
Two forces are pushing this together. First, regulators - including the ICO and the FCA in the UK - increasingly expect organisations to demonstrate not just that they responded to an incident, but that they preserved evidence to a standard that supports later analysis. The ICO's personal-data-breach guidance makes preservation expectations explicit. Second, cyber-insurance claims and follow-on litigation are now common enough that IR teams routinely assume their work product will be scrutinised by lawyers later.
Practical takeaways
For organisations: agree in advance, before an incident, who owns preservation, in what tool, and how the handover to eDiscovery will work. For legal teams: when an incident occurs, ask what was acquired, in what format, and what the chain of custody record looks like - before any further collection runs.
The Magnet Forensics blog publishes useful case-study material at magnetforensics.com/blog, and SANS DFIR continues to be a strong source of practitioner-level guidance on the IR / forensics overlap at sans.org/blog.
§ From the guide, latest version
Guide 4: Finding the Evidence - A Lawyer's Map of Modern Electronic Data SourcesGuide 4. Finding the Evidence: A Lawyer's Map of Modern Electronic Data Sources Computers, phones, email, cloud platforms, Teams, Slack, file servers, NAS, SaaS, databases, CCTV, backups, CRM, ERP, social media, messaging apps, logs, IoT and third parties - where evidence lives today, how volatile each source is, and how to map a client's estate before anything disappears. Contents 1 Executive summary 2 The problem in plain English: the evidence map has exploded 3 Why it matters legally: search duties start with source identification 4 Important terminology 5 The evidence-source map: eight families 6 Family 1: end point devices - computers, phones, tablets, removable media 7 Family 2: email systems - corporate, hosted, webmail and personal 8 Family 3: cloud productivity and collaboration - M365, Google, Teams, Slack 9 Family 4: file storage - servers, NAS, sync-and-share platforms 10 Family 5: structured systems - databases, accounting, CRM, ERP 11 Family 6: messaging and social - Whats App, Signal, SMS, social media 12 Family 7: logs and the physical world - CCTV, access control, IoT, web logs 13 Family 8: backups, archives and third-party holders 14 Volatility: which sources die first 15 The source-mapping workflow: seven steps to a defensible data map 16 Decision tree: which sources to pursue, park or release 17 Worked example 1: mapping Aldgate's estate in a fortnight 18 Worked example 2: the opponent's estate - Harlow, its MSP and the backup vault 19 Worked example 3: one custodian, eleven sources - the departed director 20 The custodian and source questionnaire: 43 questions in three parts 21 Preservation and collection notes by family 22 Privilege and confidential it y considerations 23 UK GDPR and data minimisation when mapping sources 24 Proportionality: mapping everything, collecting selectively 25 Common mistakes and how to avoid them 26 Technical limitations lawyers should understand 27 Questions lawyers should ask the opponent about their sources 28 Questions lawyers should ask a forensic or e Disclosure provider 29 Suggested wording for instructions 30 Checklist: the source-mapping essentials 31 Red flags 32 When to involve a digital forensic expert 33 How the rules differ: Scotland, NI, arbitration, tribunals, criminal 34 Glossary 35 Authoritative UK references 36 How a specialist laboratory can assist Volatility: preserve in volatility order, argue in importance order. Days to weeks - act same day. Weeks to months - act in week one. Months - act before the window closes. Quarters to years - scheduled threats. Stable until touched.
