IP Library Granted Patent US 12,443,716
Granted Patent B2
US 12,443,716 · App. 17/624,375 · Granted Oct 14, 2025

Secure cloud computing architecture and security method

Inventor: Dominique Bolignano (Paris, FR)
Assignee: PROVENRUN
G06F21/57
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,443,716
App. No.
17/624,375
Granted
Oct 14, 2025
Kind
B2
Abstract

A secure cloud computing architecture including: a first data management and/or computer program execution space (A) in which the data management or program execution is controlled by a user; and a second data management and/or computer program execution space (B) in which the data management or program execution is controlled by a third-party operator, first security policies (PSA) applied to the data or execution of programs in the first execution space (A); second security policies (PSB) applied to the data or execution of programs in the second execution space (B); a security property (P) expected by the user, compliance with the first and second security policies guaranteeing a data management and/or computer program execution in accordance with this property (P); and a trusted computing base (TCB) guaranteeing, in the absence of a violation, the application of the second security policies (PSB) in the management of the data and/or execution of the programs in the second execution space (B).

Claims (43)

1. A secure cloud computing architecture comprising:

a first execution space (A) for data management and/or computer program execution in which the management of the data and/or the execution of the programs is/are controlled by a user; and

a second execution space (B) for data management and/or computer program execution in which the management of the data or the execution of the programs is controlled by a third-party operator;

first security policies (PSA) applied to the data or to the execution of the programs in the first execution space (A);

second security policies (PSB) applied to the data or to the execution of the programs in the second execution space (B);

a security property (P) expected by the user, compliance with the first and second security policies guaranteeing data management and/or computer program execution in accordance with the security property (P); and

a trust base (TCB) guaranteeing, in the absence of violation, the application of the second security policies (PSB) in the management of the data and/or the execution of the programs in the second execution space (B),

wherein the trust base comprises:

a hardware part having observers indicating unauthorised access,

wherein the trust base comprises a hardware security module comprising the hardware part of the trust base, and

a software part, the software part being made available to the user and/or to a representative of the user and/or to a third party trusted by the user,

wherein the observers indicating unauthorised access are visible to the user and/or the representative of the user and/or the third party trusted by the user,

wherein means are provided to the user to enable the user to be convinced that all of the execution paths of the software part of the trust base guarantee compliance with the second security policies, under normal operating conditions,

wherein the architecture further includes a hardware part of the trust base forming an additional security module (BTA), the additional security module being disposed at the entrance of a subset of servers and having means for filtering data packets entering the subset, the filtration including checking up that the data packets comply with a security policy.

2. The architecture according to claim 1 , wherein the hardware security module enables the user to select a certifier to represent the user.

3. The architecture according to claim 1 , wherein a manner of rebuilding the software part of the trust base is provided or made available to the user and/or to the representative of the user and/or to the third third party trusted by the user.

4. The architecture according to claim 1 , wherein a software core of the hardware security module has been formally proven.

5. The architecture according to claim 1 , comprising an infrastructure comprising the subset which comprises one or several physical server(s) forming the space (B), wherein a hardware part and/or the software base of the trust base forming box(es) (BT) is/are associated to the servers.

6. The architecture according to claim 1 , wherein the hardware part of the trust base is provided or made available to the user and/or to the representative of the user and/or to the third party trusted by the user.

7. A method of securing a cloud computing architecture, the method comprising:

providing a first execution space (A) for data management and/or computer program execution in which the management of the data and/or the execution of the programs is/are controlled by a user;

providing a second execution space (B) for computer program execution in which the management of the data and/or the execution of the programs is/are controlled by a third-party operator;

applying first security policies (PSA) to the data and/or to the execution of the programs in the first execution space (A);

applying second security policies (PSB) to the data and/or to the execution of the programs in the second execution space (B);

defining a security property (P) expected by the user, compliance with the first (PSA) and second (PSB) security policies guaranteeing data management and/or computer program execution in accordance with the security property (P);

providing a trust base (TCB) guaranteeing the application of the second security policies (PSB) in the management of the data and/or the execution of the programs in the second execution space (B),

wherein the trust base comprises:

a hardware part having observers indicating unauthorised access,

wherein the trust base comprises a hardware security module comprising the hardware part of the trust base, the hardware part of the trust base forming an additional security module (BTA), the additional security module being disposed at the entrance of a subset of servers and having means for filtering data packets entering the subset, the filtration including checking up that the data packets comply with a security policy, and

a software part, the software part being made available to the user and/or to a representative of the user and/or to a third party trusted by the user,

wherein the observers indicating unauthorised access are visible to the user and/or the representative of the user and/or the third party trusted by the user;

and wherein

wherein the management of the data and/or the execution of the programs performed by the user at least in part in the second execution space (B) is/are deemed to meet the security property (P) expected by the user, if the observers indicating access remain blank,

and wherein means are provided to the user to enable the user to be convinced that all of the execution paths of the software part of the trust base guarantee compliance with the second security policies, under normal operating conditions.

8. The method according to claim 7 , wherein the software part of the trust base and the manner of rebuilding the software part of the trust base are provided or made available in its entirety to the user and/or to the representative of the user and/or to the third-party trusted by the user.

9. The architecture according to claim 2 , wherein a manner of rebuilding the software part of the trust base is provided or made available to the user and/or to the representative of the user and/or to the third party trusted by the user.

10. The architecture according to claim 8 , wherein a manner of rebuilding the software part of the trust base is provided or made available to the user and/or to the representative of the user and/or to the third party trusted by the user.

11. The architecture according to claim 2 , wherein a software core of the hardware security module has been formally proven.

12. The architecture according to claim 3 , wherein a software core of the hardware security module has been formally proven.

13. The architecture according to claim 2 , comprising an infrastructure comprising a subset which comprises one or several physical server(s) forming the space (B), wherein a hardware part and/or the software base of the trust base forming box(es) (BT) is/are associated to the servers.

14. The architecture according to claim 3 , comprising an infrastructure comprising a subset which comprises one or several physical server(s) forming the space (B), wherein a hardware part and/or the software base of the trust base forming box(es) (BT) is/are associated to the servers.

15. The architecture according to claim 4 , comprising an infrastructure comprising a subset which comprises one or several physical server(s) forming the space (B), wherein a hardware part and/or the software base of the trust base forming box(es) (BT) is/are associated to the servers.

16. The architecture according to claim 3 , wherein providing or making available the manner of rebuilding the software part of the trust base to the user and/or to the representative of the user and/or to the third party trusted by the user include providing or making available a source code and/or a compiler and/or generators used in rebuilding the software part of the trust base.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2022
From: BOLIGNANO, DOMINIQUE
To: PROVENRUN
Reel/Frame 060424/0092 →
CHANGE OF NAME Recorded Jan 3, 2022
From: PROVE & RUN
To: PROVENRUN
Reel/Frame 058570/0373 →
Priority Claims (2)
FR 1907284 · Jul 1, 2019 · national
FR 1907614 · Jul 8, 2019 · national
Continuity (1)
Related Publication 20220358219A1 · Nov 10, 2022
References Cited (17)
US 8572735B2 · Ghosh · 2013 [cited by examiner]
US 8997215B2 · Guriappa Srinivas · 2015 [cited by examiner]
US 20070271618A1 · Chao · 2007 [cited by examiner]
US 20110247047A1 · Loureiro et al. · 2011 [cited by applicant]
US 20120084438A1 · Raleigh · 2012 [cited by examiner]
US 20140075567A1 · Raleigh · 2014 [cited by examiner]
US 20140137179A1 · Christodorescu et al. · 2014 [cited by applicant]
US 20140289796A1 · Moloian · 2014 [cited by examiner]
US 20150143452A1 · Hamlen · 2015 [cited by examiner]
US 20160134424A1 · Forget · 2016 [cited by examiner]
US 20160212128A1 · Pike · 2016 [cited by examiner]
US 20190028281A1 · Turissini · 2019 [cited by examiner]
US 20200201779A1 · Skertic · 2020 [cited by examiner]
EP 2372974A1 · 2011 [cited by applicant]
Dinh, “A Survey of mobile cloud computing: architecture, applications, and approaches”, 2013, Wireless Communications and Mobile Computing, pp. 1587-1611 (Year: 2013). [cited by examiner]
Baumann, “Shielding applications from an untrusted cloud with Haven”, Oct. 2014, USENIX, pp. 267-280 (Year: 2014). [cited by examiner]
International Search Report and Written Opinion dated Sep. 25, 2020 in corresponding application No. PCT/EP2020/068484; w/English partial translation and partial machine translation (total 14 pages). [cited by applicant]