Systems and methods for monitoring records in an Internet of Things (IoT) device registry for changes in device property data

Patent metadata

Field	Value
Publication number	US-12530698-B2
Application number	US-202217722167-A
Country	US
Kind code	B2
Filing date	Apr 15, 2022
Priority date	Apr 16, 2021
Publication date	Jan 20, 2026
Grant date	Jan 20, 2026

Abstract

An apparatus including a device property data processing circuit, a change detection circuit, an alert circuit, and an alert provisioning circuit. The device property data processing circuit is structured to at a first time, interpret, device property data corresponding to a device registered with an IoT device registry, and at a second time, interpret, the device property data corresponding to the device registered with the IoT device registry. The change detection circuit is structured to detect a change in the device property data between the first time and the second time. The alert circuit is structured to generate, responsive to the detected change, a message that identifies the device corresponding to the device property data. The alert provisioning circuit is structured to transmit the message.

First claim

What is claimed is:

1 . A method, comprising:
monitoring, via at least one processor, one or more records in an internet of things (IoT) device registry for changes in device property data corresponding to one or more devices, each of the one or more devices corresponding to one of the one or more records, each of the one or more records including an IoT UID assigned to the corresponding device, wherein the IoT UID is generated based at least in part on device property data derived from the corresponding device and comprises one or more hashes corresponding to a meta identity component, a service identity component, a network identity component, and a physical identity component; detecting, via the at least one processor, a change in the device property data of at least one record, wherein the change in the device property data is between a first value of the device property data at a first time and a second value of the device property data at a second time, and wherein the change corresponds to an outage pattern; determining, via the at least one processor, that the change corresponds to a security vulnerability; generating, via at least one processor and responsive to the determined security vulnerability, a message that identifies, based at least in part on the IoT UID, a device corresponding to the change in the device property data; and transmitting, via the at least one processor, the message.

2 . The method of claim 1 , further comprising displaying the message.

3 . The method of claim 1 , further comprising logging the change in a database.

4 . The method of claim 1 , further comprising receiving the message at a device management platform and at least one of quarantining or patching the device.

5 . The method of claim 1 , further comprising adjusting a trust indicator based at least in part on the change.

6 . The method of claim 5 , wherein the trust indicator is at least one of a trust score, a rating, or a level value.

7 . The method of claim 5 , wherein the adjusting is an increase when the change corresponds to a patching or an updating of software and/or firmware of the device.

8 . The method of claim 5 , wherein the adjusting is a decrease when the change corresponds to a vulnerability.

9 . The method of claim 1 , wherein the change corresponds to a change in ownership of the device.

10 . The method of claim 1 , wherein the change is a location of the device.

11 . The method of claim 1 , further comprising accessing a security vulnerabilities database to pull security vulnerability signatures to determine if a registered device is affected.

12 . The method of claim 1 , further comprising interpreting a device event message and updating the at least one record in the IoT device registry based at least in part on the device event message.

13 . The method of claim 1 , wherein the message indicates the identified device is a down device.

14 . The method of claim 13 , wherein the outage pattern spans a plurality of distinct entities, and the message further identifies one or more geographic locations corresponding to the plurality of distinct entities.

15 . An apparatus, comprising:
a device property data processing circuit structured to:
at a first time, interpret, device property data corresponding to a device registered with an IoT device registry and assigned an IoT UID generated based at least in part on device property data corresponding to the device, wherein the IoT UID comprises one or more hashes corresponding to a meta identity component, a service identity component, a network identity component, and a physical identity component; and
at a second time, interpret, the device property data corresponding to the device registered with the IoT device registry;
a change detection circuit structured to detect a change in the device property data between the first time and the second time, wherein the change in the device property data corresponds to an outage pattern; an alert circuit structured to generate, responsive to the detected change, a message that identifies, based at least in part on the IoT UID, the device corresponding to the device property data; and an alert provisioning circuit structured to transmit the message.

16 . The apparatus of claim 15 , wherein the device property data processing circuit is further structured to display the message.

17 . The apparatus of claim 15 , wherein the device property data processing circuit is further structured to receive the message at a device management platform and at least one:
of quarantine; or patch the device.

18 . The apparatus of claim 15 , wherein the device property data processing circuit is further structured to adjust a trust indicator based at least in part on the change.

19 . The apparatus of claim 15 , wherein the change corresponds to an addition of a new module into the device.

20 . A system, comprising:
a device management platform comprising one or more first processors structured to manage one or more devices registered with an IoT device registry, each of the one or more devices assigned an IoT UID generated based at least in part on device property data corresponding to device, wherein the IoT UID comprises one or more hashes corresponding to a meta identity component, a service identity component, a network identity component, and a physical identity component; and a sentry device comprising one or more second processors structured to:
monitor the IoT device registry for changes in property data corresponding to the registered one or more devices;
detect a change in the property data for at least one of the one or more devices, wherein the change in the device property data is between a first value of the device property data at a first time and a second value of the device property data at a second time, and wherein the change corresponds to an outage pattern;
determine that the detected change corresponds to a security vulnerability;
generate, responsive to the determined security vulnerability, a message that identifies the at least one device of the one or more devices based at least in part on the assigned IoT UID; and
transmit the message to the device management platform, wherein the one or more first processors are further structured to:
interpret the message transmitted by the one or more second processor; and at least one of:
quarantine the at least one device; or
patch the at least one device.

21 . The system of claim 20 , wherein the one or more second processors are further structured to:
receive the message at the device management platform; and at least one of quarantining or patching the one or more devices.

22 . The system of claim 20 , wherein the one or more second processors are further structured to adjust a trust indicator based at least in part on the change.

Assignees

• Somos Inc

Inventors

• Brazao Eduardo Correia Da Silva
• Brumer Steven Norman
• Klein Ian Michael
• Kong Li
• Plante Marc Rudloff
• Ramachandran Sridhar
• Shyu Kimberly Tashner
• Sliwa Robert Janusz
• Smith Jeffrey Scott
• Wendt Christopher Anton
• Yu Haofang

Classifications

• H04L67/12

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

• H04L63/126

  the source of the received data · CPC title

• H04L43/0817

  by checking functioning · CPC title

• H04L41/0813

  characterised by the conditions triggering a change of settings · CPC title

• H04L41/0806

  for initial configuration or provisioning, e.g. plug-and-play · CPC title