Browser cyber range

Cyber labs without setup, VM, or cloud cost.

Boot as many lab machines as the scenario needs inside the browser. Students investigate real incidents without cloud ranges, backend graders, or install weeks.

5–10hsetup time saved per student
∞ runsrepeat polymorphic labs at no added server cost
$63k+modeled yearly savings for 100 students
shadow // defender
defender> tail -n 80 /var/log/web/access.log
10.0.0.210 POST /upload?name=cache-raven.phtml
10.0.0.210 GET  /cache/fragments/cache-raven.phtml?task=id

defender> checkwebshell
decoys intact  : yes
Lab status     : PASS
browser VMs hidden attacker real Linux console randomized every run

Why colleges care

Setup time, range fees, and hardware requirements compound fast.

$315kmodeled yearly savings for a 500-student program
0 serverssave cloud cost by shipping static files and browser VMs
polymorphicrepeat the same lab many times: IPs, filenames, commands, flags, and evidence change per run
alert tcp any any -> 10.0.0.10 80

IDS + firewall

BlueWall

Catch hostile traffic. Write the rule. Block only what matters.

Launch lab
/cache/fragments/shell.phtml?task=id

Webshell IR

ShadowShell

Follow logs, find the shell, preserve decoys, contain the attacker.

Launch lab
coming_soon --scenario malware-triage

More soon

Next labs

Malware triage, packet forensics, cloud security, AD-style attacks.

In progress
Full study: browser-native polymorphic labs lower cost click to expand

Executive summary

Browser-native polymorphic cyber labs can remove much of the setup, local VM, and cloud infrastructure burden from cybersecurity courses. Students open a webpage instead of installing hypervisors, importing VM images, debugging NAT networks, or waiting for a hosted range. Because lab values randomize across runs, the same scenario can be repeated for skill-building without turning into a static answer-sharing exercise.

5–10hsetup/debug time potentially saved per student
$180/yrexample hosted range category at $15/user/month
$1,500example cybersecurity laptop requirement from a college program
∞ runsrepeat labs with no added server cost per run

Methodology

The model combines five cost buckets: student setup time, TA/faculty support, hosted range/platform cost, cheating/rework, and hardware pressure. The numbers are intentionally transparent so a school can replace assumptions with its own rates.

Bucket Mid-case assumption Reason for including it
Student setup 8h saved × $20/hr Traditional VM labs often create install, import, patching, and network-debug time.
TA support 4h saved × $25/hr Less local setup means fewer environment-specific troubleshooting sessions.
Hosted range $180/student/year Example public cyber-range pricing includes a $15/user/month plan.
Answer sharing 2h/student equivalent at $70/hr Polymorphic IPs, filenames, commands, and flags reduce static-solution reuse.
Device pressure 10% avoid a $1,500 upgrade Browser labs reduce the need for high-RAM virtualization-capable student laptops.

Annual savings model

Program size Student setup TA support Hosted range Cheating/rework Device pressure Total saved Per student
100 students $16,000 $100 $18,000 $14,000 $15,000 $63,100 $631
500 students $80,000 $200 $90,000 $70,000 $75,000 $315,200 $630
2,000 students $320,000 $400 $360,000 $280,000 $300,000 $1,260,400 $630

Why polymorphism matters

Static labs are easy to overfit. Once a filename, IP, flag, or command sequence leaks, students can follow an answer key. A polymorphic lab changes evidence per run: attacker IPs, benign clients, shell names, route paths, command parameters, markers, persistence files, and flags. This makes repeat practice useful instead of repetitive.

Why browser-native matters

The lab is a static project: HTML, CSS, JavaScript, v86, BIOS/kernel/rootfs images, and scripts. That means the same lab can be hosted from a normal website and repeated without spinning up a new cloud VM for every learner.

Pricing and ROI strategy

A future product could be priced well below the modeled value delivered. For example, a $10–$20/student/month range is still small compared with the modeled savings, especially when setup time and hardware pressure are included. Institutional pricing could also work as a flat program license for departments. These numbers should be refined after vendor-by-vendor pricing research.

Source links

This is draft positioning, not a public pricing claim. Vendor-by-vendor research should happen before publishing exact comparison numbers.