On this page

Decide which evidence the support arrangement can produce

A machine problem may involve the customer, a local service partner, the overseas manufacturer and another software supplier. Their clocks, access records and responsibilities may differ. If nobody has planned how to preserve the relevant records, reconstructing the event can become slow and contentious.

The National Institute of Standards and Technology (NIST) framework for operational technology (OT) forensics explains that evidence preparation and response must account for effects on operation and safety. The business should involve qualified responders and the customer’s authorised team; this article does not tell a technician to collect data from a live system.

Sources: National Institute of Standards and Technology: Introduction and preparation/evidence-recording discussion; safety and operating implications of forensic actions

An overlapping login is evidence of timing, not proof of cause

Fictional example: the customer reports a machine interruption at 01:00 UTC. A vendor account record shows a session from 00:50 to 01:05 UTC. Those two records establish a reported interruption and a session that overlaps it. They do not establish what caused the interruption or what the user changed.

Check time zones, clock accuracy, the source of each record and what activity it actually covers. Keep an unanswered question explicit rather than filling the gap with an assumption.

Timeline entryRecord to preserve through the authorised processWhat remains unknown
Customer reports interruptionOriginal report, its timestamp and reporting person/roleWhen the physical issue began and how it was observed.
Vendor session overlapsOriginal access/activity record and time basisWhich actions occurred and whether they affected operation.
Local changes after the reportAuthorised change record and decision-makerWhether a later action altered evidence or the fault condition.

Rehearse the request for records

Use a fictional incident and approved test information. Ask each organisation which records it can supply, who authorises release and how the team will preserve originals and record subsequent handling. Do not put credentials or customer logs into a public expansion brief.

The rehearsal should reveal missing records, unclear permissions and unavailable expertise. It cannot prove legal admissibility or replace a real incident-response plan. The customer retains its operational and safety decisions.

Make the evidence gap an owner decision

Before selling remote support, cost the agreed logging/retention capability, qualified response access and coordination work. Actual contract, privacy, sector and notification duties need their own assessment; there is no universal reporting deadline in this guide.

If a supplier cannot provide the records the proposed service needs, resolve that limitation, narrow the service or document the remaining risk with the appropriate customer decision-maker.

Scope

  • Evidence-preparation guidance and a fictional timeline, not forensic collection instructions, a finding of causation, legal chain-of-custody certification or incident-reporting clearance.

Next step

Use the Relationship factsheet to identify the organisations and record-release responsibilities. Keep the detailed incident evidence plan in authorised operating systems, with a named task to resolve each gap.

Sources & review notes

Access dates show when a source was retrieved. Review dates show when its meaning was checked. Editing this guide does not recheck the law.

Digital Forensics and Incident Response Framework for Operational Technology, NIST IR 8428

National Institute of Standards and Technology

Passage, dates and research notes

official-guidance · Introduction and preparation/evidence-recording discussion; safety and operating implications of forensic actions

Accessed: 2026-11-15T18:17:06.629053+00:00 · Meaning reviewed: 2026-11-15T18:29:43.337732+00:00 · Next review target: 2026-12-15

Read the OT-specific evidence-preparation and investigation context. Used to plan records and qualified response, not to teach collection commands, certify chain of custody or establish a reporting deadline.

Your learning

Bookmark this guide or mark it as read.

Learning library
Progress privacy

Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.

This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.