# US 12,003,655 B1 · Cryptographic assertions for certificate issuance

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

- Number: US 12,003,655 B1
- Document ID: US12003655B1
- Status: Granted
- Kind: B1
- Application number: 17/544,767
- Filed: 2021-12-07
- Granted: 2024-06-04
- Earliest claimed: 2021-12-07
- Assignees: Amazon Technologies, Inc.
- Applicants: Amazon Technologies, Inc.
- Inventors: Michael S. Slaughter; Trevoli Ponds-White; James Darrin Flanagan; Georgy Sebastian
- Web page: https://patentgrep.com/patent/US12003655B1

## CPC

- H04L 9/321: {involving a third party or a trusted authority}
- H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/3247: {involving digital signatures}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Components of a public certificate authority (CA) generate respective cryptographic assertions during performance of respective tasks of a certificate issuance workflow and a workflow approval component approves/rejects certificate issuance, based upon verification of the cryptographic assertions. For example, a workflow manager may assign tasks of a certificate workflow process to a number of components that process the tasks. The components generate responses and sign the respective responses with keys particular to each component. The workflow manager gathers the cryptographic assertions and sends them to a workflow approval component that validates the assertions, verifies the assertions indicate successful completion of the workflow and approves or rejects certificate issuance.

## Claims

### Claim 1

A system, comprising:
a plurality of computers comprising respective processors and memory and configured to implement a certificate authority comprising:
a plurality of components configured to perform a plurality of tasks of a certificate issuance workflow;
a workflow manager configured to coordinate performance of the plurality of tasks among the plurality of components to perform the certificate issuance workflow; and
a certificate issuance workflow approval component configured to verify successful completion of the certificate issuance workflow;
wherein individual components of the plurality of components are configured to:
perform one or more tasks of the plurality of tasks;
generate a cryptographic assertion for a result of performing the one or more tasks; and
return the cryptographic assertion to the workflow manager;
wherein the workflow manager is configured to:
collect the cryptographic assertions from the plurality of components; and
send a request to a workflow approval component to approve completion of the certificate issuance workflow, wherein the request includes a collection of the cryptographic assertions from the plurality of components for the certificate issuance workflow; and
wherein the workflow approval component is configured to:
validate the cryptographic assertions from the plurality of components using different cryptographic keys for respective components of the plurality of components; and
verify that the validated cryptographic assertions indicate successful completion of the certificate issuance workflow; and
wherein the certificate authority is configured to issue a certificate based on verification by the workflow approval component that the certificate issuance workflow was successfully completed.

### Claim 2 (depends on 1)

The system of claim 1, wherein:
said certificate issuance workflow is performed in response to receipt of a certificate signing request (CSR); and
said individual components of the plurality of components comprise a validation component configured to, for the CSR:
process one or more domain validation requests and assert whether the requesting customer is authorized to have a certificate issued for one or more domains included as a subject alternative name (SAN) in the CSR; and
cryptographically bind the CSR with a successful domain validation check for each of the domains.

### Claim 3 (depends on 1)

The system of claim 1, wherein:
said certificate issuance workflow is performed in response to receipt of a certificate signing request (CSR); and
said individual components of the plurality of components comprise a certificate authority authorization component configured to, for a given certificate request:
perform certificate authority authorization (CAA) verification for one or more domains included as a subject alternative name (SAN) in the CSR; and
cryptographically bind the CSR with a successful CAA verification for the one or more domains.

### Claim 4 (depends on 1)

The system of claim 1, wherein the cryptographic assertions comprise:
a cryptographic assertion generated based on a domain validation process; and
a cryptographic assertion generated based on a certificate authority authorization.

### Claim 5

A method, comprising:
performing by one or more computing devices:
receiving by a workflow approval component, a request to approve completion of a certificate issuance workflow, wherein the request comprises a set of cryptographic assertions obtained from a plurality of components configured to perform a plurality of tasks of the certificate issuance workflow, the;
determining by the workflow approval component and based on the set of cryptographic assertions, whether the certificate issuance workflow was correctly completed, wherein said determining comprises:
validating individual ones of the set of cryptographic assertions from the plurality of components using different cryptographic keys for respective components of the plurality of components; and
verifying that the validated cryptographic assertions indicate successful completion of the certificate issuance workflow; and
sending, for a determination of a correctly-performed certificate issuance workflow, an indication that issuance of the certificate is approved.

### Claim 6 (depends on 5)

The method of claim 5, wherein said determining whether the certificate issuance workflow was correctly completed comprises:
determining whether a cryptographic assertion is present from each component required for the certificate issuance workflow.

### Claim 7 (depends on 5)

The method of claim 5, wherein said determining whether the certificate issuance workflow was correctly completed comprises:
determining, for individual ones of the set of cryptographic assertions, whether a claim presented for the cryptographic assertion is correct.

### Claim 8 (depends on 5)

The method of claim 5, wherein said determining whether the certificate issuance workflow was correctly completed comprises:
determining, for individual ones of the set of cryptographic assertions, whether the cryptographic assertion has expired.

### Claim 9 (depends on 5)

The method of claim 5, wherein to obtain the set cryptographic assertions that are sent in the request, the method further comprises:
coordinating, by a workflow manager, performance of the plurality of tasks among a plurality of components to perform the certificate issuance workflow; and
collecting, by the workflow manager, the cryptographic assertions from the plurality of components.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
performing, by an individual one of the components, one or more tasks of the plurality of tasks;
generating, by the individual component, a cryptographic assertion for a result of performing the one or more tasks; and
returning the cryptographic assertion to the workflow manager.

### Claim 11 (depends on 5)

The method of claim 5, wherein:
the request to approve completion of the certificate issuance workflow is for a certificate signing request (CSR); and
the method further comprises cryptographically-binding, by one of the components, the certificate signing request (CSR) with a successful domain validation check for individual ones of one or more domains included as a subject alternative name (SAN) in the CSR.

### Claim 12 (depends on 5)

The method of claim 5, wherein to collect the cryptographic assertions sent in the request received by the workflow approval component the method further comprises:
performing tasks of the certificate issuance workflow in accordance with rules from a set of individual policies specified by a policy collection version that specifies, according to an entry in a versioned policy collection data store, the set of individual policies and
collecting, during said performing the tasks, the set of cryptographic assertions to be sent to the workflow approval component.

### Claim 13

One or more non-transitory computer-readable media storing program instructions that when executed on or across one or more processors cause the one or more processors to perform:
receiving by a workflow approval component, a request to approve completion of a certificate issuance workflow, wherein the request comprises a set of cryptographic assertions obtained from a plurality of components configured to perform a plurality of tasks of the certificate issuance workflow, the;
determining by the workflow approval component and based on the set of cryptographic assertions, whether the certificate issuance workflow was correctly completed, wherein said determining comprises:
validating individual ones of the set of cryptographic assertions from the plurality of components using different cryptographic keys for respective components of the plurality of components; and
verifying that the validated cryptographic assertions indicate successful completion of the certificate issuance workflow; and
sending, for a determination of a correctly-performed certificate issuance workflow, an indication that issuance of the certificate is approved.

### Claim 14 (depends on 13)

The one or more non-transitory computer-readable media of claim 13, wherein to determine whether the certificate issuance workflow was correctly completed the program instructions, when executed on or across the one or more processors perform determining whether a cryptographic assertion is present from each component required for the certificate issuance workflow.

### Claim 15 (depends on 13)

The one or more non-transitory computer-readable media of claim 13, wherein to determine whether the certificate issuance workflow was correctly completed the program instructions, when executed on or across the one or more processors perform determining, for individual ones of the set of cryptographic assertions, whether a claim presented for the cryptographic assertion is correct.

### Claim 16 (depends on 13)

The one or more non-transitory computer-readable media of claim 13, wherein to determine whether the certificate issuance workflow was correctly completed the program instructions, when executed on or across the one or more processors perform determining, for individual ones of the set of cryptographic assertions, whether the cryptographic assertion has expired.

### Claim 17 (depends on 13)

The one or more non-transitory computer-readable media of claim 13, wherein to obtain the set cryptographic assertions that are sent in the request, the program instructions, when executed on or across the one or more processors perform:
coordinating, by a workflow manager, performance of the plurality of tasks among a plurality of components to perform the certificate issuance workflow; and
collecting, by the workflow manager, the cryptographic assertions from the plurality of components.

### Claim 18 (depends on 17)

The one or more non-transitory computer-readable media of claim 17, storing program instructions that when executed on or across the one or more processors perform:
performing, by an individual one of the components, one or more tasks of the plurality of tasks;
generating, by the individual component, a cryptographic assertion for a result of performing the one or more tasks; and
returning the cryptographic assertion to the workflow manager.

### Claim 19 (depends on 13)

The one or more non-transitory computer-readable media of claim 13,
wherein the request to approve completion of the certificate issuance workflow is for a certificate signing request (CSR); and
wherein the media store program instructions that when executed on or across the one or more processors perform cryptographically-binding, by one of the components, the certificate signing request (CSR) with a successful domain validation check for individual ones of one or more domains included as a subject alternative name (SAN) in the CSR.

### Claim 20 (depends on 13)

The one or more non-transitory computer-readable media of claim 13, wherein to collect the cryptographic assertions sent in the request received by the workflow approval component the program instructions cause the one or more processors to perform:
performing tasks of the certificate issuance workflow in accordance with rules from a set of individual policies specified by a policy collection version that specifies, according to an entry in a versioned policy collection data store, the set of individual policies and
collecting, during said performing the tasks, the set of cryptographic assertions to be sent to the workflow approval component.
