By Robert Knudsen, Computer forensics and cybersecurity examiner, Global Digital Forensics

Where Offboarding Meets Digital Evidence Inside an Enterprise

In the vast majority of corporate trade secret disputes, employment lawsuits and internal compliance inquiries, the critical moment for digital evidence comes during routine corporate offboarding rather than at the hands of sophisticated hackers. When a key executive or engineer resigns, human resources notifies IT, a helpdesk technician boots up the returned laptop to check its condition or copy desktop folders, and an automated script revokes the user Microsoft 365 license and wipes their corporate iPhone for reassignment. Within forty eight hours of that uncoordinated handoff, thousands of operating system timestamps are altered, solid state garbage collection purges deleted files and the thirty day cloud mailbox deletion timer begins ticking.

Establishing Defensible Preservation Gates Between HR, IT and Legal

Global Digital Forensics partners with general counsel, outside litigators, internal auditors and IT security leaders to build documented forensic preservation gates into offboarding. Whenever a departing employee worked with sensitive intellectual property, client lists or executive strategy, their returned hardware goes straight into physical quarantine, powered off and with the user profile left closed. At the same time, IT administrators must suspend the custodian login credentials and revoke active session tokens while leaving the underlying cloud license and data containers intact under a formal litigation hold so a certified forensic examiner can create a verified bit for bit image and cloud export.

What a Device Shows After an Unplanned Boot

The call often comes after the helpdesk has already logged into a returned laptop, and the first question is what the device still holds. Usually a great deal, and the changes the boot made are specific. Booting a Windows machine into the user's profile updates registry hives, writes new prefetch entries, rolls event logs and may trigger an update or an indexing pass that changes file access timestamps. On a solid state drive, the boot can also prompt TRIM to release blocks that deleted files occupied, so the examiner turns to cloud copies and sync logs for those files. What remains is substantial: the user's documents, browser history, USB device history in the registry, LNK files and jump lists that show which files were opened, cloud sync client logs and the event logs that survived.

After an uncontrolled boot, the record is where the examiner looks for what the departing employee opened, copied and connected in the weeks before departure, and the technician's session is accounted for in every timeline. We identify the technician's logon, the duration of that session and every artifact it touched, and we exclude or annotate those entries so a timeline presented to a court assigns the helpdesk's activity to the helpdesk and the custodian's activity to the custodian. That accounting prepares the report for the cross examination question about who was logged in.

After reprovisioning, the examination moves to the cloud accounts, backups and server logs, which the examiner preserves in place of the reimaged laptop. OneDrive and Google Drive activity logs, Microsoft 365 audit records of downloads and sharing, and email records are held apart from the device when the account was placed on hold. Our trade secret and departing employee forensics page describes the device and cloud sources that are correlated in these matters and why both are needed. Where the device has been reissued, the cloud record is where the examiner looks for the answer to the original question.

The Trade Secret Statute Rewards Reasonable Measures

The Defend Trade Secrets Act defines a trade secret in part by the owner's conduct. Information qualifies only if “the owner thereof has taken reasonable measures to keep such information secret” (18 U.S.C. 1839(3)), and the civil remedy in 18 U.S.C. 1836 depends on that definition. A company that documents how it controlled access to its designs or customer data, and preserves the record of what the departing employee took, has evidence on both elements. The offboarding record is evidence on both: the access controls that were in place and the forensic preservation that shows what left.

Preservation also protects the employer on the other side of the same dispute. When a departing employee later alleges wrongful termination or retaliation, or when a new employer is accused of receiving trade secrets, the employer's own conduct in handling the departed employee's devices and accounts is examined. A documented quarantine, a hash verified image and a cloud export made before any administrator reviewed the content are evidence that the employer preserved the record whole and as found. Under Rule 37(e), the question is whether reasonable steps were taken, and a written preservation gate is the clearest answer.

The statute and the rule together make the point that preservation is a legal position rather than an IT task. We encourage general counsel to write the preservation gate into the offboarding procedure itself, so HR's notice of a sensitive departure triggers quarantine and hold automatically rather than depending on someone remembering to call legal. Our guide to common digital evidence mistakes lists the situations this gate is designed for, and most of them are procedural rather than technical. A procedure written once and followed every time costs less than a single spoliation motion, and it is the evidence of reasonable steps a company will want to show.

The Preservation Engagement, Step by Step

The first phase is quarantine and hold, and it happens before we arrive. Returned devices are bagged, labeled with the date, custodian and the name of the person who received them, and stored powered off. Mobile devices go into airplane mode or a shielded container so they stay isolated from remote wipe commands. Accounts are suspended, with sessions revoked and credentials disabled, while the license, mailbox and cloud storage remain intact under a litigation hold. We walk administrators through those steps on the first call because each one closes a path by which evidence changes.

Imaging and export follow. Laptops are imaged bit for bit through a write blocker or, where the drive is encrypted, through a documented live acquisition with the recovery key from the endpoint management console, and every image is hashed and verified. Phones are acquired through full file system or logical extraction depending on the model, or remotely through our supported collection link when the device is with the custodian, a process that usually runs from a few minutes to overnight depending on setup. Cloud mailboxes and drives are exported in native format with their audit records. Each step is recorded in a chain of custody log.

Analysis is scoped to the legal question at hand. A departure matter usually begins with the final weeks of USB connections, cloud uploads, personal email forwarding, large file access and application installs, correlated across the device image and the cloud audit record. We report findings with the artifacts that support each, and we note which sources cover each period. The computer forensics page describes the laboratory process, and the digital forensics process guide explains how the engagement moves from preservation to report. Findings are reported in writing at the end of the first phase so counsel can decide whether to expand the scope or conclude.

Who Acts Before the First Call

Human resources holds the trigger. The moment a departure, termination or internal complaint involves someone with access to sensitive information, HR should notify legal and IT together, before the exit interview if possible, so the preservation gate opens before the employee's last session. HR also holds the signed acceptable use policy and device agreements that establish the company's right to examine its own equipment, and those documents should be located and preserved with the devices, because the other side will ask for them early. A standing checklist for sensitive departures keeps the notice from depending on any one person's memory.

IT holds the devices and the accounts. The instruction is simple and often counterintuitive: keep the laptop powered off, keep the phone as it is, keep the account, and keep the license active. Suspend sign in, revoke sessions, change the password to one no one knows, place the mailbox and drive on hold, pull the BitLocker or FileVault recovery key from the management console and record it with the device, and stop any automated reprovisioning job that is scheduled to run. Endpoint management consoles often show the device's last check in and location, which should be captured before the device is enrolled elsewhere.

Legal holds the decision. Counsel decides whether the matter warrants imaging, which custodians are in scope, and whether the analysis proceeds under a litigation hold with the expectation of a report or testimony. The legal team also directs the engagement so the examiner's work is performed at its request, and it manages communication with the departed employee and any new employer. Our expert witness page describes how the preserved record becomes a declaration or testimony when the dispute proceeds. Early legal direction also keeps the examiner's work product structured for the deliverable the matter will eventually need, whether that is a letter to the new employer or a declaration in support of an injunction.

Immediate Action Checklist Before Touching a Returned Device

If a suspicious departure or internal dispute is unfolding right now, instruct your IT staff to stop all laptop reprovisioning, gather the device BitLocker or FileVault recovery keys from your endpoint management console and isolate any returned mobile devices in Airplane Mode. Read our guide to the five digital evidence mistakes to avoid, or call Global Digital Forensics 24/7 at (800) 868-8189 to coordinate rapid, defensible device and cloud preservation. The initial consultation is free.

What an Unplanned Boot Leaves in Place

Many calls come after a technician has already signed into a returned laptop. This table lists the artifact families an examiner looks for in a departure matter, whether each tends to persist through an uncontrolled boot, what it can establish and where the examiner looks next. It complements the narrative above by showing how much a booted device still holds, and why the cloud record is read alongside it. The second column describes a tendency, which the examiner confirms on the image.

Artifact families on a returned Windows laptop, their resilience to an uncontrolled boot and the corroborating source for each.
Artifact familyAfter a helpdesk bootWhat it can establishWhere the examiner looks next
USB device history in the registryUsually survivesA device with a given serial was connected and when it was first and last seenFile system artifacts for any copy to the device
LNK files and jump listsSurvive, with new entries from the technicianWhich files and folders were opened from which profileLogon records and badge data for the person at the keyboard
Browser history and downloadsUsually survivesPersonal webmail, cloud upload pages and downloadsThe service's own log for the content uploaded
Windows event logsMay roll with new entriesLogon sessions, service installs, device eventsForwarded or exported logs for earlier periods
Prefetch and application execution recordsSurvive, with new entries addedPrograms run, including wiping and archive toolsFile system and journal records for each affected file
Deleted files on a solid state driveOften released by TRIM after bootRecovered content from blocks still allocatedCloud copies and backups for released blocks
Cloud sync client logsUsually surviveFiles synced, shared or removed from OneDrive or DriveThe provider's audit records for other accounts
Cloud audit recordsUnaffected by the deviceDownloads, sharing and sign ins for an account placed on holdSecondary copies in a SIEM or archive for earlier periods

The drug diversion case study describes examiners creating forensically sound copies of seized drives under documented acquisition and handling procedures, the same chain of custody discipline this guide asks of a returned device.

How to Begin and What Happens on the First Call

Our Preservation Checklist: Quarantine the Device, Hold the Account sets out the items to secure in the order they expire. Have ready the custodian's name and role, the date of departure or notice, the devices issued and their current location and state, the cloud accounts involved, whether any device has been booted or wiped, and whether a hold has issued. The examiner asks what the concern is, what the employee had access to, what has already happened to the devices and accounts, who the administrators are and whether counsel is directing the matter. You receive immediate preservation instructions for IT and a written proposal naming the devices and accounts to be preserved, the acquisition method for each, the questions the analysis will address and the timing factors, including whether remote phone collection is available. The initial consultation is free. Call (800) 868-8189 at any hour.

Technical References and Further Reading

Related GDF pages for this work: legal hold technical support.

Primary sources and provider documentation behind this guide: NIST SP 800-86 and NIST SP 800-101 Revision 1.

Authorities cited in this guide: 18 U.S.C. 1839, Definitions (Defend Trade Secrets Act). Supplies the reasonable measures element of the trade secret definition quoted in the guide, current text at Cornell LII. Federal Rule of Civil Procedure 37(e). Sets the reasonable steps standard for preservation of electronically stored information, current text at Cornell LII. NIST SP 800-86, Guide to Integrating Forensic Techniques into Incident Response. Establishes the collection, examination, analysis and reporting structure the preservation engagement follows, final publication August 2006. NIST SP 800-101 Revision 1, Guidelines on Mobile Device Forensics. Establishes the isolation and acquisition practices for mobile devices described in the engagement steps, Revision 1 published May 2014.