Demos & Tutorials

Videos &
Demos

06
videos
available

5 min

Automatic Blocking

First demo of the IoTEdu Core MVP, walking through the platform's three access profiles. The superuser registers a unit (in this example, Unipampa Alegrete) and integrates it with the pfSense firewall and the intrusion detection systems. Next, a virtual machine allowed on the network launches a brute-force attack, which is detected and triggers the automatic blocking of the device until the administrator allows it again.

  • Unit registration and profile assignment by the superuser
  • Administrator dashboard with devices, incidents, and the Zeek, Suricata, and Snort IDS
  • Attack, automatic blocking, and device release
14 min

Complete Setup

Step-by-step tutorial for building an IoTEdu environment from scratch. The video presents the three-layer architecture (authentication via the CAFe Federation or Google, the central orchestrator, and the network layer with a firewall and intrusion detection sensors) and walks through the entire installation up to the registration of the first institution. At the end, it runs the full cycle of registration, approval, attack, and blocking, with an average blocking time of 5.56 seconds over 75 runs.

  • Solution architecture and the three access profiles
  • Configuring the database, the pfSense API, and the IDS
  • Automatic blocking in practice and the performance of each IDS
5 min

IoTEDU MVP Demo

A tour of the platform's beta version, populated with sample data to show every possible state. The video covers the home page, the redundant login (Google plus two in-house identity providers, so that the failure of one does not block access), and the screens for each profile: the superuser manages users and units, the administrator blocks and releases devices, and users keep track of their own devices.

  • Login with Google and redundant identity providers
  • Superuser and network administrator dashboards
  • The three device states: allowed, blocked, and pending approval
3 min

Quick Demo

A bench recording with real hardware: one laptop running the API, a support laptop acting as the attacking device, and two Raspberry Pis connected to Wi-Fi. The device is registered and allowed by the administrator, and when it attacks the network it loses access within seconds. The administrator then releases it and the connection comes back.

  • The automatic blocking cycle from start to finish
  • Vertical format (YouTube Shorts)