Our challenge: IoT as the Internet of Trouble and why is important for the societyBotnets (networks of computers infected and repurposed for malicious activities) have existed for at least a decade. As early as 2000, hackers were breaking into computers all over the Internet...
Our challenge: IoT as the Internet of Trouble and why is important for the society
Botnets (networks of computers infected and repurposed for malicious activities) have existed for at least a decade. As early as 2000, hackers were breaking into computers all over the Internet and controlling them at large. Among other things, hackers used the combined computing power of these botnets to launch distributed denial-of-service (DDoS) attacks, which flood websites with traffic to take them down (attached figure).
But today the problem is getting worse, because of the abundance of cheap webcams, digital video recorders, baby monitors, smart thermostats, air quality sensors, and other gadgets in the Internet of Things (IoT). The arrival of IoT means that computers are now baked into everything from road signs & MRI scanners to prosthetics & insulin pumps .
Because these devices typically have little or no security, hackers can take them over with little effort. And that makes it easier than ever to build huge botnets that can do much more damage than taking down one website at a time.
Overall objectives
In this Phase 2 project, we will:
Develop INSTET, implement specific requirements from each of the three confirmed verticals & confirm them in the dedicated trials.
Ramp up commercialization activities in each of the three verticals and set the ground for the commercial launch of the complete INSTET solutions at the end of this Phase 2 project.
Update 15.01.2020
Explanation of the work carried out by the beneficiaries and Overview of the progress
1.1 Objectives
The main INSTET project objectives include:
•Objective 1: Develop INSTET to TRL9 and complete its industrialization;
•Objective 2: Finetune INSTET for each of the three key vertical segments;
•Objective 3: Prepare commercialization plans and other materials to launch INSTET to the market.
WP1
We have finalized the specific requirements from each of the three confirmed verticals (wearables, medical, critical infrastructures). This work is part of the “WP1 Security platform definition & platform selectionâ€.
We have released the following corresponding WP1 Deliverables (D):
• D1.1 and D1.2 Security Services Definition and IoT node selection for wearables and medical.
• D1.3 Security Services Definition and IoT node selection for critical infrastructures.
• D1.4 Report on security backend/could platforms selection and vertical.
Therefore, the status of the corresponding objectives related to WP1 is the following:
WP2
This periodic report is presenting the developments over the last 6 months namely, from 01/06/2019 to 30/11/2019. However, at the time of writing this report (January 2020), already we have finalized all the WP2 deliverables which have due date end of January 2020 according to the plan. Therefore, on the “WP2: Components Development for IoT†the developments are progressing as planned and the contributions are summarized on the following deliverables:
• D2.1 Report on Assess Security Design & Countermeasures for Secure Design (receipt date 31 Aug 2018). The scope of this document is to present a) our customized design approach towards fast and flexible software/hardware development for specific use cases, b) our methodology for secure integration towards system architecture, c) common attacks and how we could design for attack resistant blocks.
• D2.2 Report on methodology for customized design and fast integration (to be submitted by the end of January 2020). This is deliverable is focusing on hardware developments. The scope of this document is to present: a) the overview of our standard hardware IP product, namely QuiddiKey, b) New functionalities introduced and implemented in QuiddiKey, c) The performance improvement of QuiddiKey, d) The tools and simulation results of QuiddiKey, e) The introduction of Monark FPGA IP based on butterfly PUFs.
• D2.3 Report on IoT node security services & communication APIs (to be submitted by the end of January 2020). The scope of thi document is to report developments made to Intrinsic ID’s core software product, BroadKey.
• D2.4 Report on Assess Security Design & Countermeasures for Secure Design (to be submitted by the end of January 2020).
WP3
(It has been finalized in this reporting period and four deliverables have been released)
During this reporting period we have released the following corresponding WP3 deliverables:
o D3.1 Report on security architecture for wearables.
o D3.2 Report on security architecture for medical.
o D3.3 Report on security architecture for critical infrastructure.
o D3.4 Report on backend/cloud security design.
Work Package 4
On the “WP4: Integration, test & trials†the developments have started and are progressing as planned. The contributions are the following:
•We have developed Continuous Integration in order to cope the complexity of multiple software flavors (depending on the market segment and requirements) and multiple integration platforms (depending on the hardware platform of our customers). This activity gives us the opportunity for fast scalability beyond the three verticals that we have selected initially for the INSTET.
•We are building three main integrations and trials.
o On wearables: showing End-to-End Security and Secure boot.
o On medical: supporting with unclonable identities high-end devices. This activity supports the developments of our
The progress is presented in latest Technical report which includes the dissemination progress as well.
More info: https://www.intrinsic-id.com/sram-puf/collaborative-research-projects/instet-research-project/.