bastion

Digital Forensics and Evidence Handling

Build this skill

Preserve digital evidence correctly, keep a chain of custody and build an incident timeline from mixed log sources.

The counter laptop is now a crime scene

When Neha reaches the Nashik Road store at 5:20 pm, Arjun already has the reinstall disc in his hand. For a normal fault his instinct would be right: wipe the laptop, reinstall the MedLedger billing software, open the counter again. Neha stops him, because the laptop is now the best witness Tulsi Health has to what happened. Digital forensics is the careful collection, protection and examination of digital traces so that they tell a reliable story about an incident, a story that holds up if an insurer, the police or a court asks questions later.

Think of a crime scene in a film. Police tape goes up, nobody moves the furniture, and a photographer records everything before anyone touches it, because moving one chair might destroy a footprint. Digital evidence is even more fragile than a footprint. Simply opening a file, restarting a computer or running a cleaning program changes what is stored, usually without leaving any visible sign that something changed.

What counts as digital evidence

Digital evidence is any information stored or sent in digital form that helps show what happened. In the Nashik Road case it includes the scrambled files and the ransom note on the laptop, the fake invoice email Arjun opened on Thursday, the logs (automatic diaries of activity) kept by the shared drive and the email service, records of who logged in from where, and the contents of the laptop's memory. Memory, often called RAM, is the computer's short-term working space. It holds the programs running right now and traces of recent activity, and it empties the moment the power goes off.

Evidence differs in how quickly it disappears, which investigators call its volatility. Some of it lasts only seconds, some lasts for years. The sensible order is to capture the most fragile evidence first, the way a crime scene photographer records footprints in the rain before the evidence that will still be there tomorrow.

Memory (RAM)lost when power goes offsecondsNetwork connectionschange every few secondssecondsFiles on the diskchange each time they are useddaysLogs on serversoverwritten after weeksweeksBackups and archiveskept for months or yearsyears

Collect from the top down. Switching the laptop off destroys the top two layers in an instant, which is why the cable comes out but the power stays on.

Preserve first, examine later

Evidence preservation means keeping evidence exactly as it was found. The first rule is to change the original as little as possible. That is why the laptop was unplugged from the network but left switched on: the missing cable stops the spread, while the power keeps the memory alive until someone trained can capture it. Neha photographs the screen with her phone and notes the time. She also saves copies of the shared-drive logs at once, because on Tulsi Health's settings those logs are automatically overwritten after 14 days.

Investigators never examine the original disk directly. They make a forensic image, an exact bit-for-bit copy of the whole disk, including areas where deleted files once sat, and they work only on copies of that image. To prove the copy matches the original and has not changed since, they calculate a hash of it: a short fingerprint worked out from every single bit of the data. Change even one letter anywhere and the fingerprint comes out completely different, so the same fingerprint on Monday and again months later shows the evidence was never altered.

Sort the actions below from Tulsi Health's first evening. Some of them protect what the laptop can tell you, and some quietly wipe it away even though they look helpful, so think about what each one changes.

Chain of custody: the sealed bag and its signature list

Evidence is only trusted if you can show where it was at every moment. Chain of custody is the written record of every hand-over: who took the item, when, from whom, why, and where it was kept. Picture a sealed evidence bag with a list printed on the front. Each person who takes the bag signs the list, writes the time and states the reason. A gap in that list, such as a weekend nobody can account for, lets someone argue that the evidence might have been changed, and that doubt alone can sink an insurance claim or a police case.

SEALED · EVIDENCE · DO NOT OPEN NR-1 counter laptop Item 1 · counter laptop NR-1 Seized Sat 17:20, Nashik Road Disk copy fingerprint (hash): 9c41 5be0 … 77d2 e07b Chain of custody Every hand-over, timed and signed When From → to Why Sat 17:20 Arjun → Neha taken from store Sat 19:05 Neha → office safe locked away Mon 10:30 Safe → forensic firm make disk copy Mon 15:40 Forensic firm → safe copy hash checked ! A gap in this list is a gap in the story

The seal shows nobody opened the bag; the list shows who held it and why. Together they let anyone later trust that the laptop examined is the laptop seized.

Building the incident timeline

An incident timeline places every relevant event, from every source, in time order. It turns scattered clues into a story: how the attacker got in, what they did and when, and how long they were inside before anyone noticed. Clocks need care here. Cloud services often record times in UTC, the world reference time, which is five and a half hours behind Indian Standard Time, and a laptop's own clock may be a few minutes wrong. A good timeline converts every entry to one time zone and notes any clock that was off, otherwise events appear in the wrong order.

The Nashik Road timeline changes the whole recovery plan. The fake invoice email was opened on Thursday morning, Arjun's password was used from an unknown computer late on Friday night while the store was shut, and the shared drive's folders were browsed minutes later. The red screen on Saturday afternoon was the end of the attack, not its start.

Attacker insideHidden for about 54 hoursNashik Road storeOpenOpenOpenNightly backupsCleanMay hold the malware0 h12 h24 h36 h48 h60 h72 hEmail openedNight loginFiles encrypted

Hour 0 is midnight on Thursday. The attacker was inside more than two days before anyone noticed, so only the backup taken before hour 11 can be trusted.

The log extract below mixes the attack with an ordinary weekend of work. Your job is to pick out the lines that belong on the incident timeline, the way Neha did on Sunday morning.

Notes someone else can follow

Forensic documentation is the written record of everything done during the investigation: what was found, what was done to it, by whom, at what exact time, with which tool, and why. Notes are written at the moment, not remembered later, and include photographs of screens and the hash of every copy made. The test of good notes is simple. Someone who was not there, reading them months later, should be able to repeat each step and get the same result.

Pulling these ideas together gives the basic forensic principles that apply whether the case is a stolen laptop or a ransomware attack:

  1. Change the original as little as possible, and capture the most fragile evidence first.
  2. Work only on verified copies, with a hash proving each copy matches.
  3. Document every action with time, person, tool and reason.
  4. Keep an unbroken chain of custody for every item.
  5. Stay within your authority. Examine only what the investigation needs, respect people's privacy, and bring in trained specialists when the stakes are high, before anything is wiped.

Follow your curiosity.

↑ ↓ to explore · Enter to open · Escape to close