The shift board. Every incident here is a graded case with a real simulated estate behind it — open one and the topology, findings and rubric are waiting.
3
Active incidents
1
Contained
2
Queued
6
Hands-on cases open
43
Graded cases available
The customer portal was compromised through an upload bypass at 01:12, the portal service account reached the finance database, and 1.4GB left the building. Work the box, prove the breach, contain what the evidence implicates, then write the post-incident record.
Playbook: Breach crossing a segment boundary · 9 findings · 22 graded rules
An IIS application server took an unrestricted upload at 02:47, the app-pool identity reached the order file server over SMB, and a 3.1GB archive is leaving right now. Work the box with cmd.exe, prove all three phases, then contain what the evidence implicates.
Playbook: Breach crossing a segment boundary · 9 findings · 22 graded rules
Audit finding NW-AUD-114 says nobody can demonstrate the corporate VLAN is separated from the server farm, the DMZ and the internet. You get a seat on an ordinary endpoint and nothing else, so prove the design from the wire, including the endpoint holding a session it should not have.
Playbook: Segmentation assurance · 8 findings · 20 graded rules
An access switch learned a hardware address that appears in no inventory. From a seat on the same VLAN, sweep the subnet, fingerprint the service the device publishes, and prove which rule keeps it away from the file shares. Then find the corporate endpoint already routing through it.
Playbook: Rogue device on a corporate VLAN · 8 findings · 20 graded rules
Three firewall migrations later, nobody can say which rules exist, and change control will not approve the next one without evidence. You get an ordinary corporate seat, no console and no exported config. Probe each zone crossing until the rule base identifies itself by number.
Playbook: Segmentation assurance · 8 findings · 19 graded rules
Overnight the perimeter logged unusual SMTP from the published web host into the server farm, then outbound TLS from an application server. You get a shell on that server, so work out which DMZ host reached it, which rule carried the data out, and which file server was touched.
Playbook: Breach crossing a segment boundary · 8 findings · 20 graded rules