Mercurial > hg > orthanc-book
changeset 453:d44d61bdcd09
fix
| author | Alain Mazy <alain@mazy.be> |
|---|---|
| date | Fri, 03 Jul 2020 13:05:41 +0200 |
| parents | aef5c8b74381 |
| children | 35b3b0a2d16c 982774ebee52 |
| files | Sphinx/source/plugins/object-storage.rst |
| diffstat | 1 files changed, 0 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/Sphinx/source/plugins/object-storage.rst Fri Jul 03 13:02:29 2020 +0200 +++ b/Sphinx/source/plugins/object-storage.rst Fri Jul 03 13:05:41 2020 +0200 @@ -165,8 +165,6 @@ However, note that, if you're running entirely in a cloud environment, your decryption keys will still be stored on the cloud infrastructure (VM disks - process RAM) and an attacker could still eventually gain access to this keys. -Furthermore, in the scope of the `Cloud Act <https://en.wikipedia.org/wiki/CLOUD_Act>`__ , the cloud provider might still have -the possibility to retrieve your data and encryption key (while it will still be more complex than with standard encryption at rest). If Orthanc is running in your infrastructure with the Index DB on your infrastructure, and files are store in the cloud, the master keys will remain on your infrastructure only and there's no way the data stored in the cloud could be decrypted outside your infrastructure.