Client-side encryption: Difference between revisions

Revision as of 19:10, 23 February 2016

Revision as of 19:25, 23 February 2016

Line 1:

'''Client-side encryption''' (also known as [[End-to-end encryption]]) is the [[cryptographic]] technique of [[encrypting]] data on the sender's side, before it is transmitted to a [[server (computing)|server]] such as a cloud storage service.<ref name=infosectoday>{{cite web |url= http://www.infosectoday.com/Articles/Client-Side_Encryption.htm |title= Why Client-Side Encryption Is the Next Best Idea in Cloud-Based Data Security |date= 2015 |accessdate= February 21, 2016 |author= Tunio Gaffer |website= Information Security Today |publisher= Auerbach Publications}}</ref> Client-side encryption features an encryption key that is not available to the service provider, making it difficult or impossible for service providers to decrypt hosted data. Client-side encryption allows for the creation of [[zero-knowledge proof|zero-knowledge applications]] whose providers cannot access the data its users have stored, thus offering a high level of privacy.<ref name=infosectoday/>

Client-side encryption is widely recognized{{who|date=February 2016}} as an exceptionally robust data security strategy. By eliminating the potential for data to be viewed by service providers (or third parties that compel service providers to deliver access to data), client-side encryption ensures that data and files that are stored in the cloud can only be viewed on the client side of the exchange. This prevents data loss and the unauthorized disclosure of private or personal files, providing increased peace of mind for both personal and business users.<ref name=infosectoday/>

Line 8:

==See also==

* [[End-to-end encryption]] – the encryption of data between two different clients that are communicating with each other

* [[Homomorphic encryption]]