Topics In Demand
Notification
New

No notification found.

Blog
Part 2: Securing IoT with Public Key Infrastructure (PKI)

August 20, 2020

IOT

168

0

[Note: This is the second part of the Securing IoT Series from Hughes Systique. To view the first part of the 3 part blog series please click here.]

Traditional PKI (Public Key Infrastructure) systems, with their reliability and effectiveness, have been successful in securing the IT ecosystem till date. It also makes them an inevitable candidate for securing the IoT ecosystem as well. Many existing IoT ecosystems are using PKI for achieving the CIA as it enables an organization to establish and maintain a trustworthy digital ecosystem (people, systems, and things) by managing keys and certificates.

The CIA Triad to Security Design

Any effective IoT security solution should meet the requirements put forth by the information security policy, i.e. the CIA triad:

Confidentiality: Prevent information access to unauthorized parties

Integrity: Preserve consistency, accuracy and trustworthiness of the data

Availability: Access to the intended item is ensured at all times

It serves two purposes. First, it can be utilized as a model for building security measures, and second, it warrants that important areas of security are covered.

The CIA security triangle is an important security concept because all security controls, mechanisms, and safeguards are implemented to provide one or more of protection types. All risks, threats, and vulnerabilities are measured for their potential capability to compromise one or all of the CIA triad principles.

Working Towards Hardened Security

Having said that, since PKI has become an integral part of IoT security, we need to be very cautious for situations in IoT where the lifetime of devices maybe for a longer duration, they may be running legacy apps with minimal or no upgrades. Apart from the hardened security and guiding principles, the IoT PKI needs to have some additional qualities while designing IoT security to fully serve the purpose in the IoT landscape:

Flexibility

  • Since PKI involves certificates, how easy it is to execute the change of ownership?
  • How much work does it require to change the PKI root of trust or certificates?

Customizability

  • The requirements of IoT devices may vary drastically. There may be devices in the same network, which need lifetime certificates, whereas some may require short-lived certificates which ultimately leads to another question, does my PKI allow such customizations easily?

Cost-Effective

  • How much do we have to shell out for these certificates?

Ease-of-use

  • Having deployed the PKI, how much effort do we need to put in for skilling my users?
  • Are the certificates managed automatically or need human intervention?

A good IoT security solution will tend to improve the experience, by giving the appropriate tuning knobs in the hands of the user, at the same time automating the mundane operations. Protecting critical information along network connections is crucial and challenging. PKI did emerge as a viable option when applications were processed on centralized servers. But, as the industry is moving towards distributed processing, the need for a new approach has become evident. The goal is to create an ecosystem where the concept of easy generation and rotation of certificates is encouraged and trust is decentralized through the use of technologies that make it possible for geographically disparate entities to reach consensus on the state of a shared database.

References:

https://www.difenda.com/blog/what-is-the-cia-triangle-and-why-is-it-important-for-cybersecurity-management

https://www.weboftrust.info/downloads/dpki.pdf

{This blog was originally published at here}


That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.


HughesSystique

© Copyright nasscom. All Rights Reserved.