# US 2019/0173861 A1 · Sentinel appliance in an internet of things realm

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0173861 A1
- Document ID: US20190173861A1
- Status: Published application
- Kind: A1
- Application number: 16/273,353
- Filed: 2019-02-12
- Published: 2019-06-06
- Earliest claimed: 2015-06-10
- Assignees: McAfee, Inc.
- Applicants: McAfee, LLC
- Inventors: Ned M. Smith; Simon Hunt; Venkata Ramanan Sambandam
- Web page: https://patentgrep.com/patent/US20190173861A1

## CPC

- H04L 63/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)}
- H04L 9/0844: {with user authentication or key authentication, e.g. ElGamal, MTI, MQV-Menezes-Qu-Vanstone protocol or Diffie-Hellman protocols using implicitly-certified keys}
- H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)}
- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 63/02: {for separating internal from external traffic, e.g. firewalls}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

There is disclosed in one example a sentinel device, including: a hardware platform including at least a processor and configured to provide a trusted execution environment (TEE); and a security engine operable to instruct the hardware platform to: determine that an internet of things (IoT) device in a first realm R1 requires a secure communication channel with a second device in a second realm R2; query a key server for a service appliance key for the secure communication channel; establish a secure communication channel with the endpoint device using the service appliance key and the TEE; and provide a security service function within R1 including brokering communication via the secure communication channel between the IoT device and the second device.

## Claims

### Claim 1

A sentinel device, comprising:
a hardware platform comprising at least a processor and configured to provide a trusted execution environment (TEE); and
a security engine operable to instruct the hardware platform to:
determine that an internet of things (IoT) device in a first realm R1 requires a secure communication channel with a second device in a second realm R2;
query a key server for a service appliance key for the secure communication channel;
establish a secure communication channel with the endpoint device using the service appliance key and the TEE; and
provide a security service function within R1 comprising brokering communication via the secure communication channel between the IoT device and the second device.

### Claim 2 (depends on 1)

The sentinel device of claim 1, wherein the security engine is further operable to instruct the hardware platform to perform an attestation with the key server.

### Claim 3 (depends on 2)

The sentinel device of claim 2, wherein the attestation comprises attesting that the TEE conforms to a security requirement for R1.

### Claim 4 (depends on 2)

The sentinel device of claim 2, wherein the IoT device does not conform to the security requirement of R1.

### Claim 5 (depends on 2)

The sentinel device of claim 2, wherein the attestation comprises attesting that the sentinel device provides security superior to security of the IoT device.

### Claim 6 (depends on 1)

The sentinel device of claim 1, wherein the second device is an endpoint device.

### Claim 7 (depends on 1)

The sentinel device of claim 1, wherein the second device is a second sentinel device, the second sentinel device for R2.

### Claim 8 (depends on 7)

The sentinel device of claim 7, wherein the security engine is further configured to route traffic from the IoT device to the second sentinel device.

### Claim 9 (depends on 8)

The sentinel device of claim 8, wherein the security engine is configured to provide routing at an application layer.

### Claim 10 (depends on 8)

The sentinel device of claim 8, wherein the security engine is operable to perform internet protocol routing.

### Claim 11 (depends on 1)

The sentinel device of claim 1, wherein the security engine is further configured to provide a security monitoring function.

### Claim 12 (depends on 11)

The sentinel device of claim 11, wherein the security monitoring function is selected from the group consisting of network monitoring, data loss prevention, packet processing, security scanning, antivirus, firewall, deep packet inspection, reputation services, security information and event monitoring, and network access control.

### Claim 13 (depends on 1)

The sentinel device of claim 1, wherein the service appliance key is different from a key for a direct secure communication channel between the sentinel device and the second device.

### Claim 14 (depends on 1)

The sentinel device of claim 1, wherein the security engine is further configured to receive a service appliance ticket comprising the service appliance key and a second key different from the service appliance key.

### Claim 15 (depends on 1)

The sentinel of claim 1, wherein the security engine is further configured to encrypt packets from the IoT device to the second device within the TEE of the sentinel device.

### Claim 16

One or more tangible, non-transitory computer-readable mediums having stored thereon executable instructions to instruct a sentinel device to:
determine that a first device in a first realm R1 requires a secure communication channel with a second device in a second realm R2;
query a key server for a service appliance key for the secure communication channel;
establish a secure communication channel with the endpoint device using the service appliance key; and
provide a security service function within R1 comprising brokering communication via the secure communication channel between the IoT device and the second device.

### Claim 17 (depends on 16)

The one or more tangible, non-transitory computer-readable storage mediums of claim 16, wherein the instructions are further to provision a trusted execution environment (TEE).

### Claim 18 (depends on 17)

The one or more tangible, non-transitory computer-readable storage mediums of claim 17, wherein the instructions are further to perform an attestation with the key server via the TEE.

### Claim 19

A computer-implemented method of providing sentinel services to an internet of things (IoT), comprising:
determining that a first device in an IoT realm R1 requires a secure communication channel with a second device in a second realm R2;
receiving a service appliance key for the secure communication channel;
establishing a secure communication channel with the endpoint device using the service appliance key; and
providing a security service function within R1 comprising providing communication via the secure communication channel between the first device and the second device.

### Claim 20 (depends on 19)

The method of claim 19, further comprising provisioning a trusted execution environment (TEE).
