Disk Forensics Lab teaching notes

For high school cybersecurity, IT and CTE digital forensics teachers, forensic science electives, and NCL, CyberPatriot and CCST coaches. Two periods through the case, what each piece of evidence is built to show, what students get wrong and where the app answers it, what it leaves out, and how to take the USB stick's image to a real forensic tool.

Using this with a class? Make a free class and add your students yourself: each gets a username and password, with no email or Google account needed. Or give them one join code. Using Google Classroom? Post the link there; with a free class, the link also puts each student in your class, so you see their work. mytekDev is also available from the Google Workspace Marketplace, so your school's Google admin can install it for everyone.A first lesson: Open Examine on the laptop, click chores.txt in Documents and put the Picture or text tab on the projector. Ask the class what kind of file it is. It opens as gibberish, because its name says text. Then open the Bytes tab and read the first three bytes together, FF D8 FF, the signature of a JPEG photo.

Set up a free class Share to Google Classroom
Put this on your class site

Students can use Disk Forensics Lab right on your page, with no account. What they make stays on that page; to keep their work, they make a free account.

Google Sites: Insert, then Embed, then By URL, and paste this address.

https://mytekdev.com/try/diskforensicslab?embed=1

Canvas, a blog, or any page that takes HTML: paste this code where you edit the page as HTML.

<iframe src="https://mytekdev.com/try/diskforensicslab?embed=1" width="100%" height="640" style="border:0" allow="fullscreen" title="Disk Forensics Lab demo from mytekDev"></iframe>

About these notes

Disk Forensics Lab is one case and two pieces of evidence. Someone broke the school's trophy case overnight and took the cup, the case Crime Scene Lab works at the scene. One keyholder's laptop and the USB stick from their bag were taken with their consent and imaged, and the student is the examiner. They verify each copy's hash, examine the files, tag what matters, line the times up, and write the report.

Each project is its own case: the seed picks whose laptop it is (Avery, Morgan or Quinn, the three adult keyholders) and whether the files place the cup with the owner's phone after the break-in or date every cup photo to awards night, weeks before. Clearing someone is a real outcome of forensic work, and it keeps students from deciding the answer before they look.

Two periods

  1. The bench (5 minutes) Read a chain of custody card aloud: who collected the laptop, who imaged it, who handed the image to you. Press Verify the image on both items. Ask why nothing can be tagged until the hashes match.
  2. The renamed file (10 minutes) Examine, Documents, chores.txt. It opens as gibberish by its name. Open Bytes and read the first bytes against the signatures. In High school mode the student picks the type before the list will say it.
  3. The Recycle Bin (10 minutes) Open the user's bin. Each deleted file is a $R file with the content and a $I record with the original path and the time it was deleted, in UTC. Read the SSD card: why the laptop gives back only what is in the bin.
  4. The USB stick (15 minutes) _ROPHY.JPG is red, its first letter lost. Its Bytes tab shows the folder entry starting E5. Its Photo details give the position; High school converts it to decimals for the map. PHOTOS holds a dog photo half overwritten, and Free space holds three carved files. The Hash tab shows which carved file is the same as the stick's photo, and the Recycle Bin's.
  5. Timeline (5 minutes) Tag three or more files with a note each, then open Timeline. Ask why the camera time and the GPS time of one photo land on the same dot.
  6. Second period: the report, the copy, the questions Write the report and hand it in; the check holds students to "consistent with". Start a copy in a virtual machine and compare the owner's desktop with what the examiner saw. Competition teams switch the level to Competition (NCL style) for eight exact-answer questions.

What each piece of evidence is built to show

EvidenceWhereWhat it is built to show
The two hashesThe benchA copy is proved by its hash, taken when the drive was imaged and checked before work starts
chores.txtLaptop, DocumentsA file's type is in its first bytes, not its name. In one case it hides the cup; in the other it hides a birthday present, so a mismatch is a lead, not a finding
$R and $I filesLaptop, Recycle BinWhat Windows keeps when a file is deleted to the bin: the content, the original path and the deletion time
fair-flyer.pdfLaptop, DocumentsCreated after modified: what a copied file looks like, not tampering
The screenshotLaptop, PicturesNo EXIF at all, and that is normal
_ROPHY.JPGUSB stickA FAT deletion: E5 in the folder entry, first letter lost, data intact. Same SHA-256 as the photo in the laptop's bin
_OG.JPG and LIST.TXTUSB stick, PHOTOSA newer file took part of a deleted file's space: the picture is fine down to the gap
carved-1 to carved-3USB stick, Free spaceCarving finds content with no name, folder or file system times; dates inside the file, like EXIF, come with it
The cup photo's EXIFPhoto detailsCamera time has no zone, GPS time is UTC, the position is good to a few meters

What students get wrong, and where the app answers it

No study was found of what students in grades 6 to 12 believe about digital forensics. These are the beliefs teachers, practitioners and research on adults describe, and each is met in the case.

What students thinkWhere the app answers it
Deleted means goneThe stick's E5 entries and the carved photos
Deleted files can always be recoveredThe SSD card on the laptop: TRIM usually wipes a file deleted for good
Renaming a file changes what it ischores.txt, seen by its name and by its bytes
The investigator switches on the suspect's computer and looks aroundTurn on the original laptop changes its hash, and the report says so; the virtual machine copy is how an examiner sees the desktop
A hash proves who did itThe Hash tab and the report card: a match says the data is the same, nothing more
A photo's time and place are exactNo time zone in the camera time, a circle on the map, not a spot
Forensics proves guiltThe report check: "consistent with", and a line on what the evidence cannot say. Half the cases clear the owner

What the app simplifies, on purpose

Taking the USB stick to a real tool

On the bench, Download the image (64 MB) saves the stick exactly as the app examines it; its SHA-256 is the one on the card. On a Linux machine with Sleuth Kit, fls -r -p item2-usb-keys-NNNN.img lists every file with the deleted ones starred, and icat with a file's number recovers it. The same file opens in Autopsy. Each student's case has its own image.

Setting it up for a class

Grade level in the header: Middle school names the file types and converts the GPS position; High school has students read the bytes and convert it themselves; Competition (NCL style) adds eight questions with exact answers to the report.

Setup fixes whose laptop it is and what the files show, with an answer key that follows the choices. Changing it starts the work again. To give a whole class one case, set it in your own project and share that project for students to start from; the standalone page keeps its case in one browser only.

Big screen fills a projector and Esc leaves it. Start over clears a student's work and keeps the case. With a free account the work is saved as a project with a summary line for kits and grading.

Standards

The app addresses these; it does not cover all of any one.

More help

Is something on this page wrong or not clear? Write to us.

Page last reviewed November 2026.
Google, Google Classroom and Chromebook are trademarks of Google LLC.