# US 2025/0094543 A1 · Dynamic decision engine for software authority to operate

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

- Number: US 2025/0094543 A1
- Document ID: US20250094543A1
- Status: Published application
- Kind: A1
- Application number: 18/965,114
- Filed: 2024-12-02
- Published: 2025-03-20
- Earliest claimed: 2022-07-11
- Assignees: The Boeing Company
- Applicants: The Boeing Company
- Inventors: Michael L. HEIM; Christopher BREEDEN; Hong Chuen Terence HO
- Web page: https://patentgrep.com/patent/US20250094543A1

## CPC

- G06F 21/121: {Restricting unauthorised execution of programs}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system for, and method of, authorizing usage of software developed in an application management platform are disclosed. The techniques include obtaining, from the application management platform, risk qualification parameters for the software; determining a risk qualification value from the risk qualification parameters; obtaining risk threshold parameters; determining a risk threshold value from the risk threshold parameters; comparing the risk qualification value to the risk threshold value to obtain an acceptability state for usage of the software; and performing an authority to operate action based on the acceptability state, where the authority to operate action includes at least one of: authorizing release of the software upon a positive acceptability state, or instructing the application management platform to send an alert upon a negative acceptability state.

## Claims

### Claim 1

(canceled)

### Claim 2

An automated computer-implemented method of authorizing usage of software developed in an application management platform, the method comprising:
obtaining, from the application management platform, risk qualification parameters for the software, wherein the application management platform comprises a computing environment that allows for access and development of a software product, wherein the risk quantification parameters comprise design time risk parameters, and wherein the risk quantification parameters comprise build time risk parameters;
determining a risk qualification value from the risk qualification parameters;
obtaining risk threshold parameters;
determining a risk threshold value from the risk threshold parameters;
comparing the risk qualification value to the risk threshold value to obtain an acceptability state for usage of the software; and
performing an authority to operate action based on the acceptability state, wherein the authority to operate action comprises at least one of: authorizing release of the software upon a positive acceptability state, or instructing the application management platform to send an alert upon a negative acceptability state.

### Claim 3 (depends on 2)

The automated computer-implemented method of claim 2, wherein the authority to operate action comprises authorizing release of the software, the method further comprising:
automatically deploying the software.

### Claim 4 (depends on 2)

The automated computer-implemented method of claim 2, wherein the design time risk parameters are obtained at a software security architecture/planning phase.

### Claim 5 (depends on 2)

The automated computer-implemented method of claim 2, wherein the design time risk parameters comprise at least one of: a software security risk security parameter, an application threat model parameter, or a business criticality assessment parameter.

### Claim 6 (depends on 2)

The automated computer-implemented method of claim 2, wherein the build time risk parameters are obtained at a continuous deployment pipeline phase.

### Claim 7 (depends on 2)

The automated computer-implemented method of claim 2, wherein the build time risk parameters comprise at least one of: a secrets detection parameter, a static application security testing parameter, a dynamic application security testing parameter, a container vulnerability assessment parameter, a software bill of materials parameter, a software composition analysis parameter, an interactive application security testing parameter, an infrastructure as code scanning parameter, a policy as code parameter, or a code signing parameter.

### Claim 8 (depends on 2)

The automated computer-implemented method of claim 2, wherein the risk threshold parameters comprise runtime risk parameters.

### Claim 9 (depends on 8)

The automated computer-implemented method of claim 8, wherein the runtime risk parameters comprise at least one of: a runtime application security protection parameter, or an application security telemetry parameter.

### Claim 10 (depends on 2)

The automated computer-implemented method of claim 2, wherein the risk threshold parameters comprise real time risk and threat parameters.

### Claim 11 (depends on 10)

The automated computer-implemented method of claim 10, wherein the real time risk and threat parameters comprise at least one of: a code risk analysis parameter, or a threat intel parameter.

### Claim 12

A computer system for authorizing usage of software developed in an application management platform, the computer system comprising an electronic processor and a non-transitory computer-readable medium comprising instructions that, when executed by the electronic processor, configure the electronic processor to perform actions comprising:
obtaining, from the application management platform, risk qualification parameters for the software, wherein the application management platform comprises a computing environment that allows for access and development of a software product, wherein the risk quantification parameters comprise design time risk parameters, and wherein the risk quantification parameters comprise build time risk parameters;
determining a risk qualification value from the risk qualification parameters;
determining a risk qualification value from the risk qualification parameters;
obtaining risk threshold parameters;
determining a risk threshold value from the risk threshold parameters;
comparing the risk qualification value to the risk threshold value to obtain an acceptability state for usage of the software; and
performing an authority to operate action based on the acceptability state, wherein the authority to operate action comprises at least one of: authorizing release of the software upon a positive acceptability state, or instructing the application management platform to send an alert upon a negative acceptability state.

### Claim 13 (depends on 12)

The computer system of claim 12, wherein the authority to operate action comprises authorizing release of the software, the method further comprising:
automatically deploying the software.

### Claim 14 (depends on 12)

The computer system of claim 12, wherein the design time risk parameters are obtained at a software security architecture/planning phase.

### Claim 15 (depends on 12)

The computer system of claim 12, wherein the design time risk parameters comprise at least one of: a software security risk security parameter, an application threat model parameter, or a business criticality assessment parameter.

### Claim 16 (depends on 12)

The computer system of claim 12, wherein the build time risk parameters are obtained at a continuous deployment pipeline phase.

### Claim 17 (depends on 12)

The computer system of claim 12, wherein the build time risk parameters comprise at least one of: a secrets detection parameter, a static application security testing parameter, a dynamic application security testing parameter, a container vulnerability assessment parameter, a software bill of materials parameter, a software composition analysis parameter, an interactive application security testing parameter, an infrastructure as code scanning parameter, a policy as code parameter, or a code signing parameter.

### Claim 18 (depends on 12)

The computer system of claim 12, wherein the risk threshold parameters comprise runtime risk parameters.

### Claim 19 (depends on 18)

The computer system of claim 18, wherein the runtime risk parameters comprise at least one of: a runtime application security protection parameter, or an application security telemetry parameter.

### Claim 20 (depends on 12)

The computer system of claim 12, wherein the risk threshold parameters comprise real time risk and threat parameters.

### Claim 21 (depends on 20)

The computer system of claim 20, wherein the real time risk and threat parameters comprise at least one of: a code risk analysis parameter, or a threat intel parameter.
