To mitigate non-essential IoT traffic, we propose a blocking system composed of two components: IoTrigger and IoTrimmer. The former runs our methodology to produce (non-)required destination lists, and the latter uses such lists with a blocking strategy to generate firewall traffic-blocking rules. IoTrigger runs on a router providing connectivity to a set of IoT devices to test. It manages the lifecycle of functionality experiments for each device, including the invocation of user-provided trigger and probe scripts, and to finally produce (non-)required destination lists. To work, IoTrigger needs the IoT devices connected to the same router, the list of their IP addresses, the scripts to trigger and probe their functions, and any other auxiliary devices (e.g., devices used by trigger/probes scripts). Given this, IoTrigger will run the experiment and generate the destinations lists without any human interaction. We implemented a command-line prototype of IoTrigger, which includes a library of probes and triggers scripts that support the IoT devices we tested. Anyone owning the same IoT devices, and the proper trigger devices (e.g., Android phones) can use the IoTrigger prototype to reproduce our results. For new devices and new functions, new trigger/probe scripts must be added.
HOW TO RUN THE SOFTWARE
The code needs Mon(IoT)r installed. Please download and install the software here: https://moniotrlab.ccis.neu.edu/tools/
Each subdirectory shows samples for running the functionality, getting destinations from the pcap files, classifying the destinations and blocking the functionality.
run_iotrigger.sh- Code for runnig IoTrigger.get_dest.sh- Code for running the functionality and getting the destinations.classify_dest.sh- Code for classifying the destinations.blocker.sh- Code for blocking the destinations and creating the IoTrim list.blocker_all.sh- Code for blocking all the destinations in a file. Useful for blocking all the essential/non-essential destinations and checking the IoTrim list correctness.blocker_manual.sh- Code guiding the user to the manual check of destinations. It blocks destinations one-by-one and asks the user to execute the action and give feedback on the result.trigger_function.sh- Code using the experiment file to execute the activity. The activities are logged to a log file.
The GUIDELINE.txt contains a full WALKTHROUGH on a how to set up a new device and use IoTrigger to extract the list of non-essential destinations from the new device.