What does “Jitsuin Archivist” look like?

The start-up Jitsuin has developed a tool called “Jitsuin Archivist” based on Distributed Ledger Technology (DLT). The purpose of this tool is to know “Who did what to a Thing and When”.

As of today, 5 types of users can interact with the tool: Archivist Administrator, System Administrator, Maintenance Operator, Auditor, Custom (currently in beta version).

Figure 1 – The 5 user roles of “Jitsuin Archivist”

On this tool the user has access to the “Security Twins” of the connected devices. Indeed, after logging in, the user accesses a dashboard through which he has a global view of all the connected devices linked to the tool. He can see relevant statistics related to his IoT deployment, such as the number of critical incidents, the activity of connected objects, etc.

The user can also access the “Manage Assets” page where he will find a map with the location of all the connected objects linked to the tool and a list of them (where he can also see in more detail the events linked to a particular connected device).

Figure 2 – The different views of the tool “Jitsuin Archivist”: 1. dashboard with a global view, 2. all the objects and their location, 3. detailed view of an object, 4. all the actions of the object useful during security audits

The PoC: A House with a digital lock

Wavestone used Jitsuin’s tool to first address the issue of identity and access management in buildings in at the dawn of digital transformation and the to illustrate the usefulness of “Security Twins”.

To do this Wavestone used the lego house “SmartHouse” :

Figure 3 – The “SmartHouse”

Equipped with an RFID card reader, a Raspberry Pi microcontroller and a servomotor, the entrance door of the “SmartHouse” only opens to users who have an authorized access card. All actions related to opening, closing, granting of entry rights, etc. are recorded on “Jitsuin Archivist” (see figure 4).

Figure 4 – The functional diagram of the “SmartHouse”

In order to facilitate the interaction with the digital lock of the “SmartHouse”, a platform allowing the simulation of different operations made by different peopled involved in the life cycle of connected devices has been created using the Django web framework and Bootstrap. This platform allows, among other things, to:

• Send security patches to the connected lock (using Azure IoTHub)
• Assign access rights to the “SmartHouse”
• View the history of access rights requests made and those awaiting validation, etc.

This is what the platform looks like:

Figure 5 – SmartHouse’s management platform

The use of “Jitsuin Archivist” in this PoC is very interesting when regards to security audits of connected devices. Indeed, as “Jitsuin Archivist” is based on Distributed Ledger Technology (DLT), this system can be considered as “secure by design” since an auditor has a technical guarantee on the non-compromise of data (provided that the sending of this data is secure).

Here is the “Auditor View” on “Jitsuin Archivist” where it is possible to see all the information regarding the connected devices linked to the platform and to know who has done what to the connected device:

Figure 6 – The “Auditor View” of “Jitsuin Archivist”

The PoC scenario: WaveHouse rents “SmartHouses” in France …

Here is the general architecture of the PoC:

Figure 7 – The general architecture of the PoC

As one can see, the digital lock (represented by the RFID card reader, the Raspberry Pi microcontroller and the servomotor) interacts with Azure IoTHub as well to facilitate the management of its firmware updates.

The main use cases studied by Wavestone and Jitsuin

The main use cases studied by Wavestone and Jitsuin are explained in the video below:

Conclusion

Wavestone and Jitsuin were able to demonstrate – with the different use cases illustrated above in the video – how to improve the security of connected devices:

• First of all, all of the people involved in the life cycle of the digital lock of the “SmartHouse” had access to its “Security Twin”. Indeed, each of them had access to a decentralized and unchangeable register provided by “Jitsuin Archivist” with all the information regarding the security of the digital lock.
• Then, as mentioned above, this architecture is “secure by design” because as “Jitsuin Archivist” is based on Distributed Ledger Technology (DLT), one has a technical guarantee on the non-compromising of data.
• The “Security Twin” of the digital lock ensured physical security since it had the rights management information, allowing all the people involved to know who had access to the “SmartHouse”.
• Finally, since the “Security Twin” also had firmware information, the different people involved could easily know which connected devices had vulnerabilities and quickly plan the distribution of security patches.

The “Security Twins” would therefore ultimately improve the security of the connected devices, since it would be easy to know which objects are secure and which are not.

Cet article “Security Twins”: A new security & trust guarantee for connected devices (2/2) est apparu en premier sur RiskInsight.

Despite their usefulness, introducing connected devices unfortunately brings new risks for companies. Indeed, according to the Palo Alto Networks report² published in March 2020, 57% of the connected devices analyzed were vulnerable to medium or high severity attacks. This is not surprising. Securing connected devices is proving to be an arduous task that explains why Beecham Research³ finds 62% of Industrial IoT transformations fail to scale because of a lack of trust.

Therefore, with this article we will try to ask ourselves about the security and trust issues of connected devices and how companies can deal with them.

What are the security and trust issues of connected devices?

In order to mitigate the security risks on connected devices, NIST recommends in its report⁴ published in 2019 to focus on 6 main areas:

• Inventory: Maintain an accurate inventory of all connected devices and their most relevant characteristics throughout their lifecycle (see the article detailing the lifecycle of connected devices).

Figure 1 – Connected device lifecycle

• Vulnerabilities: Identify and eliminate known vulnerabilities in the software and firmware of connected devices to reduce the likelihood and ease of exploitation and compromise.
• Access: Prevent unauthorized and inappropriate physical and logical access, use and administration of connected devices by people, processes and other computing devices.
• Detect security incidents of connected devices: Monitor and analyze connected device activity for signs of incidents involving the security of the device.
• Detect data security incidents: Monitor and analyze the activity of the connected device for signs of data security incidents.
• Protect data: Prevent access and alteration of data that could expose sensitive information or allow manipulation or disruption of the operation of connected devices.

However, current IoT platforms only partially meet these security requirements (see the article detailing the usefulness of IoT platforms).

Figure 2 – The usefulness of IoT platforms

Indeed, traditional IoT architectures rely on a centralized cloud platform, operated by a third-party company and where most often the rules for data collection and storage are opaque. This is not the best solution to ensure the security of connected devices since:

• The use of a centralized cloud platform introduces the risk of “single point of failure” on the IoT architecture (although today this risk is mitigated with the implementation of a redundant architecture and backups).
• It is entirely possible for an attacker to change the data stored in the cloud database. The decision making of the different stakeholders is therefore impacted.
• Collaboration between the different stakeholders of the IoT deployment (manufacturers, maintenance operators, …) becomes more difficult because access to the platform can be restricted to them.

The use of a decentralized management system for connected devices where all stakeholders would have the possibility to reliably consult or contribute information regarding connected devices (firmware version, maintenance operations, etc.) becomes essential to guarantee the security of those devices and the integrity of data they produce.

How do “Security Twins” help meet the security challenges of connected devices?

In order to support IoT platforms and improve the security of IoT deployments, the notion of  “Security Twin” should be introduced in IoT deployments.

The principle of a “Security Twin” is simple. It is a virtual representation of the connected device that contains all its security information, such as firmware version, vulnerabilities, etc. upon which all stakeholders involved in its upkeep can reach consensus (see figure 3).

Figure 3 – The “Security Twin” mechanism (from: Jitsuin)

A “Security Twin” gains effectiveness when more stakeholders of the deployment can interact with it and reach consensus that the information provided/recorded is correct.

Therefore, solutions based on Distributed Ledger Technology (DLT) represent a logical first step in the creation of Security Twins, as they would allow the security information of the connected device to be gathered in a decentralized and immutable registry that would be accessible by all authorized stakeholders in the IoT deployment. The best well known distributed registry solution is the Blockchain (see the article on Blockchain’s uses and limitations).

Taking up the points raised earlier in the NIST report, one could say that the use of a “Security Twin” would therefore improve:

• Device and access management: all stakeholders of the IoT deployment would have access to a decentralized and immutable register of all the connected devices with the corresponding security and trust information.
• Vulnerability management and the detection of device security incidents: the different stakeholders could share device security information and take the necessary actions (e.g. the manufacturer of a connected device could notify the other stakeholders of the availability of a new firmware update thanks to the “Security Twin”).
• Data protection and the detection of data related security incidents: The very foundation of a “Security Twin” is based on the use of a decentralized and immutable register to record data related to the security of connected devices. This makes it more difficult for attackers to change the data, which reduces the risk of a security incident.

The use of “Security Twins” therefore offers the possibility of strengthening the security, integrity, trust and resilience of connected devices.

The start-up Jitsuin has developed “Jitsuin Archivist” a tool based on Distributed Ledger Technology (DLT) to overcome the lack of collaborative tools to secure connected devices. The purpose of this tool is not to replace IoT platforms but to allow the creation of “Security Twins”.

Together, Wavestone and Jitsuin sought to demonstrate the benefits of using a decentralized architecture with “Security Twins”. The two companies have therefore collaborated on the construction of a PoC (Proof of Concept) to tackle identity and access management of buildings using connected devices, which will be introduced in a future article.

1 Gartner, 29th August 2019 : https://www.gartner.com/en/newsroom/press-releases/2019-08-29-gartner-says-5-8-billion-enterprise-and-automotive-io
2 Palo Alto Networks, 10th March 2020, “Unit 42 IoT threat report”: https://unit42.paloaltonetworks.com/iot-threat-report-2020/
3 Why IoT projects fail https://www.whyiotprojectsfail.com/?cs=br2
4 NIST – “Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks” : https://csrc.nist.gov/publications/detail/nistir/8228/final

Cet article “Security Twins”: A new security & trust guarantee for connected devices (1/2) est apparu en premier sur RiskInsight.