Each machine has a public IP address attached, as well as a hostname via GCP's DNS support set up for easier access. Students can either use remote desktop or SSH to access the machines and use the security tools we've set up for them. This year, we decided to move those Kali VMs to the cloud to simplify our setup. However, as more and more students use M1 Macs that don't support standard x86-64 virtualization, this solution started to become difficult to maintain. Previously, we used to give each student a Kali Linux virtual machine (VM) download preprovisioned with these tools. Why GCP? We need to provide students with tools for learning about cyber topics during lab sections such as Burp Suite, Wireshark, nmap, and others. This fall, I'm one of five TAs for the class, and I had the responsibility of building much of our course infrastructure on Google Cloud (GCP)'s Compute Engine before the quarter started.

Hack Lab's Google Cloud infrastructure Hack Lab is Stanford's introduction to cybersecurity, cyberlaw, and cyber policy class, with nearly 180 students enrolled. This blog post describes our course's infrastructure setup (including why we had that testing box in the first place), how we discovered and remediated the incident, and how we used the incident as a way to teach students about incident response and public disclosure.

This morning, an EternalBlue-vulnerable machine used for testing for Stanford's Hack Lab course accidentally given a public IP address on Google Cloud was unsurprisingly pwned and used to launch further EternalBlue scanning against other public web hosts.

Wireshark ip lab solutions