Method for manufacturing a secure, modular business-specific hardware application and corresponding operating system
Disclosed is a method for manufacturing a secure, modular business-specific hardware application, including: a step of selecting: a hardware computer integrated into a closed case that isolates it from the outside so as to make the hardware resources of this hardware computer structurally non-expandable because these resources cannot be accessed from outside the case without damaging them, an operating system for managing containers in a generic, lightweight fashion, associated with the computer, a software development kit, associated with the operating system and with the computer, container templates, business-specific software components, a step of deploying the business-specific software components in instantiated containers based on the container templates.
1. Method for manufacturing a secure, modular business-specific hardware application, comprising:
selecting a hardware computer integrated into a closed case that isolates the hardware computer from the outside so as to make hardware resources of the hardware computer structurally non-expandable because the hardware resources cannot be accessed from outside the case without damaging the hardware resources, an operating system for managing containers in a generic, lightweight fashion, associated with the computer, a software development kit, associated with the operating system and with the hardware computer, container templates, business-specific software components; and
deploying the business-specific software components in instantiated containers based on the container templates.
2. The method for manufacturing a secure, modular business-specific hardware application according to claim 1 , wherein: the operating system capable of managing containers in a generic, lightweight fashion comprises: a generic mechanism for managing a non-predetermined number of containers, comprising: a function of installing container templates, a function of updating the container templates, a function of creating a container by instantiating a container template, a function of starting a container, a function of stopping a container, a function of destroying a container, a mechanism for configuring said generic mechanism for managing containers, capable of configuring: the list of containers to be managed, the set of additional components required for the operation of the containers to be managed.
3. The method for manufacturing a secure, modular business-specific hardware application according to claim 2 , wherein: said generic mechanism for managing containers comprises only: said function of installing container templates, said function of updating the container templates, said function of creating a container by instantiating a container template, said function of starting a container, said function of stopping a container, said function of destroying a container.
4. The method for manufacturing a secure, modular business-specific hardware application according to claim 3 , wherein: said configuration mechanism of said generic mechanism for managing containers is able to configure only: said list of containers to be managed, said set of additional components required for the operation of the containers to be managed.
5. The method for manufacturing a secure, modular business-specific hardware application according to claim 2 , wherein: said set of additional components required for the operation of the containers to be managed, comprises: virtual networks, and/or data volumes, and/or access to business-specific hardware components with the access rights of the various containers to said components.
6. The method for manufacturing a secure, modular business-specific hardware application according to claim 1 , wherein a number of software components forming said operating system is less than 100 software components.
7. The method for manufacturing a secure, modular business-specific hardware application according to claim 1 , wherein said hardware computer, integrated into a closed case that isolates it from the outside so as to make the hardware resources of the hardware computer structurally non-expandable because these resources cannot be accessed from outside the case without damaging them, already includes one or more potential business-specific hardware components.
8. The method for manufacturing a secure, modular business-specific hardware application according to claim 7 , wherein at least one of the one or more business-specific hardware components is a cryptographic card that is advantageously capable of creating/authenticating electronic signatures and/or of performing data encryption/decryption.
9. The method for manufacturing a secure, modular business-specific hardware application according to claim 1 , wherein said hardware computer comprises at least: one or more microprocessors, one or more volatile memories, one or more persistent memories, one or more network interfaces.
10. The method for manufacturing a secure, modular business-specific hardware application according to claim 9 , wherein the total capacity of the volatile memory(-ies) is between 5 and 30 GB, and the total capacity of the persistent memory(-ies) is between 50 and 500 GB.
11. The method for manufacturing a secure, modular business-specific hardware application according to claim 1 , wherein: said deployment of business-specific software components is organized into a microservices architecture.
12. The method for manufacturing a secure, modular business-specific hardware application according to claim 1 , wherein: additional security software components are implemented within said operating system, and/or specific configurations increasing the level of security are implemented within said operating system.
13. The method for manufacturing a secure, modular business-specific hardware application according to claim 1 , wherein: dedicated business hardware is implemented within the business-specific hardware application, and additional software components for controlling the dedicated business hardware are implemented within said operating system.
14. The method for manufacturing a secure, modular business-specific hardware application according to claim 1 , wherein the configuration of the entire software portion of the business-specific hardware application is hardened to improve its security, and/or the configuration of the operating system is hardened to improve its security.
15. The method for manufacturing a secure, modular business-specific hardware application according to claim 1 , wherein: the operating system is a Linux operating system, a container management system is a Docker system.
16. A non-transitory computer readable storage medium containing instructions for an operating system capable of managing containers in a generic, lightweight fashion, intended to be used in a method for manufacturing a secure, modular business-specific hardware application, comprising: a generic mechanism for managing a non-predetermined number of containers, comprising: a function of installing container templates, a function of updating the container templates, a function of creating a container by instantiating a container template, a function of starting a container, a function of stopping a container, a function of destroying a container, a mechanism for configuring said generic mechanism for managing containers, capable of configuring: the list of containers to be managed, the set of additional components required for the operation of the containers to be managed.
17. The non-transitory computer readable storage medium according to claim 16 , wherein: said generic mechanism for managing containers comprises only: said function of installing container templates, said function of updating the container templates, said function of creating a container by instantiating a container template, said function of starting a container, said function of stopping a container, said function of destroying a container.
18. The non-transitory computer readable storage medium according to claim 17 , wherein: said configuration mechanism of said generic mechanism for managing containers is able to configure only: said list of containers to be managed, said additional components required for the operation of the containers to be managed.
19. The non-transitory computer readable storage medium according to claim 16 , wherein: said set of additional components required for the operation of the containers to be managed, comprises: virtual networks, and/or data volumes, and/or access to business-specific hardware components with the access rights of the various containers to said components.
20. The non-transitory computer readable storage medium according to claim 16 , wherein a number of software components forming said operating system is less than 100 software components.