# US 2023/0155997 A1 · System and method for authenticating devices in distributed environment

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

- Number: US 2023/0155997 A1
- Document ID: US20230155997A1
- Status: Published application
- Kind: A1
- Application number: 17/526,279
- Filed: 2021-11-15
- Published: 2023-05-18
- Earliest claimed: 2021-11-15
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: SUMANTH VIDYADHARA; MANJUNATH GR; SHUBHAM KUMAR
- Web page: https://patentgrep.com/patent/US20230155997A1

## CPC

- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3273: {for mutual authentication (network architectures or network communication protocols for achieving mutual authentication in a packet data network H04L63/0869)}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods, systems, and devices for providing for trust in a distributed environment are disclosed. In a distributed environment, various devices may be remote to one another and may interact with one another via one or more operable connections. Through the operable connections, various communications may be exchanged. However, the operable connections may not natively support authentication of any particular device in the distributed system. Consequently, entities in the distributed system may not intrinsically trust that the communications received through the distributed environment are authentic. The entities of the system may mutually authenticate one another prior to trusting communications from the other entities. For example, in a scenario where a client wishes to access data hosted by a data source, the client and data source may go through a process of mutually authenticating one another. By doing so, a trusted environment may be established.

## Claims

### Claim 1

A computer-implemented method for securing data in a data source using tokens, the method comprising:
performing, by the data source, a first authentication of a client using:
a copy of a service tag of the client stored in the data source, and
a copy of a first portion of startup data stored in a startup data storage of the client, the copy of the portion of the startup data being stored in the data source and the service tag being used to identify the copy of the portion of the startup data for use during the authentication;
performing, by a client, a second authentication of the data source using:
the copy of the service tag of the client stored in the data source, and
a copy of a second portion of startup data stored in the startup data storage of the client, the copy of the second portion of the startup data being stored in the data source and the service tag being used to identify the copy of the portion of the startup data for use during the authentication;
when the first authentication of the client indicates that the client is authentic and the second authentication of the data source indicates that the data source is authentic, providing, by the data source, a token to the client, the token being usable to access secured data stored in the data source; and
when either the first authentication or the second authentication indicates that one of the client and the data source are not authentic, denying the client access to secure data in the data source.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the first portion of the startup data is usable to verify a portion of data usable to startup operation of the client.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2, wherein the second portion of the startup data is usable to verify all data usable to startup operation of the client.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the first portion comprises a signature of computer code of a startup entity, the signature and computer code being stored in a secure storage device of the client.

### Claim 5 (depends on 1)

The computer implemented method of claim 1, wherein performing the first authentication comprises:
providing a hash of the service tag to the data source;
making a determination, by the data source, that the hash indicates that the client may be a known entity;
in response to the determination:
generating a challenge based on the copy of the first portion of the startup data; and
presenting the challenge to the client;
receiving a response to the presented challenge from the client; and
using the challenge response to determine whether the client is authentic.

### Claim 6 (depends on 5)

The computer implemented method of claim 5, wherein performing the first authentication only authenticates the client to the data source.

### Claim 7 (depends on 1)

The computer implemented method of claim 1, wherein performing the second authentication comprises:
performing a key exchange between the client and the data source to provide the data source with a public key;
generating an authentication package with the public key and the copy of the second portion of startup data stored in the startup data storage of the client; and
providing the generated authentication package to the client.

### Claim 8

A client for providing computer implemented services using secured data stored in a data source, comprising:
startup storage for storing startup data and verification data usable to verify that the startup data will give rise to a predetermined entity when the startup data is executed by the client;
memory; and
a processor adapted to execute computer instructions that cause the processor to:
perform a first authentication of the client to the data source using:
a service tag of the client, and
a portion of the verification data;
perform a second authentication of the data source to the client using:
all of the verification data;
when the first authentication indicates that the client is authentic and the second authentication indicates that the data source is authentic, obtaining a token usable to access secured data stored in the data source; and
when the second authentication indicates that the data source is not authentic, aborting attempts to access the secured data.

### Claim 9 (depends on 8)

The client of claim 8, wherein the portion of the verification data comprises a signature of a portion of the startup data.

### Claim 10 (depends on 8)

The client of claim 8, wherein performing the first authentication comprises:
providing a hash of the service tag to the data source;
after providing the hash:
obtaining a challenge based on the portion of the verification data;
generating a response to the challenge, the response being based on the portion of the verification data; and
using the challenge response to authenticate the client to the data source.

### Claim 11 (depends on 10)

The client of claim 10, wherein the challenge indicates the portion of the verification data.

### Claim 12 (depends on 10)

The client of claim 10, wherein performing the first authentication only authenticates the client to the data source.

### Claim 13 (depends on 10)

The client of claim 10, wherein the challenge selects a different portion of the verification data each time the client is challenged.

### Claim 14 (depends on 8)

The client of claim 8, wherein performing the second authentication comprises:
performing a key exchange with the data source to obtain publicly known numbers usable to obtain a public key for the client;
obtaining an authentication package from the data source, the authentication package being based, at least in part, on the key exchange;
segregating the authentication package into a second public key for the data source and a copy of all of the authentication data; and
comparing the copy of all of the authentication data and the authentication data stored in the startup storage to obtain an authentication status for the data source.

### Claim 15

A data source for securing data stored in a data source, comprising:
storage for storing a copy of verification data stored in a client;
memory; and
a processor adapted to execute computer instructions that cause the processor to:
perform a first authentication of the client to the data source using:
a service tag of the client, and
a portion of the copy of the verification data;
perform a second authentication of the data source to the client using:
all of the copy of the verification data;
when the first authentication indicates that the client is authentic and the second authentication indicates that the data source is authentic, providing a token to the client usable to access secured data stored in the data source; and
when the first authentication indicates that the client is not authentic, preventing the client from accessing the data.

### Claim 16 (depends on 15)

The data source of claim 15, wherein the portion of the copy of the verification data comprises a signature of a portion of startup data usable by the client to enter a predetermined state.

### Claim 17 (depends on 15)

The data source of claim 15, wherein performing the first authentication comprises:
providing a hash of the service tag to the data source;
after providing the hash:
obtaining a challenge based on the portion of the verification data;
generating a response to the challenge, the response being based on the portion of the verification data; and
using the challenge response to authenticate the client to the data source.

### Claim 18 (depends on 17)

The data source of claim 17, wherein the challenge indicates the portion of the verification data.

### Claim 19 (depends on 17)

The data source of claim 17, wherein performing the first authentication only authenticates the client to the data source.

### Claim 20 (depends on 15)

The data source of claim 15, wherein performing the second authentication comprises:
performing a key exchange with the client to obtain publicly known numbers usable to obtain a public key;
generating an authentication package based, at least in part, on the key exchange and all of the copy of the authentication data;
providing the authentication package to the client; and
receiving a public key from the client when the client authenticates the data source using the authentication package.
