IIC Journal of Innovation 9th Edition | Page 70

IoT Trustworthiness is a Journey and NOT a Project The functional and technical evolution of the system may affect its trustworthiness requirements - Corporate mandates and roadmaps may change direction and pace - M&A activities may impact strategies and priorities The current trustworthiness levels may fluctuate over time - Normally, this level starts at a point below the required level - As trustworthiness-focused methods and processes are deployed, this level will rise - Organizations may need to raise the level of trustworthiness again later in the lifecycle due to future changes in the requirements - The current levels of trustworthiness may decay over time, due to system and human errors, lapses, cyberattacks, malicious activities, etc. - During the decommissioning stage, additional requirements may arise; example, how to decommission a nuclear facility and how to handle hazardous materials -  I O T T RUSTWORTHINESS S TATES The previous section has highlighted the importance of maintaining a system lifecycle perspective about IoT Trustworthiness. The path that trustworthiness should take during the lifecycle (red line in Figure 2) is planned/charted based on considerations such as:  Required levels of IoT Trustworthiness and the timeframes for compliance with them,  Corporate objectives and roadmaps,  Risk management considerations,  Budgetary and Return on Investment (ROI) considerations  and many others. In general, trustworthiness has three milestone states: Figure 3: The states of IoT Trustworthiness Current State This is the actual “trustworthiness” status of an IoT system, based on the system as it is currently designed, implemented and operating:  Current state of safety processes September 2018 - 65 -