# Water-Tight IoT-Just Add Security
## 2 Background  
### Related Work  
The H2020 STOP-IT project [1] presented a number of approaches for assessing and treating risk on the strategic and tactical level, as well as specific tools and technologies for cyber and physical protection of water infrastructures at the operational level. New methods and tools are embedded in the so-called STOP-IT Platform. The STOP-IT platform consists of different \"building blocks\" that can be used standalone or in combination with each other [2]. The platform allows users to choose technologies that are relevant to the specific challenges they face on a daily basis, while also having the opportunity to expand by adding more components at a later date. This facilitates improved protection against combined cyber-physical threats and analysis of cascading effects of physical and cyber incidents. The platform was validated in an operational environment, and all solutions have been demonstrated in real environments. The STOP-IT platform is structured into nine modules that bring together technological solutions and analysis tools:  
* Strategic and tactical tools are analytical tools designed to support managers and decision-makers in their efforts to increase preparedness against the impact of cyber-physical threats to the service to be delivered. They generate custom scenarios for attacks, assess risk in terms of service disruptions and calculate the effectiveness of risk mitigation measures to increase system resilience. * Operational tools support the real-time operation of the integrated system by providing a comprehensive list of technologies to detect anomalies of various natures, such as jamming, IT attacks, physical intrusion, abnormal activity, loss of data availability and integrity. The overall risk management method adopted by STOP-IT is inspired by the risk management procedure from ISO 31000 which consists of five steps: \"Establishing context\", \"Risk identification\", \"Risk analysis\", \"Risk evaluation\" and \"Risk treatment\". Compatibility with the standard is key for the STOP-IT framework to interact with existing procedures in the water sector. \"Establishing context\" is a prerequisite for a risk management plan, defining the scope of the risk management process, the main objectives of the tool and sets the criteria according to which the risk is to be assessed. \"Risk identification\" generates a comprehensive list of potential risk events that may affect a water supply system. In STOP-IT, this has resulted in the creation of a Risk Identification Database (RIDB) [3] which covers the identified risks at strategic, tactical and operational levels, and which is applied to the entire water system. The STOP-IT RIDB contains risk incidents involving physical and cyber threats. For each incident, RIDB describes the type of source of risk (e.g., external attacker, external contractor, human error, interdependent critical infrastructure, internal attacker); type of threat (physical and/or digital); type of event (destruction, interruption, manipulation); the specific element (physical or digital) where the source of risk arises (e.g., control center, control system, dosing system); in which part of the infrastructure the risk arises (e.g., catchment area, pipeline, drinking water reservoir, pumping station); the impact caused by the incident (financial, quality, quantity, reputation); and a brief description of the incident. The purpose of RIDB is not to replace the comprehensive identification of risk events for each water network operator. Instead, the examples from RIDB can allow users to start analysis and become aware of some possibilities that should be explored when local conditions develop that indicate that an event may occur. During the development of the RIDB, several meetings were held with each water network operator involved in the project. RIDB currently covers 81 incidents that have been identified as the most relevant. RIDB will be a live database that will be updated and reviewed regularly.