# US 2025/0094590 A1 · Methods to ensure trust validation and integrity of workflow execution

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

- Number: US 2025/0094590 A1
- Document ID: US20250094590A1
- Status: Published application
- Kind: A1
- Application number: 18/466,907
- Filed: 2023-09-14
- Published: 2025-03-20
- Earliest claimed: 2023-09-14
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Ameer M. Jabbar; Yidong Wang; Qi Jin; Ching-Yun Chao
- Web page: https://patentgrep.com/patent/US20250094590A1

## CPC

- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- H04L 9/3247: {involving digital signatures}
- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- 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

One example method includes receiving, at a multi cloud service orchestration platform from a client, a request for performance of a workflow, authenticating and authorizing the client, invoking orchestration of the workflow, invoking the workflow, validating a workflow definition associated with the workflow, and on successful validation, initializing execution of the workflow, and executing, at an activity container, the workflow. The method may be performed in the multi cloud service orchestration platform.

## Claims

### Claim 1

A method, comprising:
receiving, at a multi cloud service orchestration platform from a client, a request for performance of a workflow;
authenticating and authorizing the client;
invoking orchestration of the workflow;
invoking the workflow;
validating a workflow definition associated with the workflow, and on successful validation, initializing execution of the workflow; and
executing, at an activity container, the workflow.

### Claim 2 (depends on 1)

The method as recited in claim 1, wherein the workflow corresponds to a workflow definition included in a digitally signed workflow package that also comprises a workflow implementation, an activity definition, and an activity implementation.

### Claim 3 (depends on 1)

The method as recited in claim 1, wherein the workflow resides in a workflow registry prior to execution.

### Claim 4 (depends on 1)

The method as recited in claim 1, wherein the activity container executes only digitally signed workflows.

### Claim 5 (depends on 1)

The method as recited in claim 1, wherein the workflow is executed in the activity container according to immutable workflow parameters, and a security context, that are immutable and cannot be modified by the activity container while the workflow is executing.

### Claim 6 (depends on 1)

The method as recited in claim 1, wherein the validating of the workflow definition, and the initializing of the execution of the workflow, are performed by a workflow service.

### Claim 7 (depends on 1)

The method as recited in claim 1, wherein a digitally signed workflow package that comprises the workflow definition, as well as a workflow implementation, an activity definition, and an activity implementation, is validated and reviewed by a certificate authority.

### Claim 8 (depends on 1)

The method as recited in claim 1, wherein a digitally signed workflow package that comprises the workflow definition, as well as a workflow implementation, an activity definition, and an activity implementation, is stored, prior to execution of the workflow, in a workflow registry by a workflow subsystem.

### Claim 9 (depends on 1)

The method as recited in claim 1, wherein the workflow is executed in the activity container according to immutable workflow parameters that have been digitally signed.

### Claim 10 (depends on 1)

The method as recited in claim 1, wherein client security context data and workflow parameters are available to the workflow on a read-only basis.

### Claim 11

A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
receiving, at a multi cloud service orchestration platform from a client, a request for performance of a workflow;
authenticating and authorizing the client;
invoking orchestration of the workflow;
invoking the workflow;
validating a workflow definition associated with the workflow, and on successful validation, initializing execution of the workflow; and
executing, at an activity container, the workflow.

### Claim 12 (depends on 11)

The non-transitory storage medium as recited in claim 11, wherein the workflow corresponds to a workflow definition included in a digitally signed workflow package that also comprises a workflow implementation, an activity definition, and an activity implementation.

### Claim 13 (depends on 11)

The non-transitory storage medium as recited in claim 11, wherein the workflow resides in a workflow registry prior to execution.

### Claim 14 (depends on 11)

The non-transitory storage medium as recited in claim 11, wherein the activity container executes only digitally signed workflows.

### Claim 15 (depends on 11)

The non-transitory storage medium as recited in claim 11, wherein the workflow is executed in the activity container according to immutable workflow parameters, and a security context, that are immutable and cannot be modified by the activity container while the workflow is executing.

### Claim 16 (depends on 11)

The non-transitory storage medium as recited in claim 11, wherein the validating of the workflow definition, and the initializing of the execution of the workflow, are performed by a workflow service.

### Claim 17 (depends on 11)

The non-transitory storage medium as recited in claim 11, wherein a digitally signed workflow package that comprises the workflow definition, as well as a workflow implementation, an activity definition, and an activity implementation, is validated and reviewed by a certificate authority.

### Claim 18 (depends on 11)

The non-transitory storage medium as recited in claim 11, wherein a digitally signed workflow package that comprises the workflow definition, as well as a workflow implementation, an activity definition, and an activity implementation, is stored, prior to execution of the workflow, in a workflow registry by a workflow subsystem.

### Claim 19 (depends on 11)

The non-transitory storage medium as recited in claim 11, wherein the workflow is executed in the activity container according to immutable workflow parameters that have been digitally signed.

### Claim 20 (depends on 11)

The non-transitory storage medium as recited in claim 11, wherein client security context data and workflow parameters are available to the workflow on a read-only basis.
