Managed securitized containers and container communications

• US 10,579,793 B2
• Filed: 12/14/2018
• Issued: 03/03/2020
• Est. Priority Date: 06/12/2017
• Status: Active Grant

• Current Assignee: Ironclad Encryption Corp.
• Original Assignee: Daniel Maurice Lerner
• Inventors: Lerner, Daniel Maurice
• Primary Examiner(s): Holder, Bradley W
• Application Number:
  US16/221,041
• Publication Number:
  US 20190260716A1
• Time in Patent Office: 445 Days
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 21/36 by graphic or iconic representation
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: H04L 2463/082 applying multi-factor authentication cryptographic mechanisms or cryptographic arrangements including means for verifying the identity or authority of a user of the system or for message authentication H04L9/32
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0861 using biometrical features, e.g. fingerprint, retina-scan cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/0819 Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) network architectures or network communication protocols for key distribution in a packet data network H04L63/062
• CPC Class Codes: H04L 9/0866 involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics
• CPC Class Codes: H04L 9/088 Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068
• CPC Class Codes: H04L 9/0894 Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
• CPC Class Codes: H04L 9/14 using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Abstract

This disclosure provides for the securitization and/or encryption of software container devices that utilize both a control plane and a trust plane for ensuring that communication signals transmitted from and data residing within these containers are not corruptible. In addition, processors for monitoring statistics regarding data at rest and data on the move associated with creating these secure containers are also included.

Claims

1. One or more securitized software container management devices, comprising:

at least one computer processing unit (CPU) with computational capabilities that is connected to and controls a computer memory via an address bus and a data bus where said address bus accesses a designated range of computer memories and range of memory bits and said data bus provides a flow of transmission(s) into and out of said CPU and computer memory;

at least one control plane;

at least one trust plane; and

at least one software container;

wherein controller logic that exists within the control plane transfers signals along a single path to said trust plane or to said software container, or both said trust plane and said software container, wherein said signals further travel through said control plane to said trust plane or said software container, or both said trust plane and said software container, and wherein said signals are securitized or encrypted, or both securitized and encrypted either before, or as, said signals enter said at least one software container;

wherein one or more access devices or one or more user devices, or both one or more access devices and one or more user devices further comprises;

at least one computer processing unit (CPU) with computational capabilities that is connected to and controls a computer memory via an address bus and a data bus where said address bus accesses a designated range of computer memories and range of memory bits and said data bus provides a flow of transmission(s) into and out of said CPU and computer memory;

one or more real or one or more virtual master distributed auto-synchronous array (DASA) databases or both one or more real and one or more virtual master distributed auto-synchronous array (DASA) databases located within or external to said access devices and said user devices, where said master (DASA) databases at least store and retrieve data and also include at least two or more partial distributed auto-synchronous array (DASA) databases, wherein said partial DASA databases function in either an independent manner, a collaborative manner or both an independent manner and a collaborative manner, wherein said master and said partial DASA databases analyze and provide information in a form of data and act to control one or more output devices, wherein said output devices are computing devices.

2. The one or more securitized software container management devices of claim 1, wherein said one or more output devices create user devices, and wherein said master and said partial DASA databases configure bi-directional transmission of data to and from multiple partial user devices, to and from multiple partial access devices, or to and from both multiple partial user and multiple partial access devices, wherein said user devices and said access devices are computing devices, and wherein one or more partial user and one or more partial access devices store and provide at least partial copies of portions of said master DASA databases, and wherein said master DASA databases, said partial DASA databases, or both said partial DASA databases and said master DASA databases are linked and communicate with each other as well as inclusion of one or more logging and monitoring databases that provide statistical and numerical calculations utilizing data, wherein said one or more access devices authenticate using a first set of computing operations, and validate using a second set of computing operations, and wherein a third set of computing operations controls access for a specified set of users.

3. The one or more securitized software container management devices of claim 1, wherein said at least one software container is connected to said control plane where said signals enter said software container subsequent to an entrance to said control plane, wherein said control plane controller logic accesses one or more software containers and wherein a set of instructions is added to said software containers via one or more application logic repositories and from one or more software container prototype repositories,

and;

wherein said at least one software container is connected to said trust plane where said signals enter said software container subsequent to entering said trust plane.

4. The one or more securitized software container management devices of claim 1, wherein said signals are sent directly from said control plane controller logic to said at least one container and wherein signals from said control plane are control plane signals and wherein said signals are sent directly from said trust plane controller logic to said at least one container and wherein signals from said trust plane are trust plane signals.

5. The one or more securitized software container management devices of claim 4, wherein said control plane signals flow through said trust plane or other mechanism that provides trust prior to entrance into said software containers and wherein said control plane includes its own mechanism of trust.

6. The one or more securitized software container management devices of claim 1, wherein said signals are communications signals and wherein said communications signals either contain or themselves are data transmissions, wherein said signals are securitized while said software containers are created, and wherein securitized signals are a mechanism of trust.

7. The one or more securitized software container management devices of claim 1, wherein said signals are securitized for software containers that already exist.

8. The one or more securitized software container management devices of claim 1, wherein said signals are encrypted for software containers that either are created or already exist and wherein encrypted signals are a mechanism of trust.

9. The one or more securitized software container management devices of claim 1, wherein said signals are securitized and encrypted for software containers that either are created or already exist and wherein securitized and encrypted signals are a mechanism of trust.

10. The one or more securitized software container management devices of claim 1, wherein said signals travel through one or more tunnels from said control plane to said trust plane and wherein said signals travel through one or more tunnels from either said control plane or said trust plane or both said control plane and said trust plane into and out of said software containers.

11. The one or more securitized software container management devices of claim 10, wherein said tunnels themselves are securitized and carry securitized transmissions.

12. The one or more securitized software container management devices of claim 10, wherein said tunnels themselves are encrypted and carry encrypted transmissions.

13. The one or more securitized software container management devices of claim 10, wherein said tunnels are both securitized and encrypted and carry both securitized and encrypted transmissions.

14. The one or more securitized software container management devices of claim 10, wherein transmissions are data, voice, or optical transmissions, or wherein said transmissions are data, voice, and optical transmissions, and wherein said signals are comprised of electrical, optical, mechanical, electromagnetic, or radiative energy, or electrical, optical, mechanical, electromagnetic, and radiative energy from an energy source that provides said signal types, and wherein said tunnels are channels through which said signal types travel.

15. The one or more securitized software container management devices of claim 1, wherein said trust plane provides both inter-container and external container connections for signals traveling into and out of said trust plane.

16. The one or more securitized software container management devices of claim 1, wherein said control plane has both inter-container and external container connections for signals traveling into and out of said control plane.

17. The one or more securitized software container management devices of claim 1, wherein said signals into, out of, or within said control plane provide an ability to create, initiate, modify, destroy, and remove said software containers, where said software containers are temporary and obsolete subsequent to deployment.

18. The one or more securitized software container management devices of claim 1, wherein said signals that traverse said control plane are authenticated, verified, or encrypted, or wherein said signals that traverse said control plane are authenticated, verified, and encrypted by said controller logic wherein said controller logic exists either within or external to said control plane.

19. The one or more securitized software container management devices of claim 1, wherein said signals that traverse said trust plane are authenticated, verified or encrypted, or wherein said signals that traverse said trust plane are authenticated, verified and encrypted by controller logic that exists either within or external to said trust plane.

20. The one or more securitized software container management devices of claim 1, wherein said software containers are embedded with secure communications.

21. The one or more securitized software container management devices of claim 1, wherein said software containers operate in a frictionless manner in that scripted control and operation occurs without interruption and wherein originated signals remain intact during operation.

22. The one or more securitized software container management devices of claim 1, wherein said signals carry preprogrammed source code that enables and manages operation of said software containers.

23. The one or more securitized software container management devices of claim 1, wherein said software containers are virtual devices.

24. The one or more securitized software container management devices of claim 1, wherein said software containers include a statistics processor, wherein statistics exist for setup and operational parameters, system resource use, communications connections, volume of data, run time, and external communications monitoring, and wherein said statistics also provide for statistical correlation and autocorrelation to create warnings and alarms for software containers that do not maintain statistical norms in comparison with software containers that are within statistical norms.

25. A method for using one or more securitized software container management devices, comprising:

wherein said securitized software container management devices include at least one control plane, at least one trust plane, and at least one software container, wherein a controller that exists within the control plane transfers signals along a single path to said trust plane or to said software container, or both said trust plane and said software container and wherein said signals continue traveling through said control plane to said trust plane or said software container, or both said trust plane and said software container, and wherein said signals are securitized or encrypted, or said signals are securitized and encrypted either before, or as, said signals are entering said at least one software container;

wherein one or more access devices or one or more user devices, or both one or more access devices and one or more user devices with one or more real or one or more virtual master distributed auto-synchronous array (DASA) databases or both one or more real and one or more virtual master distributed auto-synchronous array (DASA) databases located within or external to said access devices and said user devices, wherein said master (DASA) databases at least store and retrieve data and also include at least two or more partial distributed auto-synchronous array (DASA) databases, wherein said partial DASA databases function in either an independent manner, a collaborative manner or both an independent manner and a collaborative manner, wherein said master and said partial DASA databases analyze and provide information in a form of data and act to control one or more output computing devices.