# US 2021/0344508 A1 · Hardware Security Module that Enforces Signature Requirements > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0344508 A1 - Document ID: US20210344508A1 - Status: Published application - Kind: A1 - Application number: 17/375,730 - Filed: 2021-07-14 - Published: 2021-11-04 - Earliest claimed: 2018-09-06 - Assignees: Securosys SA - Applicants: Securosys SA - Inventors: Marcel P. Dasen; Melanie R. Raemy Grob; Lewin Boehnke - Web page: https://patentgrep.com/patent/US20210344508A1 ## CPC - H04L 9/3247: {involving digital signatures} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - G06F 21/335: {for accessing specific resources, e.g. using Kerberos tickets} - G06F 21/602: {Providing cryptographic facilities or services} - H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates} - H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage} - H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)} - H04L 9/3215: {using a plurality of channels (network architectures or network communication protocols using different networks H04L63/18)} - H04L 9/3231: {Biological data, e.g. fingerprint, voice or retina (network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861)} - 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/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)} - H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)} - H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract In an embodiment, an HSM may provide a cryptographic signature service. The HSM may maintain key/token pairs for various users/entities and for a first entity for which signature may be desired. The HSM may ensure that the requirements for the entity's signature are met, and then may apply the entity's signature. In an embodiment, the HSM may augment the private token for the first entity with the public keys of users/entities which are to approve the entity's signature. As the approvals are received, the HSM may record the approvals and may apply the signature once the approvals are received. ## Claims ### Claim 1 A hardware security module (HSM) comprising: a key storage storing a plurality of cryptographic key/token pairs during use, wherein at least a first key/token pair of the plurality of cryptographic key pairs is assigned to a first entity and includes a first private token, and wherein a plurality of entities are associated with the first entity; and a cryptographic engine coupled to the key storage, the cryptographic engine configured to respond to a private token usage request for the first private token received from a second entity of the plurality of entities with a cryptographically-signed object signed using the first private token responsive to determining, in the cryptographic engine, that one or more approvals from one or more third entities of the plurality of entities have been received by the cryptographic engine, wherein the one or more third entities are a quorum of a plurality of the plurality of entities that are permitted to approve cryptographic signing of the object. ### Claim 2 (depends on 1) The HSM as recited in claim 1 wherein the first private token is augmented with a first attribute specifying the quorum. ### Claim 3 (depends on 2) The HSM as recited in claim 2 wherein the first private token is augmented with a second attribute specifying a second quorum of the plurality of entities from which approvals are required prior to responding with the cryptographically-signed object. ### Claim 4 (depends on 3) The HSM as recited in claim 3 wherein the first private token is augmented with a third attribute specifying a logical operator, and the cryptographic engine is configured to apply the logical operator to combine receipt of the quorum and receipt of the second quorum. ### Claim 5 (depends on 2) The HSM as recited in claim 2 wherein the first private token is further augmented with the one or more time parameters, wherein the cryptographic engine is configured to respond with the cryptographically-signed object responsive to the quorum being received within a time period indicated by the one or more time parameters. ### Claim 6 (depends on 1) The HSM as recited in claim 1 wherein the first private token is augmented with one or more usage attributes specifying permitted usages of the first private token. ### Claim 7 (depends on 6) The HSM as recited in claim 6 wherein the permitted usages include a modify usage, wherein the modify usage permits the first private token to be used to modify attributes of other private tokens. ### Claim 8 (depends on 6) The HSM as recited in claim 6 wherein the permitted usages include a block usage, wherein the block usage permits the first private token to block other private tokens from cryptographically signing objects. ### Claim 9 (depends on 8) The HSM as recited in claim 8 wherein the permitted usages include an unblock usage, wherein the unblock usage permits the first private token to unblock blocked private tokens. ### Claim 10 A method comprising: storing a plurality of cryptographic key/token pairs in a key storage of a hardware security module (HSM), wherein at least a first key/token pair of the plurality of cryptographic key/token pairs is assigned to a first entity and includes a first private token, and wherein a plurality of entities are associated with the first entity; and responding, from a cryptographic engine in the HSM, to a private token usage request for the first private token received from a second entity of the plurality of entities with a cryptographically-signed object signed using the first private token responsive to determining, in the cryptographic engine, that one or more approvals from one or more third entities of the plurality of entities have been received by the cryptographic engine, wherein the one or more third entities are a quorum of a subset of the plurality of entities that are permitted to approve cryptographic signing of the object. ### Claim 11 (depends on 10) The method as recited in claim 10 wherein the first private token is augmented with a first attribute specifying the quorum. ### Claim 12 (depends on 11) The method as recited in claim 11 wherein the first private token is augmented with a second attribute specifying a second quorum of a third subset of the plurality of entities from which approvals are required prior to responding with the cryptographically-signed object. ### Claim 13 (depends on 12) The method as recited in claim 12 wherein the first private token is augmented with a third attribute specifying a logical operator, and the method further comprises applying the logical operator to combine receipt of the quorum and receipt of the second quorum. ### Claim 14 (depends on 10) The method as recited in claim 10 wherein the first private token is further augmented with the one or more time parameters, the method further comprising responding with the cryptographically-signed object responsive to the quorum being received within a time period indicated by the one or more time parameters. ### Claim 15 A hardware security module (HSM) comprising: a key storage storing a plurality of cryptographic key/token pairs during use, wherein at least a first key/token pair of the plurality of cryptographic key pairs is assigned to a first entity and includes a first private token, and wherein a plurality of entities are associated with the first entity; and a cryptographic engine coupled to the key storage, the cryptographic engine configured to respond to a private token usage request for the first private token received from a second entity of the plurality of entities with a cryptographically-signed object signed using the first private token responsive to determining, in the cryptographic engine, that one or more approvals from one or more third entities of the plurality of entities have been received by the cryptographic engine, and wherein the first private token is augmented with a modify attribute permitting the first private token to be used to modify attributes of other private tokens. ### Claim 16 (depends on 15) The HSM as recited in claim 15 wherein the first private token is augmented with a block attribute, wherein the block attribute permits the first private token to block other private tokens from cryptographically signing objects. ### Claim 17 (depends on 16) The HSM as recited in claim 16 wherein the first private token is augmented with an unblock attribute, wherein the unblock attribute permits the first private token to unblock blocked private tokens. ### Claim 18 (depends on 16) The HSM as recited in claim 16 wherein the one or more third entities are a quorum of a plurality of the plurality of entities that are permitted to approve cryptographic signing of the object, and wherein the first private token is augmented with a first attribute specifying the quorum. ### Claim 19 (depends on 18) The HSM as recited in claim 18 wherein the first private token is further augmented with the one or more time parameters, wherein the cryptographic engine is configured to respond with the cryptographically-signed object responsive to the quorum being received within a time period indicated by the one or more time parameters. ### Claim 20 (depends on 18) The HSM as recited in claim 18 wherein the first private token is augmented with a second attribute specifying a second quorum of the plurality of entities from which approvals are required prior to responding with the cryptographically-signed object, and wherein the first private token is augmented with a third attribute specifying a logical operator, and the cryptographic engine is configured to apply the logical operator to combine receipt of the quorum and receipt of the second quorum.