# US 12,010,511 B2 · Method and apparatus for encryption key exchange with enhanced security through opti-encryption channel

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

- Number: US 12,010,511 B2
- Document ID: US12010511B2
- Status: Granted
- Kind: B2
- Application number: 18/078,855
- Filed: 2022-12-09
- Published: 2023-04-13
- Granted: 2024-06-11
- Earliest claimed: 2019-12-10
- Assignees: Winkk, Inc.
- Applicants: Winkk, Inc
- Inventors: Robert O. Keith, Jr.; Bradley E. Gray
- Web page: https://patentgrep.com/patent/US12010511B2

## CPC

- H04W 12/0471: Key exchange
- H04L 9/0822: {using key encryption key}
- H04L 9/0852: {Quantum cryptography (transmission systems employing electromagnetic waves other than radio waves, e.g. light, infrared H04B10/00; wavelength-division multiplex systems H04J14/02; WDM arrangements H04J14/03)}
- 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/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A security platform architecture is described herein. The security platform architecture includes multiple layers and utilizes a combination of encryption and other security features to generate a secure environment.

## Claims

### Claim 1

An apparatus comprising:
a non-transitory memory and a processor coupled to the memory, the processor configured for implementing:
maintaining a secure vault, wherein the secure vault is configured for storing code;
accessing one or more building block modules, wherein the one or more building block modules are formed using the code stored in the secure vault, wherein the one or more building block modules form an application comprising identification proofing based on behavior analysis;
executing an orchestrator, wherein the orchestrator is configured to control access to the one or more building block modules; and
implementing a security callback wherein access to the code stored in the secure vault is restricted when a call to a server results in a non-matching hash.

### Claim 2 (depends on 1)

The apparatus of claim 1 wherein the code comprises executables, dynamic link libraries, configuration information and/or data.

### Claim 3 (depends on 1)

The apparatus of claim 1 wherein the secure vault is configured for implementing a data at rest encryption scheme.

### Claim 4 (depends on 1)

The apparatus of claim 1 wherein the code is encrypted using white noise encryption.

### Claim 5 (depends on 1)

The apparatus of claim 1 wherein the code is signed.

### Claim 6 (depends on 1)

The apparatus of claim 1 wherein the one or more building block modules communicate using encrypted communications.

### Claim 7 (depends on 1)

The apparatus of claim 1 wherein the one or more building block modules are each wrapped in one or more application programming interfaces.

### Claim 8 (depends on 1)

The apparatus of claim 1 wherein the orchestrator is configured to:
deploy services,
utilize one or more keys to access the code,
control one or more policies, and
organize the one or more building block modules.

### Claim 9

A method comprising:
maintaining a secure vault, wherein the secure vault is configured for storing code;
accessing one or more building block modules, wherein the one or more building block modules are formed using the code stored in the secure vault, wherein the one or more building block modules form an application comprising identification proofing based on behavior analysis;
executing an orchestrator, wherein the orchestrator is configured to control access to the one or more building block modules; and
implementing a security callback wherein access to the code stored in the secure vault is restricted when a call to a server results in a non-matching hash.

### Claim 10 (depends on 9)

The method of claim 9 wherein the code comprises executables, dynamic link libraries, configuration information and/or data.

### Claim 11 (depends on 9)

The method of claim 9 wherein the secure vault is configured for implementing a data at rest encryption scheme.

### Claim 12 (depends on 9)

The method of claim 9 wherein the code is encrypted using white noise encryption.

### Claim 13 (depends on 9)

The method of claim 9 wherein the code is signed.

### Claim 14 (depends on 9)

The method of claim 9 wherein the one or more building block modules communicate using encrypted communications.

### Claim 15 (depends on 9)

The method of claim 9 wherein the one or more building block modules are each wrapped in one or more application programming interfaces.

### Claim 16 (depends on 9)

The method of claim 9 wherein the orchestrator is configured to:
deploy services,
utilize one or more keys to access the code,
control one or more policies, and
organize the one or more building block modules.

### Claim 17

A system comprising:
a secure vault configured for storing code;
one or more building block modules, wherein the one or more building block modules are formed using the code stored in the secure vault, wherein the one or more building block modules form an application comprising identification proofing based on behavior analysis;
executing an orchestrator, wherein the orchestrator is configured to control access to the one or more building block modules; and
a security callback implementation wherein access to the code stored in the secure vault is restricted when a call to a server results in a non-matching hash.

### Claim 18 (depends on 17)

The system of claim 17 wherein the code comprises executables, dynamic link libraries, configuration information and/or data.

### Claim 19 (depends on 17)

The system of claim 17 wherein the secure vault is configured for implementing a data at rest encryption scheme.

### Claim 20 (depends on 17)

The system of claim 17 wherein the code is encrypted using white noise encryption.

### Claim 21 (depends on 17)

The system of claim 17 wherein the code is signed.

### Claim 22 (depends on 17)

The system of claim 17 wherein the one or more building block modules communicate using encrypted communications.

### Claim 23 (depends on 17)

The system of claim 17 wherein the one or more building block modules are each wrapped in one or more application programming interfaces.

### Claim 24 (depends on 17)

The system of claim 17 wherein the orchestrator is configured to:
deploy services,
utilize one or more keys to access the code,
control one or more policies, and
organize the one or more building block modules.