Part 3 (and final part) of our series focusing on best practices and pitfalls to avoid to secure connected products and processes with an IoT platform for identity.

What are the top 5 most difficult technology aspects of security and identity for IoT?

  1. No single established standard for device identity management
  2. Inadequacy of traditional IAM models (too person-centric, static) to encompass non-carbon entities and dynamic relationships
  3. Management of connectivity, data and authentication across organization and network boundaries
  4. Heterogeneous networks (bandwidth, latency, coverage)
  5. Multiplicity of IoT standards (MQTT, AMQP, CoAP, etc.) exacerbated by overlapping industry alliances

What are the top 3 best practices when implementing security and identity for IoT?

  1. Ensure that identity and access capabilities can be enforced autonomously, even when the device is disconnected
  2. Understand the dynamic nature of identity-driven relationships among IoT devices
  3. Allow application of different policies to the same IoT devices depending on context (time, space)

What are the top 3 pitfalls to avoid when implementing security and identity for IoT?

  1. Rely too much on IoT device capabilities (e.g. X509 certificate)
  2. Assume uninterrupted access and connectivity to IoT devices
  3. Expect and apply the same capabilities as traditional IAM

What are the top 5 guidelines that Covisint sees its customers use?

  1. Ability to scale
  2. Standards support
  3. Proven track record (years of existence, number and size of customers)
  4. Ability to bridge agile and legacy systems, cloud and on-premise systems
  5. Ease of administration

Recommendation: IoT platforms are accelerators of IoT adoption. They are designed to offer core capabilities enabling developers to more quickly and efficiently build, deploy and manage connected applications and focus on creating the business logic that will differentiate their connected products and connected processes.

By providing special-purpose services, consistent operating environments and standards-based frameworks, IoT platforms allow for the rapid implementation of proof of concepts (POC) for concept validation and for the iterative roll out of new software-based solutions for ongoing market fit.

Users of IoT Platforms should take a fit for purpose approach and select the platform(s) that best suit their needs and offer the maximum level of integratability and interoperability with other IoT systems. Most business IoT platforms will be a composite of several IoT technology platforms.

Users and buyers should particularly care about platform offerings that enable them to create and manage the digital ecosystems that constitute their connected products and connected processes and within which people, systems and things will produce, use, consume or store data.