How ics-range-team/ics_range_v2 works
OT_RANGE_V2 is a lightweight, multi-zone operational-technology cyber range: it deploys two PLC stations, three FUXA SCADA instances, attacker and operator workstations, network routers, a mirrored-traffic sensor, a user portal, and a minimal 3D station viewer. The intended workflow spans operating the simulated stations and observing mirrored network traffic; the README documents the mirroring path but not the detailed control or data links between station services. SCADA capabilities are represented from the source tree and sampled modules; unsampled connections are omitted.
Main entry points: main.js SCADA Central · carto_client.py Kali Attacker · router1/app.py R1 Router · router2/app.py R2 Router
Components 17
OT Stations
- PLC-A Webserver
station_a/plc_a/webserver/webserver.py - PLC-B Webserver
station_b/plc_b/webserver/webserver.py
SCADA Systems
- SCADA-A
station_a/scada_a/server/main.js - SCADA-B
station_b/scada_b/server/main.js - SCADA Central
scada_central/server/main.js - SCADA Client
scada_central/client/src/app/editor/editor.component.ts - DAQ Storage
scada_central/server/runtime/storage/daqstorage.js - Alarm Storage
scada_central/server/runtime/alarms/alarmstorage.js
User Interfaces
- Kali Attacker
kali-attacker/carto_client.py - Engineering Workstation
- Station B 3D Viewer
viewer3d-station-b/backend/modbus_mapping.py
Range Management
- User Portal
portal/backend/server.js - Portal User Records
Other components
- Operator
Connections 9
- R1 Router → OT Sensor: mirrors traffic
- R2 Router → OT Sensor: mirrors traffic
- Operator → User Portal: manages users
- User Portal → Portal User Records: persists users
- Operator → SCADA Client: uses
- Kali Attacker → R1 Router: sends traffic
- Kali Attacker → R2 Router: sends traffic
- SCADA Central → DAQ Storage: stores DAQ data
- SCADA Central → Alarm Storage: stores alarms