# US 2024/0004983 A1 · Distributed quorum authorization enforcement through an api gateway

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

- Number: US 2024/0004983 A1
- Document ID: US20240004983A1
- Status: Published application
- Kind: A1
- Application number: 17/855,890
- Filed: 2022-07-01
- Published: 2024-01-04
- Earliest claimed: 2022-07-01
- Assignees: Thales Dis Cpl USA, Inc.
- Applicants: Thales Dis Cpl USA, Inc.
- Inventors: Devesh Kumar TEWARI; Amit SINHA
- Web page: https://patentgrep.com/patent/US20240004983A1

## CPC

- G06F 21/40: by quorum, i.e. whereby two or more security principals are required
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- G06F 21/34: involving the use of external additional devices, e.g. dongles or smart cards
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one embodiment a Hardware Server Module (HSM) (10) implementing a distributed quorum authentication enforcement is provided, whereby user access to a resource (40) on the device (10) is enforced via an API gateway (16). The HSM comprises one or more resources, a separate resource manager API for accessing the one or more resources, an enforcement module for enforcing access to the one or more resources via the API gateway according to a quorum policy, and a quorum manager for generating and storing a quorum request in a database. The API gateway (16) can be a RESTful API using HTTP requests to produce and consume data related to quorum services via at least one of a GET, PUT, POST, PATCH and DELETE command type. Other embodiments are disclosed.

## Claims

### Claim 1

A computer implemented method for distributed quorum authentication enforcement of a device (10), whereby user access to a resource (40) on the device (10) is enforced via the API gateway (16), characterized in that the method comprises the steps of,
in a quorum creation event stage (310):
creating a quorum request (52) when an operation on said resource (40) is attempted that requires quorum authorization, by:
inquiring a quorum policy (51) if a quorum is required to access said resource (40);
generating the quorum request (52) in accordance with said quorum policy (51) and storing it in a database (17) thereby attaching it to said resource (40),
generating a quorum identifier (ID) to associate with said resource (40) included in the quorum requst (52);
responsive to said creating of said quorum request (52), informing administrators to each provide an approval status for said quorum request (52) via said API gateway (16);
in a quorum approval event stage (330):
responsive to receiving said approval status from said administrators via said API gateway (16), validating said administrators are authorized to approve said quorum request (52),
if validated, updating a voting count on the quorum request (52) in a database (17); and
informing said user via said API gateway (16) of said approval status, and enforcing an access to said resource in accordance with said quorum policy (51) and updated quorum request (52),
wherein said quorum request includes said quorum ID, an approval threshold, a voting count, a quorum expiry, and an approval status.

### Claim 2 (depends on 1)

The method of claim 1 further comprising,
in a quorum data retrieval event stage (310), via said API gateway (16)
checking whether said user or an administrator is allowed to access said quorum id;
if so, associating said quorum id with said quorum request (52); and
providing details of said quorum request (52) to said use or administrator via said API (16).

### Claim 3 (depends on 1)

The method of claim 1 further comprising,
in a quorum application event stage (340), via said API gateway (16):
checking whether said user or an administrator is allowed to access said quorum id;
if so, associating said quorum id with said quorum request (52);
retrieving details of said quorum request (52); and
if an approval threshold is met in view of said voting count and within said quorum expiry, updating said approval status to indicate quorum is approved for said resource, and commiting said approval status in said database (17) for said quorum request (52).

### Claim 4 (depends on 1)

The method of claim 1 is performed by a hardware processor executing computer program code instructions from an electronic memory to execute at least said method steps.

### Claim 5 (depends on 1)

The method of claim 1, wherein said operation on said resource comprises one among update, view, modify, copy or delete.

### Claim 6 (depends on 1)

The method of claim 1, wherein said API gateway (16) is a RESTful API using HTTP requests to produce and consume data related to quorum services via at least one of a GET, PUT, POST, PATCH and DELETE command type.

### Claim 7

A Hardware Server Module (HSM) implementing a distributed quorum authentication enforcement through a API gateway (16), whereby user access to a resource (40) on the device (10) is enforced via the API gateway, characterized in that the HSM comprises:
one or more resources (40);
a resource manager API (36) for accessing said one or more resources (40);
an enforcement module (34) for enforcing access to said one or more resources via said API gateway (16) according to a quorum policy (51); and
a quorum manager (37) for generating and storing a quorum (52) request in a database (17),
wherein
in a quorum creation event stage (310):
said enforcement module (34) inquires a quorum policy (51) if a quorum is required to access said resource (40);
said quorum manager (37) creates a quorum request (52) when an operation on said resource 40 is attempted that requires quorum authorization, by:
generating the quorum request (52) in accordance with said quorum policy (51) and storing it in a database (17) thereby attaching it to said resource (40),
generating a quorum identifier (ID) to associate with said resource (40) included in the quorum requst (52);
responsive to said creating of said quorum request (52), said resource manager API (36) informs administrators to each provide an approval status for said quorum request (52) via said API gateway (16);
in a quorum approval event stage (330):
responsive to receiving said approval status from said administrators via said API (16), said quorum manager (37) validates said administrators are authorized to approve said quorum request (52),
if validated, updates a voting count on the quorum request (52) in a database (17); and
informs said user via said API gateway (16) of said approval status, and enforcement module 34 enforces an access to said resource in accordance with said quorum policy (51) and updated quorum request (52),
wherein said quorum request includes said quorum ID, an approval threshold, a voting count, a quorum expiry, and an approval status.

### Claim 8 (depends on 7)

The HSM of claim 7 wherein, or a quorum creation (310) event stage:
said API gateway (16) sends access token to quorum manager (37) to validate whether a user is authentic and exists;
said quorum manager (37) validates said user and sends user identity to said API Gateway (16), which checks internal rules to determine to which micro-service of said resource manager API (36) to send the quorum request (52) and invoke appropriate resource manager API (36) with name of said user.

### Claim 9 (depends on 8)

The HSM of claim 8, wherein
said resource manager API (36) consults Enforcement module (34) to determine if user is authorized to perform requested operation;
said enforcement module (34) reads internal authorization policy from database (17), and determines from said quorum policy (51) if the operation requires a quorum before a configuration change is committed on said resource; and
said resource manager API (36) prepares a quorum request (52) and sends request to Quorum manager (37) to generate a quorum request (52) along with required data to store in database.

### Claim 10 (depends on 9)

The HSM of claim 9, wherein
said Quorum manager (37) creates said quorum identifier (53) for said quorum request (52) and stores data associated with the quorum request (52) in the database (17);
said Quorum manager (37) returns the generated quorum identifier (53) to resource manager API (36) to the user through API gateway (16).

### Claim 11 (depends on 7)

The HSM of claim 7 wherein, for a quorum approval (340) event stage, user vote to approve or deny a quorum request if they are authorized by:
said API gateway (16) requests HSM to approve a quorum with quorum identifier (53) to approve and authorize a token;
said API gateway (16) forwards the request to quorum management module (37) to determine if user is allowed to invoke resources API 36 and respond whether user is authorized or not.

### Claim 12 (depends on 11)

The HSM of claim 11 wherein
said quorum manager (37) reads details of the quorum request (52) from database (17), then consults enforcement module (34) if user has authorization to approve the request;
said enforcement module (34) reads the authorization for the quorum policy 51 from database (17) and responds back to quorum manager, and
if user is authorized, the quorum manager (37) increases an approval count of the quorum request (52) and stores this information as an entry in database (17), and
responds back to the user through API gateway (16) to confirm or deny user approval, wherein once a required approval has been received, the user or an approver to the quorum request can invoke resources API 36 to apply configuration changes on said HSM.

### Claim 13 (depends on 1)

The HSM of claim 1 further comprising at least one a hardware processor executing computer program code instructions from an electronic memory to execute processes of at least one microservice running in an operating system of said HSM to support operation of said resources (40), resource manager API (36), said enforcement module (34), and said quorum manager (37).
