Granted Patent B2

US 12,204,631 · App. 17/855,890 · Granted Jan 21, 2025

Inventors: Devesh Kumar Tewari (Noida, IN); Amit Sinha (Pradesh, IN)

Assignee: THALES DIS CPL USA, INC.

G06F21/40G06F21/34

Abstract

Claims (60)

1. A computer implemented method for distributed quorum authentication enforcement of a Hardware Security Module (HSM) device, whereby when a user accesses a resource on the HSM device that user's access is enforced within a quorum expiry period via the Applications Programming interface (API) gateway responsive to real time authentication of administrators remotely working in coherence with access to a shared secret for authorizing HSM operations needing simultaneous approval, characterized in that the method comprises the steps of,

in a quorum creation event stage:

creating a quorum request when an operation on said resource is attempted that requires quorum authorization, by:

inquiring a quorum policy if a quorum is required to access said resource;

generating the quorum request in accordance with said quorum policy and storing it in a database thereby attaching it to said resource,

generating a quorum identifier (ID) to associate with said resource included in the quorum request;

responsive to said creating of said quorum request, informing said administrators to each provide an approval status for said quorum request in real time via said API gateway;

in a quorum approval event stage:

responsive to receiving said approval status from said administrators working in coherence to complete the shared secret for said HSM operational requirements via said API gateway within said quorum expiry period, validating said administrators are authorized to approve said quorum request,

if validated, updating a voting count on the quorum request in a database; and

informing said user via said API gateway of said approval status, and enforcing an access to said resource in accordance with said quorum policy and updated quorum request,

wherein said quorum request includes said quorum ID, an approval threshold, a voting count, the quorum expiry period, and an approval status.

2. The method of claim 1 further comprising,

in a quorum data retrieval event stage, via said API gateway

checking whether said an administrators are allowed to access said quorum id; and

providing details of said quorum request to said administrators via said API gateway.

3. The method of claim 1 further comprising,

in a quorum application event stage, via said API gateway:

checking whether said administrators are allowed to access said quorum id;

retrieving details of said quorum request; and

if an approval threshold is met in view of said voting count and within said quorum expiry period, updating said approval status to indicate quorum is approved for said resource, and committing said approval status in said database for said quorum request.

4. 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.

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

6. The method of claim 1 , wherein said API gateway is in an architectural style of 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.

7. A Hardware Security Module (HSM) device implementing a distributed quorum authentication enforcement through a API gateway, whereby when a user accesses a resource on the HSM device, that user's access is enforced within a quorum expiry period via the Applications Programming interface (API) gateway responsive to real time authentication of administrators remotely working in coherence with access to a shared secret for authorizing HSM operations needing simultaneous approval, characterized in that the HSM comprises:

one or more resources;

a resource manager API for accessing said one or more resources;

an enforcement module for enforcing access to said one or more resources via said API gateway according to a quorum policy; and

a quorum manager for generating and storing a quorum request in a database,

wherein

in a quorum creation event stage:

said enforcement module inquires a quorum policy if a quorum is required to access said resource;

said quorum manager creates a quorum request when an operation on said resource 40 is attempted that requires quorum authorization, by:

generating the quorum request in accordance with said quorum policy and storing it in a database thereby attaching it to said resource,

generating a quorum identifier (ID) to associate with said resource included in the quorum request;

responsive to said creating of said quorum request, said resource manager API informs administrators to each provide an approval status for said quorum request via said API gateway;

in a quorum approval event stage:

responsive to receiving said approval status from said administrators working in coherence to complete the shared secret for said HSM operational requirements via said API gateway within said quorum expiry period, said quorum manager validates said administrators are authorized to approve said quorum request,

if validated, updates a voting count on the quorum request in a database; and

informs said user via said API gateway of said approval status, and enforcement module enforces an access to said resource in accordance with said quorum policy and updated quorum request,

wherein said quorum request includes said quorum ID, an approval threshold, a voting count, the quorum expiry period, and an approval status.

8. The HSM of claim 7 wherein during said quorum creation event stage:

said API gateway sends access token to quorum manager to validate whether the user is authentic and exists;

said quorum manager validates said user and sends user identity to said API gateway, which checks internal rules to determine to which micro-service of said resource manager API to send the quorum request and invoke appropriate resource manager API with name of said user.

9. The HSM of claim 8 , wherein

said resource manager API consults Enforcement module to determine if the user is authorized to perform requested operation;

said enforcement module reads internal authorization policy from database, and determines from said quorum policy if the operation requires a quorum before a configuration change is committed on said resource; and

said resource manager API prepares a quorum request and sends request to Quorum manager to generate a quorum request along with required data to store in database.

10. The HSM of claim 9 , wherein

said Quorum manager creates said quorum identifier for said quorum request and stores data associated with the quorum request in the database;

said Quorum manager returns the generated quorum identifier to resource manager API to the user through API gateway.

11. The HSM of claim 7 wherein, during the quorum approval event stage, each administrator votes to approve or deny a quorum request if they are authorized, whereby:

said API gateway requests HSM to approve the quorum with quorum identifier and authorize a token that validates the administrator;

said API gateway forwards the request to quorum management module to determine if the user is allowed to invoke resources API and respond whether the user is authorized or not.

12. The HSM of claim 11 wherein

said quorum manager reads details of the quorum request from database, then consults enforcement module if the administrator has authorization to approve the request;

said enforcement module reads the authorization for the quorum policy 51 from database and responds back to quorum manager, and

if the administrator is authorized, the quorum manager increases an approval count of the quorum request and stores this information as an entry in database, and

responds back to the administrator through API gateway to confirm or deny the user approval, wherein once a required approval has been received, the user can invoke resources API to apply configuration changes on said HSM.

13. The HSM of claim 11 further comprising at least one 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, resource manager API, said enforcement module, and said quorum manager.

Assignments (2)

Continuity (1)

References Cited (32)