Isn't encryption on the device the best bet for a safe cloud | idgard®

Isn't encryption on the device the best bet for a safe cloud?

Isn't encryption on the device the best bet for a safe cloud?

The term „cloud computing“ encompasses two aspects:
  1. Data storage in a cloud for one’s self, excluding multiple or third-party access.
  1. Data processing or storage of information in a cloud, intended for multiple or third-party access.
In the first case, encrypting data on a device and then transferring it in encrypted form to the cloud is sufficient. However, should information be shared with third parties, as in the second case, the secret key would have to be distributed through some safe channels or by centralized key administration. Transferring the key through unsafe channels (e.g., a password by e-mail), can lead to undesired eavesdropping through robots and third parties. However, should the data not only be stored but also processed in the cloud, data encryption is necessary once it has been transferred to the cloud. This is because data processing requires, with the exception of so-called homomorphic encryption, that the data is available in plain text. Usually at this point, the administrators of the cloud, as well as the cloud application, have direct access to the confidential data. Consequently, that kind of data processing requires trustworthy providers and administrators. The special feature of the sealed cloud is that it logically, electronically and mechanically prevents the operators or administrators from accessing the data during processing. Thus, the sealed cloud creates the possibility to process confidential data in the cloud. idgard® applies this new basic technology to enable secure communication via sealed privacy boxes without complicated key management.


Dieser Artikel konnte Ihre Frage nicht beantworten?

Wir helfen Ihnen gerne weiter! Schreiben Sie uns einfach eine Nachricht mit Ihren Fragen und wir melden uns so bald wie möglich bei Ihnen zurück.

   Ticket erstellen

Haftungshinweis/Disclaimer

Der Inhalt dieser Onlinehilfe dient lediglich zu Informations- und Dokumentationszwecken für das Produkt idgard® und kann jederzeit ohne Vorankündigungen geändert werden. Für Fehler oder Ungenauigkeiten übernehmen wir keine Verantwortung oder Haftung. Aufgrund technischer Weiterentwicklungen behält sich die uniscon GmbH jederzeit vor, den Funktionsumfang des Produkts zu ändern.


(C) uniscon GmbH



    • Related Articles

    • Operator-safe data exchange with idgard®

      Operator-safe data exchange with idgard® With idgard®, operator security means that we have no access to your data. idgard® eliminates this risk completely, not only thanks to its encryption technology but also through intelligent physical access ...
    • Problem with new login

      Problem with new login At the moment, when connecting idgard® Boxes with WebDAV via FullQualifiedDistinguished Name (FQDN) as "networkfolder" and not as "drive", problems occur after a new Windows login due to a problem of the Windows WebDav Client ...
    • Future developments of idgard®

      Future developments of idgard® idgard® is the first cloud service built on sealed cloud technology, which makes it possible, for the first time, to combine end-to-end security with data processing in the cloud. So far, it was possible either to only ...
    • Enable WebDAV function

      Enable WebDAV function WebDAV customarily postulates local storage of a username and password, so that it is only secure and recommendable if the used device is in a trustworthy environment. Protection Class Implications as per Trusted Cloud Data ...
    • Logging in to idgard® using the TOTP password (two-factor authentication)

      Logging in to idgard® using the T-OTP (time-based one-time Password) Sensitive data requires a higher level of protection. An authentication app must be installed before the TOTP process can be used. After setting up TOTP, the user must enter a ...