Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 36 ยท Projects and Practice

Digital Forensics Practice Questions

Test your digital forensics knowledge with scenario questions on network, log, mobile, cloud and timeline analysis, plus hands-on exercises and a self-review checklist.

This final lesson is for practice. You will work through short scenarios, answer review questions that mix every topic of this chapter range, and try a few small exercises. There are no new concepts; the goal is to see whether you can apply what you know, explain your reasoning and notice what the evidence does not show.

Try each scenario by writing down your answer first, then compare it with the notes.

Scenario 1: The noisy scanner

A web access log shows 600 requests from one address in two minutes, nearly all 404, hitting paths like /admin, /.git/config and /wp-login.php. There is one 200 for / and no POST requests.

Questions: Is this an intrusion? What would change your mind? What do you record?

Notes: This looks like automated scanning with no evidence of success. It becomes more serious if later requests from the same address return 200 for sensitive paths, if POST requests follow, or if sizes show downloads. Record the address, the time range, the count and the response code distribution, and the logs you did not have (web logs).

Scenario 2: The late-night login

auth.log shows five failed SSH logins for deploy from 203.0.113.9, then Accepted publickey for deploy from the same address, at 03:12. The deploy user normally logs in from 198.51.100.4. Then a sudo entry runs /bin/bash.

Questions: What is the likely sequence? What alternative explanations exist? What do you collect next?

Notes: The five failures were password attempts, but the success was by public key, which means failures and success may be unrelated, or a key was added or stolen. Alternatives: the engineer traveled; a CI system moved. Collect: when the key was added to authorized_keys (file times), other logins by that key, the shell history, and process activity (authentication logs).

Scenario 3: The phone export

A messaging app database has message IDs 1..400 but only 350 rows, and a deleted column set on 12 rows that still show text.

Questions: What explains the missing 50 and the 12 flagged rows? How do you check?

Notes: The flagged rows are soft deleted. The 50 gaps may be rows removed, or IDs that were never used. Check the WAL, freelist pages and other tables, and look for app clean-up (VACUUM) (SQLite analysis).

Scenario 4: The cloud key

CloudTrail shows CreateAccessKey for admin-svc by build-bot, then StopLogging, then 400 GetObject calls, all from a new address.

Questions: What does this sequence suggest? What is preserved first? What would you ask the owner?

Notes: It suggests a compromised credential and an attempt to hide it. Preserve the logs and snapshots before rotating keys; verify with the owner whether build-bot normally creates keys; check what the 400 objects were and whether data left the network (cloud forensics).

Exercise: Rank suspicious addresses

Write a small program that scores addresses. Add a rule of your own and explain it.

Python Exercise: score the addresses

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Check your rule against the data: 198.51.100.4 should stay on top and its lead should grow, matching the intuition that a success after failures is more worrying than a scan.

Exercise: Convert timestamps

A phone export has three timestamps: a Unix-millisecond value, a Cocoa value and a WebKit value. Convert them and confirm they refer to the same minute.

Python Exercise: epoch conversions

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Exercise: Spot the weak statement

Rewrite each as a fact, inference or opinion with its support:

  1. "The employee deleted the evidence."
  2. "The server was hacked at 14:03."
  3. "The IP address proves who did it."

Hint: Replace each with what the data shows (time, source, account) and add a confidence word plus what else you would need (report writing).

Mixed review questions

Quick check ยท 10 questions

of 10 answered You scored / 10 ยท perfect!

  1. 1. Which source is smallest and best for finding who talked to whom over months?

    Flows summarize connections without payloads, so long retention is practical.
  2. 2. A pcap record header is how many bytes?

    Each record has a 16-byte header: seconds, microseconds, captured length, original length.
  3. 3. What is the strongest sign of guessed credentials in a web log?

    Failures followed by success on an authentication endpoint is the classic pattern.
  4. 4. Which Windows event records a cleared audit log?

    Event 1102 means the audit log was cleared.
  5. 5. Why do you copy the -wal file with a SQLite database?

    The write-ahead log can contain committed and sometimes deleted data.
  6. 6. What is the first thing to do with a running seized phone?

    Isolation prevents remote wipe and new data; documentation records the state at seizure.
  7. 7. In cloud investigations, why should you snapshot before terminating an instance?

    Ephemeral resources vanish; preserve first, then contain.
  8. 8. A file's modified time is earlier than its created time. Likely cause?

    A copy gets a new creation time while usually keeping the original modified time.
  9. 9. Which statement is a conclusion with appropriate caution?

    It states what the evidence supports without claiming identity.
  10. 10. What proves that evidence has not changed since acquisition?

    Matching hashes demonstrate integrity of the data.

Self-review checklist

Tick each one you could explain to a colleague without notes:

  • The sources of network evidence and what each can prove.
  • How to parse and explain a pcap, a web log and an SSH log.
  • What mobile acquisition types exist and why isolation matters.
  • How to read an app SQLite database safely.
  • How cloud audit logs identify actions and what to preserve first.
  • How to normalize time and build a timeline.
  • MACB times and the copy rule.
  • How to separate facts from opinions in a report.
  • What authority, privacy and admissibility require.

Summary

  • Practice means applying concepts to scenarios and explaining the reasoning.
  • Always name alternative explanations and the evidence that would separate them.
  • State what the evidence does not show.
  • Reuse your tools (log triage, manifest, timeline) on new synthetic data to build speed.

Next: back to the Digital Forensics track