Patent Description:
It is the object of the present invention to provide a very efficient way of identifying any security threats for IoT devices.

This object is solved by the subject matter of the independent claims, which define the scope of protection.

Briefly stated, the disclosed technology is generally directed to device security in an IoT environment. For example, such technology is usable in IoT security. In one example of the technology, a set of security rules that are associated with an expected condition of at least one IoT device is stored. IoT data associated with the at least one IoT device is received. The IoT data may be aggregated data that includes at least two different types of data. A determination is made, based on the IoT data, as to whether the set of security rules has been violated. An alert is selectively sent based on the determination.

Some examples of the disclosure include a system to monitor, detect and mitigate security threats to IoT devices using telemetry about the IoT device security state, and using other environmental data from other IoT devices. In some examples, telemetry data from multiple IoT devices in the environment is used, and a model of the environment is formed. In some examples, the resulting model is used to detect security threats such as intrusions and tampering.

Other aspects of and applications for the disclosed technology will be appreciated upon reading and understanding the attached figures and description.

Non-limiting and non-exhaustive examples of the present disclosure are described with reference to the following drawings. In the drawings, like reference numerals refer to like parts throughout the various figures unless otherwise specified. These drawings are not necessarily drawn to scale.

For a better understanding of the present disclosure, reference will be made to the following Detailed Description, which is to be read in association with the accompanying drawings, in which:.

The following description provides specific details for a thorough understanding of, and enabling description for, various examples of the technology. One skilled in the art will understand that the technology may be practiced without many of these details. In some instances, well-known structures and functions have not been shown or described in detail to avoid unnecessarily obscuring the description of examples of the technology. It is intended that the terminology used in this disclosure be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain examples of the technology. Although certain terms may be emphasized below, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section. Throughout the specification and claims, the following terms take at least the meanings explicitly associated herein, unless the context dictates otherwise. The meanings identified below do not necessarily limit the terms, but merely provide illustrative examples for the terms. For example, each of the terms "based on" and "based upon" is not exclusive, and is equivalent to the term "based, at least in part, on", and includes the option of being based on additional factors, some of which may not be described herein. As another example, the term "via" is not exclusive, and is equivalent to the term "via, at least in part", and includes the option of being via additional factors, some of which may not be described herein. The meaning of "in" includes "in" and "on. " The phrase "in one embodiment," or "in one example," as used herein does not necessarily refer to the same embodiment or example, although it may. Use of particular textual numeric designators does not imply the existence of lesser-valued numerical designators. For example, reciting "a widget selected from the group consisting of a third foo and a fourth bar" would not itself imply that there are at least three foo, nor that there are at least four bar, elements. References in the singular are made merely for clarity of reading and include plural references unless plural references are specifically excluded. The term "or" is an inclusive "or" operator unless specifically indicated otherwise. For example, the phrases "A or B" means "A, B, or A and B. " As used herein, the terms "component" and "system" are intended to encompass hardware, software, or various combinations of hardware and software. Thus, for example, a system or component may be a process, a process executing on a computing device, the computing device, or a portion thereof. The term "IoT hub" is not limited to one particular type of IoT service, but refers to the device to which the IoT device communicates, after provisioning, for at least one IoT solution or IoT service of any type. That is, the term "IoT hub," as used throughout the specification and the claims, is generic to any IoT solution.

Briefly stated, the disclosed technology is generally directed to device security in an IoT environment. For example, such technology is usable in IoT security. In one example of the technology, a set of security rules that is associated with an expected condition of at least one IoT device is stored. IoT data associated with the at least one IoT device is received. The IoT data may be aggregated data that includes at least two different types of data. A determination is made, based on the IoT data, as to whether the set of security rules has been violated. An alert is selectively sent based on the determination.

In some applications, IoT devices tend to be deployed remotely, potentially in adverse environments. Frequently such devices may not be physically accessible to the operators or owners to the device. Such devices may also be "in the wild" so that they are unattended and physically available to the public with no physical monitoring. physical supervision, or physical security, and thus people may be able to physically tamper with the devices. It may be possible for someone to transfer malware to such a device, steal a certificate from such a device, or the like. Examples of the disclosure monitor the security of the devices, detect intrusions and/or threats to the device, and/or communicate such intrusions and/or threats to a remote party, e.g., a system or operator who might be able to mitigate the intrusion and/or threat.

Some examples of the disclosure include a system to monitor, detect, and/or mitigate security threats to IoT devices using telemetry information about the IoT device security state, using telemetry data, and using other environmental data from other IoT devices. In some examples, data collection agents are deployed on IoT devices, and the sensor data generated by such IoT devices is used to model and detect security threats to the IoT devices. These data collection agents may be configured remotely using configuration data.

In some examples, multiple agents on various IoT devices can be used to collect various types of data which can then be used conjuctively to form a more holistic model of device operation, and intrusion. In some examples, agent data from the IoT device itself is used to report the security state of the IoT device. In some examples, agent data from a collection of devices is used to form a model of the operating environment. In some examples, telemetry data from multiple IoT devices in the environment is used and a model of the environment is formed.

In some examples, the resulting model is used to detect security threats such as intrusions and/or tampering.

<FIG> is a diagram of environment <NUM> in which aspects of the technology may be practiced. As shown, environment <NUM> includes computing devices <NUM>, as well as network nodes <NUM>, connected via network <NUM>. Even though particular components of environment <NUM> are shown in <FIG>, in other examples, environment <NUM> can also include additional and/or different components. For example, in certain examples, the environment <NUM> can also include network storage devices, maintenance managers, and/or other suitable components (not shown). Computing devices <NUM> shown in <FIG> may be in various locations, including on premise, in the cloud, or the like. For example, computer devices <NUM> may be on the client side, on the server side, or the like.

As shown in <FIG>, network <NUM> can include one or more network nodes <NUM> that interconnect multiple computing devices <NUM>, and connect computing devices <NUM> to external network <NUM>, e.g., the Internet or an intranet. For example, network nodes <NUM> may include switches, routers, hubs, network controllers, or other network elements. In certain examples, computing devices <NUM> can be organized into racks, action zones, groups, sets, or other suitable divisions. For example, in the illustrated example, computing devices <NUM> are grouped into three host sets identified individually as first, second, and third host sets 112a-112c. In the illustrated example, each of host sets 112a-112c is operatively coupled to a corresponding network node 120a-120c, respectively, which are commonly referred to as "top-of-rack" or "TOR" network nodes. TOR network nodes 120a-120c can then be operatively coupled to additional network nodes <NUM> to form a computer network in a hierarchical, flat, mesh, or other suitable types of topology that allows communications between computing devices <NUM> and external network <NUM>. In other examples, multiple host sets 112a-112c may share a single network node <NUM>. Computing devices <NUM> may be virtually any type of general- or specific-purpose computing device. For example, these computing devices may be user devices such as desktop computers, laptop computers, tablet computers, display devices, cameras, printers, or smartphones. However, in a data center environment, these computing devices may be server devices such as application server computers, virtual computing host computers, or file server computers. Moreover, computing devices <NUM> may be individually configured to provide computing, storage, and/or other suitable computing services.

In some examples, one or more of the computing devices <NUM> is an IoT device, a gateway device, a device that comprises part or all of an IoT hub, a device comprising part or all of a device portal service, or the like, as discussed in greater detail below.

<FIG> is a diagram illustrating one example of computing device <NUM> in which aspects of the technology may be practiced. Computing device <NUM> may be virtually any type of general- or specific-purpose computing device. For example, computing device <NUM> may be a user device such as a desktop computer, a laptop computer, a tablet computer, a display device, a camera, a printer, or a smartphone. Likewise, computing device <NUM> may also be server device such as an application server computer, a virtual computing host computer, or a file server computer, e.g., computing device <NUM> may be an example of computing device <NUM> or network node <NUM> of <FIG>. Computing device <NUM> may also be an IoT device that connects to a network to receive IoT services. Likewise, computer device <NUM> may be an example any of the devices illustrated in or referred to in <FIG>, as discussed in greater detail below. As illustrated in <FIG>, computing device <NUM> includes processing circuit <NUM>, operating memory <NUM>, memory controller <NUM>, data storage memory <NUM>, input interface <NUM>, output interface <NUM>, and network adapter <NUM>. Each of these afore-listed components of computing device <NUM> includes at least one hardware element.

Computing device <NUM> includes at least one processing circuit <NUM> configured to execute instructions, such as instructions for implementing the herein-described workloads, processes, or technology. Processing circuit <NUM> may include a microprocessor, a microcontroller, a graphics processor, a coprocessor, a field-programmable gate array, a programmable logic device, a signal processor, or any other circuit suitable for processing data. The aforementioned instructions, along with other data (e.g., datasets, metadata, operating system instructions, etc.), may be stored in operating memory <NUM> during run-time of computing device <NUM>. Operating memory <NUM> may also include any of a variety of data storage devices/components, such as volatile memories, semi-volatile memories, random access memories, static memories, caches, buffers, or other media used to store run-time information. In one example, operating memory <NUM> does not retain information when computing device <NUM> is powered off. Rather, computing device <NUM> may be configured to transfer instructions from a non-volatile data storage component (e.g., data storage component <NUM>) to operating memory <NUM> as part of a booting or other loading process.

Operating memory <NUM> may include <NUM>th generation double data rate (DDR4) memory, <NUM>rd generation double data rate (DDR3) memory, other dynamic random access memory (DRAM), High Bandwidth Memory (HBM), Hybrid Memory Cube memory, 3D-stacked memory, static random access memory (SRAM), or other memory, and such memory may comprise one or more memory circuits integrated onto a DIMM, SIMM, SODIMM, or other packaging. Such operating memory modules or devices may be organized according to channels, ranks, and banks. For example, operating memory devices may be coupled to processing circuit <NUM> via memory controller <NUM> in channels. One example of computing device <NUM> may include one or two DIMMs per channel, with one or two ranks per channel. Operating memory within a rank may operate with a shared clock, and shared address and command bus. Also, an operating memory device may be organized into several banks where a bank can be thought of as an array addressed by row and column. Based on such an organization of operating memory, physical addresses within the operating memory may be referred to by a tuple of channel, rank, bank, row, and column.

Despite the above-discussion, operating memory <NUM> specifically does not include or encompass communications media, any communications medium, or any signals per se.

Memory controller <NUM> is configured to interface processing circuit <NUM> to operating memory <NUM>. For example, memory controller <NUM> may be configured to interface commands, addresses, and data between operating memory <NUM> and processing circuit <NUM>. Memory controller <NUM> may also be configured to abstract or otherwise manage certain aspects of memory management from or for processing circuit <NUM>. Although memory controller <NUM> is illustrated as single memory controller separate from processing circuit <NUM>, in other examples, multiple memory controllers may be employed, memory controller(s) may be integrated with operating memory <NUM>, or the like. Further, memory controller(s) may be integrated into processing circuit <NUM>. These and other variations are possible.

In computing device <NUM>, data storage memory <NUM>, input interface <NUM>, output interface <NUM>, and network adapter <NUM> are interfaced to processing circuit <NUM> by bus <NUM>. Although, <FIG> illustrates bus <NUM> as a single passive bus, other configurations, such as a collection of buses, a collection of point to point links, an input/output controller, a bridge, other interface circuitry, or any collection thereof may also be suitably employed for interfacing data storage memory <NUM>, input interface <NUM>, output interface <NUM>, or network adapter <NUM> to processing circuit <NUM>.

In computing device <NUM>, data storage memory <NUM> is employed for long-term non-volatile data storage. Data storage memory <NUM> may include any of a variety of non-volatile data storage devices/components, such as non-volatile memories, disks, disk drives, hard drives, solid-state drives, or any other media that can be used for the non-volatile storage of information. However, data storage memory <NUM> specifically does not include or encompass communications media, any communications medium, or any signals per se. In contrast to operating memory <NUM>, data storage memory <NUM> is employed by computing device <NUM> for non-volatile long-term data storage, instead of for run-time data storage.

Also, computing device <NUM> may include or be coupled to any type of processor-readable media such as processor-readable storage media (e.g., operating memory <NUM> and data storage memory <NUM>) and communication media (e.g., communication signals and radio waves). While the term processor-readable storage media includes operating memory <NUM> and data storage memory <NUM>, the term "processor-readable storage media," throughout the specification and the claims whether used in the singular or the plural, is defined herein so that the term "processor-readable storage media" specifically excludes and does not encompass communications media, any communications medium, or any signals per se. However, the term "processor-readable storage media" does encompass processor cache, Random Access Memory (RAM), register memory, and/or the like.

Computing device <NUM> also includes input interface <NUM>, which may be configured to enable computing device <NUM> to receive input from users or from other devices. In addition, computing device <NUM> includes output interface <NUM>, which may be configured to provide output from computing device <NUM>. In one example, output interface <NUM> includes a frame buffer, graphics processor, graphics processor or accelerator, and is configured to render displays for presentation on a separate visual display device (such as a monitor, projector, virtual computing client computer, etc.). In another example, output interface <NUM> includes a visual display device and is configured to render and present displays for viewing.

In the illustrated example, computing device <NUM> is configured to communicate with other computing devices or entities via network adapter <NUM>. Network adapter <NUM> may include a wired network adapter, e.g., an Ethernet adapter, a Token Ring adapter, or a Digital Subscriber Line (DSL) adapter. Network adapter <NUM> may also include a wireless network adapter, for example, a Wi-Fi adapter, a Bluetooth adapter, a ZigBee adapter, a Long Term Evolution (LTE) adapter, or a <NUM> adapter.

Although computing device <NUM> is illustrated with certain components configured in a particular arrangement, these components and arrangement are merely one example of a computing device in which the technology may be employed. In other examples, data storage memory <NUM>, input interface <NUM>, output interface <NUM>, or network adapter <NUM> may be directly coupled to processing circuit <NUM>, or be coupled to processing circuit <NUM> via an input/output controller, a bridge, or other interface circuitry. Other variations of the technology are possible.

Some examples of computing device <NUM> include at least one memory (e.g., operating memory <NUM>) adapted to store run-time data and at least one processor (e.g., processing unit <NUM>) that is respectively adapted to execute processor-executable code that, in response to execution, enables computing device <NUM> to perform actions. In some examples, computing device <NUM> is enabled to perform actions such as the actions in the process of <FIG> or <FIG> below, or actions in a process performed by one or more of the computing devices in <FIG> below.

<FIG> is a block diagram illustrating an example of a system (<NUM>) for IoT communications. System <NUM> may include network <NUM>, IoT hub <NUM>, IoT devices <NUM>-<NUM>, gateway devices <NUM> and <NUM>, and device portal service <NUM>, which all connect to network <NUM>. As previously discussed, the term "IoT hub" is not limited to one particular type of IoT service, but refers to the device to which the IoT device communicates, after provisioning, for at least one IoT solution or IoT service of any type. That is, the term "IoT hub," as used throughout the specification and the claims, is generic to any IoT solution. The term "IoT device" refers to a device that makes use of, or is intended to make use of, IoT services. An IoT device can include virtually any device that connects to the cloud to use IoT services, including for telemetry collection or any other purpose. Device portal service <NUM> includes one or more devices that provide a device portal. The term "IoT hub" refers to a device, or multiple devices such as a distributed system, to which IoT devices connect via the network for IoT services.

Each of the IoT devices <NUM>-<NUM>, gateway devices <NUM> and <NUM>, and/or the devices that comprise IoT hub <NUM> and/or device portal service <NUM> may include examples of computing device <NUM> of <FIG>. <FIG> and the corresponding description of <FIG> in the specification illustrates an example system for illustrative purposes that does not limit the scope of the disclosure.

Network <NUM> may include one or more computer networks, including wired and/or wireless networks, where each network may be, for example, a wireless network, local area network (LAN), a wide-area network (WAN), and/or a global network such as the Internet. On an interconnected set of LANs, including those based on differing architectures and protocols, a router acts as a link between LANs, enabling messages to be sent from one to another. Also, communication links within LANs typically include twisted wire pair or coaxial cable, while communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including T1, T2, T3, and T4, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art. Furthermore, remote computers and other related electronic devices could be remotely connected to either LANs or WANs via a modem and temporary telephone link. In essence, network <NUM> includes any communication method by which information may travel between IoT hub <NUM>, IoT devices <NUM>-<NUM>, gateway devices <NUM>-<NUM>, and device portal service <NUM>.

As one example, IoT devices <NUM>-<NUM> are devices that are intended to make use of IoT services provided by one or more IoT hubs, such as IoT hub <NUM>. Device portal service <NUM> includes a device or multiple devices that perform actions in providing a device portal to users of IoT devices.

Optional gateway devices <NUM> and <NUM> are devices that may be used by some of the IoT devices <NUM>-<NUM> for accessing IoT hub <NUM>. In some examples, after provisioning, some or all of the IoT devices <NUM>-<NUM> communicate to IoT hub <NUM> without using an intermediary. In other examples, some or all of the IoT devices <NUM>-<NUM> communicate with IoT hub <NUM> using an intermediary device such as one or more of gateway devices <NUM> and <NUM>. Device portal service <NUM> is a service which may be used by users of IoT devices to manage IoT services for IoT devices including IoT devices <NUM>-<NUM>.

System <NUM> may include more or less devices than illustrated in <FIG>, which is shown by way of example only.

For clarity, the processes described herein are described in terms of operations performed in particular sequences by particular devices or components of a system. However, it is noted that other processes are not limited to the stated sequences, devices, or components. For example, certain acts may be performed in different sequences, in parallel, omitted, or may be supplemented by additional acts or features, whether or not such sequences, parallelisms, acts, or features are described herein. Likewise, any of the technology described in this disclosure may be incorporated into the described processes or other processes, whether or not that technology is specifically described in conjunction with a process. The disclosed processes may also be performed on or by other devices, components, or systems, whether or not such devices, components, or systems are described herein. These processes may also be embodied in a variety of ways. For example, they may be embodied on an article of manufacture, e.g., as processor-readable instructions stored in a processor-readable storage medium or be performed as a computer-implemented process. As an alternate example, these processes may be encoded as processor-executable instructions and transmitted via a communications medium.

<FIG> is a diagram illustrating an example dataflow for a process (<NUM>) for IoT authentication. <FIG> and the corresponding description of <FIG> in the specification illustrate an example process for illustrative purposes that do not limit the scope of the disclosure.

In the illustrated example, first, step <NUM> occurs. At step <NUM>, IoT hub <NUM> stores a set of security rules that is associated with an expected condition of at least one IoT device (e.g., IoT device <NUM>). In some examples, the set of security rules is based upon an assessment of IoT data associated with at least one IoT device (e.g., IoT device <NUM>). The set of security rules stored may differ, for example, based on the type of IoT device, upon the particular deployment context, and other factors. The set of security rules is discussed in greater detail below (after the discussion of the IoT data collected at step <NUM> below).

As shown, step <NUM> occurs next in some examples. In step <NUM>, a configuration request may be generated by device portal service <NUM> and then the configuration request may be communicated from device portal service <NUM> to IoT hub <NUM>. The configuration request may be associated with adjusting the set of security rules stored in IoT hub <NUM>. In some examples, the configuration request is a request to change a set of security rules to an adjusted set of security rules. The configuration request can be made in different ways in different examples. In some examples, there is a basic mode in which the default set of security rules is used, and there is also an advanced setting where the user can make a configuration request to change default set of security rules. As shown, step <NUM> occurs next in some examples. At step <NUM>, IoT hub <NUM> may adjust the set of security rules stored in IoT hub <NUM> based on the configuration request received from device portal service <NUM> at step <NUM>.

As shown, step <NUM> occurs next in some examples. At step <NUM>, IoT device <NUM> receives and collects environmental data from the environment, e.g., the environment in the vicinity of IoT device <NUM>, and collects data about the internal security state of IoT device <NUM>. The environmental data may include telemetry data, data indicating whether or not IoT device <NUM> has been physically tampered with, and/or the like. The telemetry data may include temperature, humidity, occupancy of a location associated with the IoT device, geolocation, and/or the like. The data about the internal security state of IoT device <NUM> may include operating system (OS) version, current state of the active processes, open ports, internet protocol (IP) addresses of devices connected, and/or the like. The data may be collected via software inputs, hardware inputs, or both.

The telemetry data collected at step <NUM> may include telemetry that the IoT device already collects in some examples. For example, an IoT device that is a temperature sensor may already be configured to collect temperature data.

IoT device <NUM> may have one or more tampering switches that detect physical tampering. In one example, the tampering switch is off if IoT device <NUM> has not been physically tampered with, and the tampering switch is on if IoT device <NUM> has been physically tampered with. The environmental data may include an indication as to whether the tampering switch is on or off. For instance, in some examples, IoT device <NUM> has a cover that is connected to two tampering switches. If the cover is opened, both tampering switches turn on.

In some examples, IoT device <NUM> may include a software agent that collects the environmental data and the data about the internal security of IoT device <NUM>. In some examples, IoT device <NUM> has a software data collection agent deployed on IoT device <NUM> to collect environmental and/or internal state data. In some examples, some or all of the IoT devices have a software data collection agent deployed on the IoT device to collect environmental and/or internal state data from the IoT devices.

The set of security rules stored in IoT hub <NUM> is based on a model of the normal behavior of the IoT devices (e.g., <NUM> and/or <NUM>-<NUM> of <FIG>). This model may represent the state of the IoT devices while these devices are working under normal conditions. In some examples, the set of security rules acts as a configurable IoT device model. The set of rules may be defined such that the set of rules is violated if an attack or other security intrusion or security threat occurs.

For example, the IoT devices may be subject to various types of security attacks which may be classified into two categories: cyber attacks and physical attacks. Cyber-attacks include attacks on the cyber properties of the devices, such as on the operating system, network infrastructure, connection, and data. Physical attacks include attacks such as physical tampering of the devices, manipulation of data generation elements of the devices, relocation, and the like. In some examples, the set of security rules is generated or adjusted such that violation of the set of security rules indicates at least a possibility of an attack (e.g., a physical attack or a cyber attack) on one or more IoT devices. Accordingly, once any of these attacks occur, a violation of the set of rules should occur in one example since the data collected from the devices will then be contrary to the model. The model may include one or more patterns for the telemetry data.

Accordingly, the set of security rules may define normal operating conditions which, if not met, may indicate the possibility of a security threat. For example, the set of security rules may be violated if one or more of the data elements is outside of an expected range. For example, the set of security rules may require that temperature is in a certain range, that the tampering switch is off, that certain blacklisted processes are not running, and/or the like. Expected ranges or expected discrete values may be contingent upon time of day and other factors. In some examples, rather than simply comparing each type of data such as temperature or the like to an expected range (or expected discrete value) individually, the set of security rules are based on multiple types of data considered together, based on a model. For instance, in some examples, temperature in the environment above the expected range might not result in a violation of the security rules unless there is also occupancy in the environment.

In some examples, the set of security rules are based on a model of the environmental and internal security data collected by the IoT devices, where the model effectively provides a "golden" image of the expected data. The golden image may reflect normal behavior of the IoT devices in normal operating conditions absent any intrusion or security threat. If, based on the received IoT data, some aspects differ from the golden image, the set of rules might be considered to be violated depending on other data. For instance, accordingly to the golden image for an occupancy sensor of a particular room in the mall, the occupancy sensor should not show occupancy during certain hours in which no one is expected to be present in the mall. However, the rules may specify that, for example, if the mall gate is open and the guard is still present in the mall, then the occupancy at the unexpected time does not trigger a violation of the set of security rules. In some examples, data from multiple IoT devices may be involved in the model and set of security rules in order to determine whether or not the set of rules have been violated. By using data from multiple IoT devices, a more holistic model of device operation and operating environment and intrusion may be used than if the model were based upon one IoT device.

In some examples, the set of security rules include one or both of a whitelist of processes and a blacklist of processes. The whitelist and blacklist of processes may be useful in determining whether or not an IoT device has been infected by malware. A "whitelist" of process refers to a list of approved processes, and a "blacklist" of processes refers to a list of prohibited processes.

In some examples, the collected IoT data, including collected telemetry data, can be used to assist in constructing the model in order to create or adjust the set of security rules.

As shown, step <NUM> occurs next in some examples. At step <NUM>, IoT device <NUM> may make a determination as to whether or not to send data to IoT hub <NUM>. In some examples, at step <NUM>, IoT device <NUM> simply determines to always send all of the data to IoT hub <NUM>. In some examples, data is only sent upon a threshold based on one of more of the types of data being exceeded.

For instance, in some examples, IoT device <NUM> makes a determination to send temperature data only if the temperature detected is outside of a predetermined range, such as <NUM>-<NUM> degrees Fahrenheit. In some examples, the fact that the temperature is outside of the range of <NUM>-<NUM> degrees Fahrenheit is not in and of itself a violation of the security rules-IoT device <NUM> does not make the determination about whether or not the set of security rules are violated, in this example, but only sends temperature data upon temperature being outside of a particular range, and for which therefore there might be a violation of the set of security rules depending on other factors.

As shown, step <NUM> occurs next in some examples when the determination at step <NUM> is positive. At step <NUM>, the IoT data may be communicated from IoT device <NUM> to IoT hub <NUM>. If, in contrast, the determination at step <NUM> is negative, other processing is resumed.

As shown, step <NUM> occurs next after step <NUM> in some examples. At step <NUM>, IoT hub <NUM> makes a determination, based on the IoT data received at step <NUM>, as to whether the set of security rules stored in IoT hub <NUM> has been violated. In some examples, the determination at step <NUM> is a comparison of the aggregated IoT device data with the configurable IoT device model.

As shown, step <NUM> occurs next in some examples. At step <NUM>, IoT hub <NUM> selectively sends an alert to device portal service <NUM> based on the determination at step <NUM>. If at step <NUM> it was determined that the set of rules were violated, IoT hub <NUM> communicates an alert to device portal service <NUM>. If instead at step <NUM> it was determined that the set of rules were not violated, IoT hub <NUM> does not send out an alert.

If IoT device <NUM> becomes disconnected from the cloud, data cannot be collected from IoT device <NUM>, but the fact that IoT device <NUM> is disconnected from the cloud is itself a form of information and in some examples an alert may result from IoT device <NUM> being disconnected from the cloud.

In some examples, the set of security rules may be further adjusted over time, both to reduce false positives, and to successfully detect attacks that might otherwise not be detected. In some examples, IoT hub <NUM> includes a learning layer that learns from anomalies and adapts by changing the set of security rules over time and learning over time.

In some examples, rather than sending the IoT data directly to IoT hub <NUM>, IoT device <NUM> sends the data to a gateway device (e.g., gateway device <NUM> or <NUM> of <FIG>). In some examples, the gateway device, rather than IoT device <NUM>, makes the determination as to whether or not to send the IoT data to IoT hub <NUM>. In some examples, multiple different IoT devices (e.g., <NUM>-<NUM> of <FIG>) send IoT data to one gateway device, which aggregates the data before determining whether and which IoT data to send on to IoT hub <NUM>.

In some examples, at step <NUM>, rather than simply sending out an alert, other details, including, for example, information about the nature of the attack or threat, as far as can be determined, is also communicated from IoT hub <NUM> to device portal service <NUM> along with the alert. For example, if IoT hub <NUM> determines both through GPS that a device has been moved and from other IoT data that malware has been installed, then the nature of this attack can be communicated from IoT hub <NUM> to device portal service <NUM>, which is potentially a different scenario than if only one of these two events had occurred. Aggregate data from multiple IoT devices can also be used, when applicable, to further describe the nature of the security threat in a communication from IoT hub <NUM> to device portal service <NUM>.

<FIG> is a logical flow diagram illustrating an example of a process (<NUM>) for IoT authentication. In one example, process <NUM> is performed by an IoT hub, such as IoT hub <NUM> of <FIG>. After a start block, the process proceeds to block <NUM>. At block <NUM>, a set of security rules that is associated with an expected condition of at least one IoT device is stored. The process then moves to block <NUM>. At block <NUM>, IoT data associated with the at least one IoT device is received. The IoT data may be aggregated data that includes at least two different types of data. The process then proceeds to decision block <NUM>.

At decision block <NUM>, a determination is made, based on the IoT data, as to whether the set of security rules has been violated. If the determination at decision block <NUM> is negative, the process proceeds a return block, where other processing is resumed. If, instead the determination at decision block <NUM> is positive, the process advances to block <NUM>, where an alert is sent. For instance, in some examples, the alert is sent a device portal service. The process then proceeds to a return block, where other processing is resumed. In this way, an alert is selectively sent based on the determination at decision block <NUM>.

Claim 1:
A system for Internet of Things, loT, security, comprising at least one IoT device (<NUM>) and an IoT hub (<NUM>), wherein:
each IoT device (<NUM>) of the at least one IoT device (<NUM>) comprises means for:
receiving and collecting environmental data from the environment and collecting internal security state data of the IoT device (<NUM>), wherein the data is aggregated IoT data including at least two different types of data;
making a determination as to whether or not to send each of the at least two different types of data to the IoT hub (<NUM>), wherein the determination to send for each of the at least two types data is made based on whether the each of the at least two types of data is outside of a predetermined range;
when the determination is positive, communicating the at least two different types of IoT data to the IoT hub (<NUM>); and
the IoT hub (<NUM>) comprises means for:
storing (<NUM>) a set of security rules that are associated with an expected condition of the at least one IoT device (<NUM>), wherein the set of security rules stored in IoT hub (<NUM>) is based on a model of the normal behavior of the at least one IoT device (<NUM>) representing the state of the at least one IoT device (<NUM>) while working under normal conditions and the set of rules is defined such that the set of rules is violated if an attack or other security intrusion or security threat occurs, wherein the set of security rules are based on multiple types of data considered together such that the fact that one type of data is outside of the predetermined range does not in and of itself result in a violation of the security rules;
receiving the IoT data (<NUM>) associated with the at least one IoT device (<NUM>);
making a determination, based on the IoT data and on the set of security rules, as to whether the set of security rules has been violated (<NUM>); and
selectively sending an alert (<NUM>) based on the determination.